Bug 986789 - An error occurred while configuring puppet in transaction puppet page
An error occurred while configuring puppet in transaction puppet page
Product: oVirt
Classification: Community
Component: ovirt-node (Show other bugs)
Unspecified Unspecified
high Severity high
: ---
: 3.4.1
Assigned To: Ryan Barry
Depends On:
Blocks: 988666
  Show dependency treegraph
Reported: 2013-07-22 02:09 EDT by haiyang,dong
Modified: 2014-04-30 06:55 EDT (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 988666 (view as bug list)
Last Closed: 2014-04-30 06:55:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
attached Screenshot (5.57 KB, image/png)
2013-07-22 02:09 EDT, haiyang,dong
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 17489 None None None Never

  None (edit)
Description haiyang,dong 2013-07-22 02:09:50 EDT
Created attachment 776730 [details]
attached Screenshot

Description of problem:
Using edit-node install ovirt-node-plugin-puppet into ovirt-node-iso,
enter into puppet page and enabled puppet service and configure the puppet server
and puppet certificate name
then clicking "save & Run" button. but An error occurred while configuring puppet 
in transaction puppet page with the follow error info:
An error occurred while applying the changes:
__init__() takes exactly 2 arguments(3 given) (Seen puppet transaction page.png)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:


Actual results:

Expected results:

Additional info:
Comment 1 Ryan Barry 2013-08-06 10:53:21 EDT
A fix for this has been posted. It looks like it was a side-effect of changes to ovirt.node.utils.fs.File.
Comment 3 Sandro Bonazzola 2014-03-04 04:22:53 EST
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

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