The cluster driver shouldn't accept iSCSI/FC volumes
Bug #1749958 reported by
Lucian Petrut
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| compute-hyperv |
Fix Released
|
Undecided
|
Lucian Petrut | ||
Bug Description
There are critical known issues related to the cluster driver and passthrough disks. When an instance is failed over, the instance attached volumes need to be accessible on the destination host. This will not happen transparently for such disks, for which reason the instance may bounce between a few nodes and then end up in error state, basically defeating the purpose of the cluster driver.
The cluster driver shouldn't accept attaching iSCSI/FC Cinder volumes.
| Changed in compute-hyperv: | |
| assignee: | nobody → Lucian Petrut (petrutlucian94) |
| Changed in compute-hyperv: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to compute-hyperv (master) | #1 |
| Changed in compute-hyperv: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 937aa55ffa0deef
Author: Lucian Petrut <email address hidden>
Date: Fri Feb 16 15:18:46 2018 +0200
Cluster driver: Blacklist iSCSI/FC volume drivers
There are critical known issues related to the cluster driver and
passthrough disks.
When an instance is failed over, the instance attached volumes need
to be accessible on the destination host. This will not happen
transparently for such disks, for which reason the instance may
bounce between a few nodes and then end up in error state,
basically defeating the purpose of the cluster driver.
This change ensures that the Hyper-V Cluster driver rejects
iSCSI/FC Cinder volumes, raising an error that describes possible
alternatives.
Closes-Bug: #1749958
Change-Id: I231b51c648e134