Created attachment 893877 [details] can't set password Description of problem: TUI: Can't set password for adding Node through oVirt Engine UI In oVirt Engine menu, user can set password for adding Node through oVirt Engine UI, but actually we can't do that and it will pop-up: oVirt Engine Fingerprint Can't connect to oVirt Engine. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20140508.0.el6ev ovirt-node-3.0.1-18.el6_5.10.noarch vdsm-4.14.7-1.el6ev.x86_64 RHEV-M: av8.1 How reproducible: 100% Steps to Reproduce: 1. Install rhev-hypervisor6-6.5-20140508.0.el6ev. 2. Configure network. 3. Enter oVirt Engine menu, leave management server blank. 4. Set password for for adding Node through oVirt Engine UI. 5. Save & Register Actual results: Can't set password for adding Node through oVirt Engine UI Expected results: Can set password for adding Node through oVirt Engine UI Additional info: Workaround is here: Enter rescue mode and set root password, and then add Node through oVirt Engine UI with the new root password can successful, the Node can up normally. No such issue on build rhev-hypervisor6-6.5-20140407.0.el6ev, so it is a regression bug.
Created attachment 893879 [details] vdsm.log
verified on Red Hat Enterprise Virtualization Hypervisor release 6.5 (20140507.0.el6ev)
I can still reproduce the bug on Red Hat Enterprise Virtualization Hypervisor release 6.5 (20140507.0.el6ev) stpes to reproduce: 1. Configure network 2. Enter Enine page 3. Set password ( Do NOT set a management server url) 4. Hit Save & Register Result: A dialog is shown (can not register to engine) Expected result: The root password is set
moving to QA i tested it on z stream rhevh
Removing FailedQA because the build that was tested in comment 4 5 and 6 were all OLD builds not containing the fix.
verified on Red Hat Enterprise Virtualization Hypervisor release 6.5 (20140513.0.el6ev) ovirt-node-plugin-vdsm-0.1.1-19.el6ev.noarch
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. http://rhn.redhat.com/errata/RHBA-2014-0673.html