Bug 466015 - unable to use VG that is active unless name matches VG name
unable to use VG that is active unless name matches VG name
Product: Fedora
Classification: Fedora
Component: libvirt (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Daniel Veillard
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-10-07 14:16 EDT by Patrick C. F. Ernzer
Modified: 2009-11-18 08:42 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-11-18 08:42:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Patrick C. F. Ernzer 2008-10-07 14:16:35 EDT
Description of problem:
On your box I have one huge VG which hosts your rootfs and has Free PE

Version-Release number of selected component (if applicable):
package qemu is not installed

How reproducible:

Steps to Reproduce:
1. open add storage pool in virt-manager
2. select type LVM
3. give a name that is different from your existing VG
3. at target path give it your existing VG (obviously there must be Free PE in the VG)
Actual results:
no pool with matching namelibvir: Storage error : no pool with matching name

Expected results:
clearer UI

Additional info:
it works just fine if I give as name the actual name of my VG, but I suspect other users will run into this.

  - redo the dialogs so that one chooses a type first and no name in the first screen. in the second screen, if it's type LVM  offer a drop down of active VGs or the ability to create a new one
  - alternatively just document the bahavious _in the dialog_
Comment 1 Bug Zapper 2008-11-25 22:38:34 EST
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
Comment 2 Bug Zapper 2009-11-18 04:17:18 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Cole Robinson 2009-11-18 08:42:25 EST
Libvirt does have this capability, by specifying:


in the pool XML. This is also supported by upstream virt-manager, though I don't think it will be backported to F10, so just closing as UPSTREAM.

Note You need to log in before you can comment on or make changes to this bug.