Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: Executing "puppet agent disable" and it's not throwing any error message.
Customer executed"# puppet agent disable" across a set of nodes to disbale puppet and received no error. The correct command was 'puppet agent --disable'. As a result configuration changes were taking place when the should not have.
Version-Release number of selected component (if applicable):
puppet-3.8.6-2.el7sat.noarch
How reproducible: Always
Steps to Reproduce:
1. Execute below command on the system to disable puppet:
# puppet agent disable
Actual results:
command executed without any error, with exit status 0:
[root@client ~]# rpm -qa puppet
puppet-3.8.6-2.el7sat.noarch
[root@client ~]# puppet agent disable
[root@client ~]# echo $?
0
Expected results:
It should throw any error message like, not a valid option.
Additional info:
Created patch from upstream MR, and applied works on puppet version puppet-3.8.6
To apply the patch follow below steps
1) Download the patch attached to this Bugzilla to /tmp location
2) Execute following commands on the puppet client
# /usr/share/ruby/vendor_ruby/puppet/application
# patch -p1 agent.rb < /tmp/agent.rb.patch
3) Verify
# puppet agent disable
Error: Could not prepare for execution: The puppet agent command does not take parameters
# echo $?
1
# puppet agent --disable
# echo $?
0
-- nagoor