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.
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.
Created redmine issue http://projects.theforeman.org/issues/20174 from this bug
Upstream bug assigned to mhulan
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 -------------------------------------------
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20174 has been resolved.
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.
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