Red Hat Bugzilla – Bug 1023642
Throw "TypeError("The type (<type 'bool'>) of OVIRT_PUPPET_ENABLED" error when disabling puppet
Last modified: 2014-06-09 10:07:32 EDT
+++ This bug was initially created as a clone of Bug #1022960 +++
Description of problem:
Using edit-node install ovirt-node-plugin-puppet into ovirt-node-iso and clean install this
iso .Login it and enter into puppet page, configure
Puppet Certificate Name: agent2.example.com
after clicking "Save" button to apply this configuration. check that it will configure puppet success.
But when disabling puppet via unchecked "Enable Puppet ", it will throw execption
about "TypeError("The type (<type 'bool'>) of OVIRT_PUPPET_ENABLED" error info.(Seen execption when disable puppet.png )
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Could reproduce this issue in downstream:
so need clone it from upstream to track it in rhev-h
Unslect "Enable Puppet" in puppet_page.py to disable puppet.No exception was thrown. It will stop puppet service and remove related
configuration info from "/etc/puppet/puppet.conf"
so this bug has been fixed on ovirt-node-3.0.1-9.el6_5, after the status of this bug changed into "ON_QA", I will verify it.
According to comment 4 , change the status 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.
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.