Red Hat Bugzilla – Bug 598359
virt-manager doesn't create logical volumes on the first attempt
Last modified: 2010-06-14 14:03:29 EDT
Created attachment 418512 [details]
virt-manager --debug log, clearly showing the virt-manager problem.
Description of problem:
In RHEL 6 (and present git head), virt-manager doesn't create logical lvm volumes on the first attempt.
Instead it generates an error message (twice), and on the third attempt (no change to the details) the logical volume creation works and is usable.
Version-Release number of selected component (if applicable):
(and also tried against virt-manager compiled against git head, 0.8.4+)
Steps to Reproduce:
1. Use storage pool creation wizard to create a new logical volume, using a disk device (/dev/sdc) that is not presently known to lvm. (ie not in pvscan, etc). Ensure the "Build Pool" option is checked. This will fail with a misleading error claiming the source path hasn't been specified.
Screenshots 1 - 4.
2. After the above error message, uncheck the "Build Pool" option, then try again. This time it will fail with an error message saying the lvm group isn't found. (correct)
Screenshots 5 & 6.
3. After this second error message, check the "Build Pool" option again. The settings are now the same as in step 1. Additionally, it's worth noting that in this point pvscan and vgscan show no evidence of the device or volume group being in existence.
Now when the Finish button is clicked, the storage pool creation works.
Screenshots 7 - 9.
Storage volumes can now be created, as evidenced by screenshots 10 & 11.
Error message occurs for the first two attempts at logical storage pool creation. Storage pool creation works on the third attempt.
Storage pool creation to work on the first attempt.
Also attaching the virt-manager debug log for this session, and the libvirtd on the RHEL 6 server for this session.
Created attachment 418513 [details]
Created attachment 418514 [details]
Created attachment 418515 [details]
Created attachment 418517 [details]
Created attachment 418518 [details]
Created attachment 418519 [details]
Created attachment 418520 [details]
Created attachment 418521 [details]
Created attachment 418522 [details]
Created attachment 418525 [details]
Created attachment 418526 [details]
Created attachment 418527 [details]
The matching libvirtd log from this session.
Created attachment 418533 [details]
Ogg video of the error session, recorded with Gtk-RecordMyDesktop. Works with (at least) VLC media player.
Can you also provide the output of virt-manager --debug when reproducing? I'll try to reproduce myself.
Created attachment 418892 [details]
virt-manager --debug log
This is the capture of stdout and stderr, created with:
# virt-manager --debug 2>&1 | tee virt-manager-debug.log
Created attachment 418893 [details]
virt-manager --debug log, from the .virt-manager dir
This is the virt-manager.log from the .virt-manager directory, created from running virt-manager --debug
Created attachment 418894 [details]
libvirtd --verbose log, from the same session as the new virt-manager --debug logs
Cole, if it's any use it's easy to give you remote access (root and X11 enabled) to the server with this problem. (ie. ssh -Xl root somehost)
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
The main issue here is that pool build was broken for LVM and disk pools. There is another side issue in that LVM volume group enumeration is broken, which was making the wizard more confusing then it needed to be. Bug for that issue filed here:
Duping this to your disk pool bug, which is basically the same problem.
*** This bug has been marked as a duplicate of bug 597519 ***