incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Iliya (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-506) Unable to execute API command liststoragepools
Date Sat, 17 Nov 2012 19:58:11 GMT


Iliya commented on CLOUDSTACK-506:

This was a fresh installation

>Do you know if it actually works as primary storage after this?
yes, i run console proxy and storage on this primary storage.

>do you have a procedure to reproduce and perhaps some logs around this time? 
1. Create 2 managment server 
2. Create Master-Master SQL Server I'm using Percona-Server-server-55-5.5.28-rel29.1.335.rhel6.x86_64
3. Create 2 node RHCS cluster with CLVM 
4. Create volume group on shared iSCSI disk (with multipathing) 
5. Create the zone.
6. Create KVM cluster 
7. Create primary storage (using a VG from the previous step)
8. this bug
what logs are needed? 
> Unable to execute API command liststoragepools
> ----------------------------------------------
>                 Key: CLOUDSTACK-506
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>          Components: KVM, Storage Controller, Volumes
>    Affects Versions: 4.0.0
>         Environment: CentOS 6.3 
> kernel-2.6.32-279.14.1.el6.x86_64
> lvm2-2.02.95-10.el6_3.2.x86_64
> lvm2-cluster-2.02.95-10.el6_3.2.x86_64
> lvm2-libs-2.02.95-10.el6_3.2.x86_64
> qemu-kvm-
> libvirt-0.9.10-21.el6_3.5.x86_64
> libvirt-client-0.9.10-21.el6_3.5.x86_64
>            Reporter: Iliya
>            Priority: Minor
>         Attachments: error.png
> When i try add the primary storage (CLVM). I get an error , such as 
> Unable to execute API command liststoragepools due to invalid value. Obhect storage_pool(uuid:
undefined) does not exist.  And there is no information about the newly added primary storage.
> But if i reload the page, the primary storage displayed normally.
> I attached screenshot  

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message