Red Hat Bugzilla – Bug 988668
TUI:miss "Reset" button for puppet page
Last modified: 2014-01-21 14:46:37 EST
+++ This bug was initially created as a clone of Bug #986820 +++
Description of problem:
Using edit-node install ovirt-node-plugin-puppet into ovirt-node-iso,
enter into puppet page and check that miss "Reset" button for puppet page.
(Seen puppet page.png)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Could reproduce this issue on the follow build:
so need to clone it from ovirt-node upstream to downstream to track this issue
Using edit-node install ovirt-node-plugin-puppet into rhev-hypervisor6-6.5-20131017.0.iso, then install this edited iso
enter into puppet page and check that "Reset" button in puppet page and also the "Reset" button functions can work
so this bug has been fixed, 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:
Thanks in advance.
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.