tickets | 20 Jun 2012 05:01

[Puppet - Bug #15122] (Unreviewed) Incorrect error message when running Puppet Agent that is administratively locked

Issue #15122 has been reported by Ryan Coleman.

Bug #15122: Incorrect error message when running Puppet Agent that is administratively locked

  • Author: Ryan Coleman
  • Status: Unreviewed
  • Priority: Normal
  • Assignee:
  • Category: agent
  • Target version:
  • Affected Puppet version: 2.7.12
  • Keywords: agent
  • Branch:

Scenario
I used MCollective to disable Puppet Agent on an agent which drops the lock file in place.

Later, I forgot about this and ran puppet agent -t.

Here’s the error message I received.

[root <at> animal-centos ~]# puppet agent -t notice: Skipping run of Puppet configuration client; administratively disabled; use 'puppet Puppet configuration client --enable' to re-enable.

I believe the correct message would have been use ‘puppet agent —enable’ to re-enable.

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
tickets | 27 Jun 2012 01:25

[Puppet - Bug #15122] (Duplicate) Incorrect error message when running Puppet Agent that is administratively locked

Issue #15122 has been updated by Matthaus Litteken.
  • Status changed from Unreviewed to Duplicate

Dupe of 14946.

Bug #15122: Incorrect error message when running Puppet Agent that is administratively locked

  • Author: Ryan Coleman
  • Status: Duplicate
  • Priority: Normal
  • Assignee:
  • Category: agent
  • Target version:
  • Affected Puppet version: 2.7.12
  • Keywords: agent
  • Branch:

Scenario
I used MCollective to disable Puppet Agent on an agent which drops the lock file in place.

Later, I forgot about this and ran puppet agent -t.

Here’s the error message I received.

[root <at> animal-centos ~]# puppet agent -t notice: Skipping run of Puppet configuration client; administratively disabled; use 'puppet Puppet configuration client --enable' to re-enable.

I believe the correct message would have been use ‘puppet agent —enable’ to re-enable.

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Gmane