Bug 1465154

Summary: "No storage pools are defined" when attempting to edit libvirt compute profile
Product: Red Hat Satellite Reporter: jcallaha
Component: Compute Resources - libvirtAssignee: Marek Hulan <mhulan>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: bkearney, cpatters, egolov, inecas, jcallaha, mhulan, oshtaier, sgraessl, tbrisker
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-1.15.6.9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:59:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
page load error none

Description jcallaha 2017-06-26 19:52:38 UTC
Created attachment 1292056 [details]
page load error

Description of problem:
When attempting to edit a libvirt compute profile, the page presents an error:
"Oops, we're sorry but something went wrong No storage pools are defined".
There are also two 500 ISEs in the web console. (see attached)

Version-Release number of selected component (if applicable):
Satellite 6.3 Snap 4

How reproducible:
Always

Steps to Reproduce:
1. Setup a libvirt compute resource
2. Navigate to the compute profiles page
3. Click one of the three pre-made options, then the libvirt CR

Actual results:
The page does not load correctly. See attached.

Expected results:
The page loads correctly, and you are able to edit the compute resource.

Comment 3 Marek Hulan 2017-06-30 08:43:47 UTC
I'm unable to reproduce this, it works just fine for my libvirt. I was only able to reproduce if I deactivated all storage pools. Could you double check your libvirt has a storage pool defined and active? Please paste the output of

    sudo virsh pool-list

If that's the cause, I think this is not a blocker but I think we should improve the error messaging to better explain what's going on. It should perhaps do the check also when creating the CR. There's probably no point of creating libvirt CR without the storage pool.

Please update blocker flag and move to satellite-backlog according to your findings, thank you.

Comment 4 Marek Hulan 2017-06-30 10:59:21 UTC
Created redmine issue http://projects.theforeman.org/issues/20174 from this bug

Comment 5 Satellite Program 2017-06-30 12:04:39 UTC
Upstream bug assigned to mhulan

Comment 6 Satellite Program 2017-06-30 12:04:42 UTC
Upstream bug assigned to mhulan

Comment 7 jcallaha 2017-06-30 19:13:00 UTC
Marek, it looks like you are spot on. There are no pools listed as shown below. I will update the title to reflect that the error message should be updated.

[root@cloud-qe-22 ~]# virsh pool-list
 Name                 State      Autostart 
-------------------------------------------

Comment 8 Satellite Program 2017-07-03 20:05:59 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20174 has been resolved.

Comment 10 Peter Ondrejka 2017-11-20 09:15:17 UTC
Verified on Sat 6.3 snap 25, the "no storage pool available on hypervisor" warning is displayed instead of error when assigning a compute profile and when creating a host.

Comment 11 Bryan Kearney 2018-02-21 16:59:24 UTC
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/RHSA-2018:0336