[Ovirt-devel] [PATCH 1/2] Provides a new storage administration system to the managed node.

Darryl L. Pierce dpierce at redhat.com
Mon Nov 9 20:04:00 UTC 2009


On Mon, Nov 09, 2009 at 02:54:50PM -0500, Joey Boggs wrote:
> ACK pending below comments:
>
> For lvm -It  creates a pool fine, when creating a volume its missing the  
> volume group name when running lvcreate
>
> +-----+ An Exception Has Occurred +-----+
> Couldn't create storage volume '1.img': 'internal error  '/sbin/lvcreate  
> --name 1.img -L 1024K /tmp/lvm' exited with non-zero status 3 and signal 
> 0
> Volume group name expected (no slash) Run `lvcreate --help' for more  
> information.   

Does the same thing happen with virt-manager when doing the same thing?

> iscsi creates a pool fine but when you reach creating a volume it tells  
> you it's no implemented, any way to block this option for even being  
> available or alert the user ahead of time?
>
>
> All the other options create pools/volumes fine

I'm not sure if there's an easy way to block it without forcing us to
have to do an upgrade later when it's implemented. When I first saw
that, I double checked virt-manager and it's doing the same thing,
giving an error that the iSCSI pool is not available. So at least in
that way we're consistent.

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20091109/d88d706a/attachment.sig>


More information about the ovirt-devel mailing list