Bug 1528818

Summary: If libvirtd is down, we allow only AMD CPUs
Product: [oVirt] cockpit-ovirt Reporter: Yedidyah Bar David <didi>
Component: Hosted EngineAssignee: Phillip Bailey <phbailey>
Status: CLOSED CURRENTRELEASE QA Contact: Yihui Zhao <yzhao>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 0.11.3CC: bugs, cshao, huzhao, nsednev, qiyuan, rbarry, sbonazzo, stirabos, yaniwang, ycui, yzhao
Target Milestone: ovirt-4.2.2Keywords: Triaged
Target Release: 0.11.12Flags: rule-engine: ovirt-4.2+
ycui: testing_plan_complete?
sbonazzo: devel_ack+
yzhao: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.11.12-0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:05:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1522712    
Attachments:
Description Flags
libvirtd_running_cpu
none
libvirtd_stop_cpu none

Description Yedidyah Bar David 2017-12-24 11:57:00 UTC 
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:
Comment 1 Yihui Zhao 2018-01-08 11:38:09 UTC 
Created attachment 1378485 [details]
libvirtd_running_cpu
Comment 2 Yihui Zhao 2018-01-08 11:39:11 UTC 
Created attachment 1378486 [details]
libvirtd_stop_cpu
Comment 3 Yihui Zhao 2018-01-08 11:42:34 UTC 
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
Comment 4 Ryan Barry 2018-02-07 18:07:45 UTC 
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.
Comment 5 Ryan Barry 2018-02-08 12:14:16 UTC 
*** Bug 1543082 has been marked as a duplicate of this bug. ***
Comment 6 Simone Tiraboschi 2018-02-21 18:32:47 UTC 
Can we move this to modified?
Comment 7 Nikolai Sednev 2018-02-22 18:00:24 UTC 
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.
Comment 8 Sandro Bonazzola 2018-03-29 11:05:40 UTC 
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.