Okay I've been remiss in posting this reply but I've actually solve this issue.
What I ended up having to do is remove puppet remove Ruby remove all the gems and then manually clean out all the directories that are touched by everything that I just mentioned. Then very carefully I reinstalled everything starting with puppet and used Deb packages instead of loading through gems. Now everything runs very happily. What I would gather by this is something got corrupted somewhere along the line that forced me to take such drastic actions. On Tue, Oct 25, 2016, 17:07 Rob Nelson <rnels...@gmail.com> wrote: > Could you share how your testing environment is set up? Most use bundler, > so that the puppet agent installed on the system doesn't affect the tests, > but it would appear that is not the case here. However, before commenting > further, we need to see a bit more about the setup. > > I do not think the agent failure is strictly related, in that the agent > should work fine out of the box, but by enumerating your test setup, we may > find some variant settings/locations you use that are causing a conflict. > > > Rob Nelson > rnels...@gmail.com > > On Tue, Oct 25, 2016 at 2:03 PM, Peter Berghold <salty.cowd...@gmail.com> > wrote: > > What I thought were unrelated issues I've discovered they are related. > > I was using RSpec doing spec testing on Puppet code very happily when I > decided to install the Puppet agent (attempting to eat my own dog food of > course) and then RSpec broke. > > Error message spec started throwing out: > > NoMethodError: > undefined method `static_catalogs?' for > #<Puppet::Node::Environment:0x000000011a16b0> > > causing all my test cases to fail. > > Additionally the Puppet agent will not run as a service but it will run > standalone (puppet agent -t). > > During install: > Job for puppet.service failed because the control process exited with > error code. See "systemctl status puppet.service" and "journalctl -xe" for > details. > invoke-rc.d: initscript puppet, action "start" failed. > > Checking systemctl status > > ● puppet.service - Puppet agent > Loaded: loaded (/lib/systemd/system/puppet.service; enabled; vendor > preset: enabled) > Active: failed (Result: exit-code) since Tue 2016-10-25 18:01:14 UTC; > 52s ago > Process: 7473 ExecStart=/usr/bin/puppet agent $DAEMON_OPTS (code=exited, > status=1/FAILURE) > > Oct 25 18:01:13 mtznjv1pdev01 puppet[7473]: WARN: Clearing out unresolved > specs. > Oct 25 18:01:13 mtznjv1pdev01 puppet[7473]: Please report a bug if this > causes problems. > Oct 25 18:01:14 mtznjv1pdev01 puppet-agent[7473]: Could not autoload > puppet/indirector/report/rest: uninitialized cons > Oct 25 18:01:14 mtznjv1pdev01 puppet-agent[7473]: Did you mean? > Puppet::Indirector > Oct 25 18:01:14 mtznjv1pdev01 puppet-agent[7473]: Could not prepare for > execution: Could not autoload puppet/indirecto > Oct 25 18:01:14 mtznjv1pdev01 puppet-agent[7473]: Did you mean? > Puppet::Indirector > Oct 25 18:01:14 mtznjv1pdev01 systemd[1]: puppet.service: Control process > exited, code=exited status=1 > Oct 25 18:01:14 mtznjv1pdev01 systemd[1]: Failed to start Puppet agent. > Oct 25 18:01:14 mtznjv1pdev01 systemd[1]: puppet.service: Unit entered > failed state. > Oct 25 18:01:14 mtznjv1pdev01 systemd[1]: puppet.service: Failed with > result 'exit-code'. > > and I get the same messages with "journalctl -ex" > > So for now my development system is going without a Puppet agent. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CAArvnv0uZKSrWO5uwSTVKrdBLFSeaMyHcYvZ6Fvrj3xZL69A7A%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CAArvnv0uZKSrWO5uwSTVKrdBLFSeaMyHcYvZ6Fvrj3xZL69A7A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CAC76iT_fHwWwGaGvDtfw8SdwGPegMq%2BjSNy51yR2vXqi0iQeww%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CAC76iT_fHwWwGaGvDtfw8SdwGPegMq%2BjSNy51yR2vXqi0iQeww%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAArvnv1AZ5YsuXsKWoG3o3atGtCys%3D3KGWZ%3DdDqNKMZTYXiijg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
