VMware: nova ignores cinder volume mappings

Bug #1490257 reported by Gary Kotton on 2015-08-30
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Gary Kotton

Bug Description

When booting from a volume the Nova driver ignores the cinder 'storage_policy' and moves the volume to the datastore that nova selected. Nova should use the cinder datastore

Gary Kotton (garyk) on 2015-08-30
Changed in nova:
assignee: nobody → Gary Kotton (garyk)
tags: added: kilo-backport-potential vmware
Changed in nova:
status: New → In Progress

Fix proposed to branch: master
Review: https://review.openstack.org/220085

Reviewed: https://review.openstack.org/220085
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aadc18d883281d9f5e6b23a619056d83f8bdfc4c
Submitter: Jenkins
Branch: master

commit aadc18d883281d9f5e6b23a619056d83f8bdfc4c
Author: Gary Kotton <email address hidden>
Date: Thu Sep 3 03:50:30 2015 -0700

    VMware: add method for getting hosts attached to datastore

    Add in a method that returns hosts attached to a datastore. This will
    enable us to validate if the cinder volume is accessible by a running
    instance.

    Change-Id: I840ffda4926cea879d5945886ba87da72fc90805
    Partial-bug: #1490257

description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers