Bug 1023642 - Throw "TypeError("The type (<type 'bool'>) of OVIRT_PUPPET_ENABLED" error when disabling puppet
Throw "TypeError("The type (<type 'bool'>) of OVIRT_PUPPET_ENABLED" error whe...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Ryan Barry
Virtualization Bugs
Depends On: 1022960
  Show dependency treegraph
Reported: 2013-10-26 08:18 EDT by haiyang,dong
Modified: 2014-06-09 10:07 EDT (History)
17 users (show)

See Also:
Fixed In Version: ovirt-node-3.0.1-8.el6
Doc Type: Bug Fix
Doc Text:
When disabling puppet by unchecking "Enable Puppet []", the following exception was generated:"TypeError("The type (<type 'bool'>) of OVIRT_PUPPET_ENABLED" This was caused by a logic problem in the code which is now fixed. puppet is disabled when the check bock is unchecked.
Story Points: ---
Clone Of: 1022960
Last Closed: 2014-01-21 14:35:54 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rbarry: needinfo-

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 20487 None None None Never
Red Hat Product Errata RHBA-2014:0033 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2014-01-21 19:14:30 EST

  None (edit)
Description haiyang,dong 2013-10-26 08:18:48 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 Server:master.example.com
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):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:
Comment 2 haiyang,dong 2013-10-26 08:22:25 EDT
Could reproduce this issue in downstream:

so need clone it from upstream to track it in rhev-h
Comment 4 haiyang,dong 2013-12-17 05:40:15 EST
Test version:

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.
Comment 5 haiyang,dong 2013-12-19 21:09:09 EST
According to comment 4 , change the status into "verified"
Comment 6 Cheryn Tan 2014-01-08 00:35:37 EST
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.
Comment 8 errata-xmlrpc 2014-01-21 14:35:54 EST
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.


Note You need to log in before you can comment on or make changes to this bug.