You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wido den Hollander (JIRA)" <ji...@apache.org> on 2013/05/15 14:03:15 UTC
[jira] [Resolved] (CLOUDSTACK-2515) KVM Agent iterates all libvirt
storage pools and hits a nullpointer exception on RBD pools
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wido den Hollander resolved CLOUDSTACK-2515.
--------------------------------------------
Resolution: Fixed
Fix Version/s: (was: 4.1.1)
4.1.0
Fixed in 68a428f84dea9c051456882d6762f419c40d90db
> KVM Agent iterates all libvirt storage pools and hits a nullpointer exception on RBD pools
> ------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2515
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2515
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: KVM
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Wido den Hollander
> Assignee: Wido den Hollander
> Priority: Blocker
> Fix For: 4.1.0
>
>
> Commit 6928679ba834bb8bb404d6e87c07f34a6f047884 made storage pools non-persistent, but it also makes the assumption that every storage pool has a targetPath eg, where it is mounted.
> RBD storage pools do not have this and when LibvirtStorageAdapter iterates all pools it does a check on the targetPath, which leads to a NullPointerException on RBD pools.
> The piece of code:
> StoragePool p = conn.storagePoolLookupByName(poolname);
> LibvirtStoragePoolDef pdef = getStoragePoolDef(conn, p);
> if (pdef.getTargetPath().equals(path)) {
> ..
> }
> This is a BLOCKER for 4.1, since it doesn't allow you to deploy from ISO's when you have a RBD storage pool, even when you are not deploying on that pool.
> Link to the commit: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=6928679ba834bb8bb404d6e87c07f34a6f047884
--
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