VMware: should not take the first host found in the cluster to perform iSCSI related operations

Bug #1325789 reported by Arnaud Legendre
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned
VMwareAPI-Team
New
Undecided
Unassigned

Bug Description

When attaching an iSCSI volume, Nova triggers a HBA scan in order to
find the static targets and indirectly populate the SCSI topology in
vCenter.
The current implementation takes the first host found as the host to
perform the scan. This doesn't take into account the fact that the VM
can run on another host. This is problematic because then the host
where the VM is running is not aware of the target that the VM is
supposed to be attached to.

See: http://<email address hidden>/msg25648.html for more details

Tags: vmware
Changed in nova:
assignee: nobody → Arnaud Legendre (arnaudleg)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
status: New → In Progress
Gary Kotton (garyk)
Changed in nova:
importance: Undecided → High
tags: added: icehouse-backport-potential vmware
summary: - VMware: vm_util.get_host_ref() should take into account where the VM is
- located
+ VMware: should not take the first host found in the cluster to perform
+ iSCSI related operations
description: updated
Changed in nova:
assignee: Arnaud Legendre (arnaudleg) → Davanum Srinivas (DIMS) (dims-v)
Changed in nova:
assignee: Davanum Srinivas (DIMS) (dims-v) → nobody
Changed in nova:
status: In Progress → Confirmed
Changed in nova:
assignee: nobody → Gary Kotton (garyk)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Arnaud Legendre (<email address hidden>) on branch: master
Review: https://review.openstack.org/97612
Reason: Abandon this patch for now. We need to come with a complete solution to the problem

Changed in nova:
status: In Progress → Confirmed
Alan Pevec (apevec)
tags: removed: icehouse-backport-potential
Changed in nova:
assignee: Gary Kotton (garyk) → nobody
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in nova:
importance: High → Undecided
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.