Red Hat Bugzilla – Bug 1016386
Missed persist puppet.conf in puppet_page.py
Last modified: 2014-01-21 14:52:43 EST
Description of problem:
Missed persist puppet.conf in the code of puppet_page.py. This will lead to
lose configuration info in the puppet.conf after reboot rhev-h.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
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:
Thanks in advance.
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
After reboot rhev-h, check that configuration info still was saved in the puppet.conf.
so this bug has been fixed,change the status into "verified".
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.