Created attachment 1519996 [details] Picture Description of problem: Hosted engine wizard displays "System data could not be retrieved!". Cannot deploy hosted-engine via cockpit UI. Version-Release number of selected component (if applicable): redhat-virtualization-host-4.3-20190109.0.el7_6.x86_64.liveimg.squashfs cockpit-176-4.el7.x86_64 cockpit-dashboard-176-4.el7.x86_64 cockpit-system-176-4.el7.noarch cockpit-ws-176-4.el7.x86_64 cockpit-ovirt-dashboard-0.12.0-1.el7ev.noarch cockpit-machines-ovirt-176-4.el7.noarch cockpit-bridge-176-4.el7.x86_64 virt-hosted-engine-setup-2.3.0-1.el7ev.noarch ovirt-hosted-engine-ha-2.3.0-1.el7ev.noarch firefox-62.0-2.fc28.x86_64 google-chrome-stable-68.0.3440.106-1.x86_64 How reproducible: 100% Steps to Reproduce: 1. Clean install redhat-virtualization-host-4.3-20190109.0.el7_6.x86_64.liveimg.squashfs 2. Login to http://<host IP>:9090 with root account 3. Go to Virtualization->hosted-engine 4. Click "Start" of Hosted Engine Actual results: Hosted engine wizard displays "System data could not be retrieved!" Expected results: Hosted engine should display wizard for setting without error Additional info: The issue occurs with Firefox and Chrome browsers
Created attachment 1519997 [details] Log file
It seams like RHVH specific. I didn't seen it happening on regular RHEL deployments.
(In reply to Nikolai Sednev from comment #3) > It seams like RHVH specific. I didn't seen it happening on regular RHEL > deployments.
No, it wasn't RHVH specific. It was descending from here: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/blob/master/defaults/main.yml#L65 In ovirt-ansible-hosted-engine-setup we have eth0 as a default so everything was fine if eth0 was on the host otherwise it was failing.
ovirt-hosted-engine-setup-2.3.2-1.el7ev.noarch ovirt-hosted-engine-ha-2.3.0-1.el7ev.noarch rhvm-appliance-4.3-20190115.0.el7.x86_64 I successfully deployed HE over NFS using ethernet interface different than eth0. Original error wasn't reproduced. Moving to verified.
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://access.redhat.com/errata/RHEA-2019:1050