Bug #20174

"No storage pools are defined" when attempting to edit libvirt compute profile

Added by Marek Hulán 10 months ago. Updated 10 months ago.

Status:Closed
Priority:Normal
Assigned To:Marek Hulán
Category:Compute resources - libvirt
Target version:-
Difficulty: Bugzilla link:1465154
Found in release: Pull request:https://github.com/theforeman/foreman/pull/4633
Story points-
Velocity based estimate-
Release1.16.0Release relationshipAuto

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1465154

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 / Foreman nightly

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.

Additional info:

The problem can be observed when there's no libvirt storage pool active. We should be able to detect this and display proper message both at compute profile page as well as in host form during provisioning.

Associated revisions

Revision 3cf9d65f
Added by Marek Hulán 10 months ago

Fixes #20174 - handle no storage pool gracefully

History

#1 Updated by The Foreman Bot 10 months ago

  • Status changed from New to Ready For Testing
  • Assigned To set to Marek Hulán
  • Pull request https://github.com/theforeman/foreman/pull/4633 added

#2 Updated by Daniel Lobato Garcia 10 months ago

  • Subject changed from "No storage pools are defined" when attempting to edit libvirt compute profile to "No storage pools are defined" when attempting to edit libvirt compute profile
  • Release set to 1.16.0

#3 Updated by Anonymous 10 months ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF