Description of problem: $Summary Version-Release number of selected component (if applicable): Current master How reproducible: Not sure, I think always Steps to Reproduce: 1. Stop libvirtd (or perhaps also break it. For actual flow see bug 1528813). 2. Start deploy 3. Actual results: CPU type drop-down has only AMD CPUs. Expected results: Not sure - either both Intel and AMD or show a message "Failed to get list of CPUs from libvirtd, please check" Additional info:
Created attachment 1378485 [details] libvirtd_running_cpu
Created attachment 1378486 [details] libvirtd_stop_cpu
Can reproduce. Test version: cockpit-ovirt-dashboard-0.11.3-0.1.el7ev.noarch rhvh-4.2.0.6-0.20180104.0+1 Test steps: 1. Install the latest rhvh4.2 2. Check the libvirtd status, deploy SHE via cockpit, then check the cpu type 3. Stop the libvirtd service, deploy SHE via cockpit, then check the cpu type Test results: With libvirtd running: https://bugzilla.redhat.com/attachment.cgi?id=1378485 With libvirtd stop: https://bugzilla.redhat.com/attachment.cgi?id=1378486
I actually can't reproduce this. With libvirt stopped, the wizard fails to load (problems on the JS console). Either way, we can do better. I'll write a patch.
*** Bug 1543082 has been marked as a duplicate of this bug. ***
Can we move this to modified?
Works for me on these components: cockpit-ovirt-dashboard-0.11.12-0.1.el7ev.noarch rhvm-appliance-4.2-20180202.0.el7.noarch ovirt-hosted-engine-ha-2.2.6-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.11-1.el7ev.noarch Linux alma03.qa.lab.tlv.redhat.com 3.10.0-855.el7.x86_64 #1 SMP Tue Feb 20 06:46:45 EST 2018 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.5 Beta (Maipo) I've turned off libvirtd service and checked that it was stopped on host, then started UI NGN on host and received proper CPU Intel family. Then checked on host and seen that libvirtd service was running. Moving to verified.
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.