Bug 698529 - virt-manager can not create lvm pool if not ues vg_name
Summary: virt-manager can not create lvm pool if not ues vg_name
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager
Version: 5.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-21 06:51 UTC by Huang Wenlong
Modified: 2013-10-20 21:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-12 23:14:47 UTC
Target Upstream Version:

Attachments (Terms of Use)
error-message (115.77 KB, image/png)
2011-04-21 06:55 UTC, Huang Wenlong 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Huang Wenlong 2011-04-21 06:51:56 UTC 
Description of problem:
virt-manager can not create lvm pool if not ues vg_name 
virt-manager will run the vgchanage -ay "pool_name" , if the "pool_name" is a not exist vg,it will show up error message .
I will attatch the screenshot 


Version-Release number of selected component (if applicable):
virt-manager-0.6.1-13.el5

How reproducible:
100%

Steps to Reproduce:
1. open virt-manager
2. enter "Details" => "Storage" => "add Storage pool" => "input a name (not any of vg_name)" =>forward 
3. choose the correct vg path then click "Finish "
  
Actual results:
show up the error windows 

Expected results:
create lvm pool successfully 

Additional info:

virt-manager-0.8.4-8.el6.noarch in rhel6 is fine
Comment 1 Huang Wenlong 2011-04-21 06:55:35 UTC 
Created attachment 493717 [details]
error-message
Comment 2 Cole Robinson 2011-07-12 23:14:47 UTC 
Backporting the required fix for this would be too invasive at this point in RHEL5. Users will have to create the pool XML by hand and specify <source name='vgname'/>. This is already fixed in RHEL5

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