Description of problem: UI crash when setup hosted engine through TUI. It will report error like follows. ================================================================================ An error appeared in the UI: Exception('There are not enough arguments given for <function update at 0x39981b8> of <ovirt.node.setup.hostedengine.hosted_engine_page.HostedEngine object at 0x3bc6710>',) Press ENTER to logout ... or enter 's' to drop to shell ================================================================================ Version-Release number of selected component (if applicable): rhev-hypervisor6-6.6-20150304 ovirt-node-3.2.1-9.el6.noarch ovirt-node-plugin-hosted-engine-0.2.0-9.0.el6ev.x86_64 ovirt-hosted-engine-setup-1.2.2-1.el6ev.noarch ovirt-hosted-engine-ha-1.2.5-1.el6ev.noarch How reproducible: 100% Steps to Reproduce: 1. Install rhev-hypervisor6-6.6-20150304 2. Enable network 3. Configure hosted engine by click <Setup Hosted Engine> Actual results: 1. It will report error like follows. ================================================================================ An error appeared in the UI: Exception('There are not enough arguments given for <function update at 0x39981b8> of <ovirt.node.setup.hostedengine.hosted_engine_page.HostedEngine object at 0x3bc6710>',) Press ENTER to logout ... or enter 's' to drop to shell ================================================================================ Expected results: 1. After step3, it should start the hosted engine setup process. Additional info:
I succeeded to istall RHEVH Red Hat Enterprise Virtualization Hypervisor 6.6 (20150304.0.el6ev) following these steps: Via Foreman installed latest RHEVH version and then via ENGINE installed rhev-hypervisor6-6.6-20150304.0.el6ev.noarch.rpm, then upgraded two RHEVH hypervisors to rhev-hypervisor6-6.6-20150304.0.el6ev.noarch.rpm and set them to maintenance, then removed from my first ENGINE. Now that I had two Red Hat Enterprise Virtualization Hypervisor 6.6 (20150304.0.el6ev) hypervisors, I started my HE deployment by "screen hosted-engine --deploy" command on first hypervisor and finished the deployment successfully, then installed RHEVM, then added second hypervisor with the RHEVH rhev-hypervisor6-6.6-20150304.0.el6ev.noarch.rpm. My only problem was improper status reported by ENGINE via WEBUI as appears within the attachment.
Created attachment 1000027 [details] improper status reported
(In reply to Nikolai Sednev from comment #2) > I succeeded to istall RHEVH Red Hat Enterprise Virtualization Hypervisor 6.6 > (20150304.0.el6ev) following these steps: > > Via Foreman installed latest RHEVH version and then via ENGINE installed > rhev-hypervisor6-6.6-20150304.0.el6ev.noarch.rpm, then upgraded two RHEVH > hypervisors to rhev-hypervisor6-6.6-20150304.0.el6ev.noarch.rpm and set them > to maintenance, then removed from my first ENGINE. > > Now that I had two Red Hat Enterprise Virtualization Hypervisor 6.6 > (20150304.0.el6ev) hypervisors, I started my HE deployment by "screen > hosted-engine --deploy" command on first hypervisor and finished the > deployment successfully, then installed RHEVM, then added second hypervisor > with the RHEVH rhev-hypervisor6-6.6-20150304.0.el6ev.noarch.rpm. My only > problem was improper status reported by ENGINE via WEBUI as appears within > the attachment. Hi Nikolai, Please open a different bug to this report. Thanks!
Hi Sandro, Any ideas for the comment#2 and screenshot?
I don't know what's causing that status to be displayed. Oved?
We had a QE build in which working with the updated engine, and older VDSM, caused status ERROR for the host. What engine build are you working with?
Also, isn't it similar to Bug 1200474 ?
(In reply to Oved Ourfali from comment #7) > We had a QE build in which working with the updated engine, and older VDSM, > caused status ERROR for the host. > What engine build are you working with? I am not using the updated engine. Maybe the error in comment#2 is similar with bug#1199387. For my issue, I just install the clean rhev-hypervisor6-6.6-20150304. version list: # rpm -qa |grep engine ovirt-hosted-engine-ha-1.2.5-1.el6ev.noarch ovirt-node-plugin-hosted-engine-0.2.0-9.0.el6ev.x86_64 ovirt-hosted-engine-setup-1.2.2-1.el6ev.noarch # rpm -qa |grep vdsm ovirt-node-plugin-vdsm-0.2.0-19.el6ev.noarch vdsm-4.16.8.1-7.el6ev.x86_64
Hi Fabian, Please provide RHEVH-HE relevant image for this bug to be verified on 3.6 environment.
Test version: rhev-hypervisor7-7.2-20151104.0.iso ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch ovirt-node-plugin-hosted-engine-0.3.0-2.el7ev.noarch Test steps: 1. Install rhev-hypervisor7-7.2-20151104.0.iso 2. Enable network 3. Configure hosted engine by click <Deploy Hosted Engine> Test result: 1. Hosted Engine setup process can be triggered correctly. So this issue is fixed in ovirt-node-plugin-hosted-engine-0.3.0-2.el7ev.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. https://rhn.redhat.com/errata/RHBA-2016-0378.html