[
https://issues.apache.org/jira/browse/CLOUDSTACK-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499121#comment-13499121
]
Marcus Sorensen commented on CLOUDSTACK-506:
--------------------------------------------
Hmm. Ok. I haven't done much with the UI, it could be a simple UI bug or it
could be a mistake in what is being passed back, or even something that fails
but sticks around in the database. Do you know if it actually works as primary
storage after this? I do fresh installs and perform this operation relatively
often with no issue, do you have a procedure to reproduce and perhaps some logs
around this time?
> Unable to execute API command liststoragepools
> ----------------------------------------------
>
> Key: CLOUDSTACK-506
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-506
> 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-0.12.1.2-2.295.el6_3.2.x86_64
> 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: http://www.atlassian.com/software/jira
