Hyper-V cannot attach volumes when the host is an AD member
Bug #1328870 reported by
Lucian Petrut
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Lucian Petrut | ||
Havana |
Fix Released
|
Undecided
|
Unassigned | ||
Icehouse |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The domain name gets added to the initiator name used by the host when it's an AD member. The method which automatically gets the initiator name when this is not set in the registry does not take this into account. Trying to use a wrong initiator name will lead to an exception when trying to log in to the according iSCSI target.
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in nova: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
https:/ /review. openstack. org/#/c/ 99367/