VMware driver: Fix for invalid datastore selection
Added filter to ignore datastores that are not mounted, in-accessible
and read-only for volume creation. Without this VMware's VC/ESX driver can
choose such datastore with higher invalid capacity value as returned by the
server for volume creation.
Also using parent's self.mox object in the test cases rather than creating
a new mox.Mox obj everytime.
Reviewed: https:/ /review. openstack. org/44862 github. com/openstack/ cinder/ commit/ 564f8d140fd8a96 8e55b1aee57200b 9f015bee6d
Committed: http://
Submitter: Jenkins
Branch: master
commit 564f8d140fd8a96 8e55b1aee57200b 9f015bee6d
Author: Kartik Bommepally <email address hidden>
Date: Tue Sep 3 05:12:33 2013 -0700
VMware driver: Fix for invalid datastore selection
Added filter to ignore datastores that are not mounted, in-accessible
and read-only for volume creation. Without this VMware's VC/ESX driver can
choose such datastore with higher invalid capacity value as returned by the
server for volume creation.
Also using parent's self.mox object in the test cases rather than creating
a new mox.Mox obj everytime.
Fixes bug: 1220217
Change-Id: If8319562ddc11f c31eb928b3807ae ad2b11b94bc