Red Hat Bugzilla – Bug 1016373
Met clear /etc/puppet/puppet.conf issue
Last modified: 2014-01-21 14:52:39 EST
Description of problem:
Using edit-node install ovirt-node-plugin-puppet into rhev-hypervisor6-6.5-20130930.0.auto665.el6.iso ,
enter into puppet page and enabled puppet service and configure the puppet server
and puppet certificate name
then clicking "Save" button.Then check the file "/etc/puppet/puppet.conf", the content of /etc/puppet/puppet.conf
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Still met clear /etc/puppet/puppet.conf issue, also this bug blocked Bug 1016393,
Bug 1016386, Bug 988666 to verify. so change "Priority" into "urgent".
Test as follow:
Using edit-node install ovirt-node-plugin-puppet into rhevh-6.5-20131213.0.0.iso and clean install this
iso .Login it and enter into puppet page, configure
Puppet Certificate Name: dhcp-10-106.nay.redhat.com
after clicking "Save" button to apply this configuration. check that:
[root@agent2 admin]# cat /etc/puppet/puppet.conf |more
server = "dhcp-10-214.nay.redhat.com"
certname = "dhcp-10-106.nay.redhat.com"
# The Puppet log directory.
# The default value is '$vardir/log'.
logdir = /var/log/puppet
so this issue about "clear /etc/puppet/puppet.conf issue" has been fixed,after the status of this bug changed into "ON_QA", i'll verify it.
According to comment 10, change it into "verified".
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thank you for your help.
Also this bug was fixed in the follow version:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.