yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53353
[Bug 1288360] Re: FibreChannel detach fails with missing devices key
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: Low => Undecided
** Changed in: nova
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1288360
Title:
FibreChannel detach fails with missing devices key
Status in OpenStack Compute (nova):
Expired
Bug description:
When a FibreChannel volume is a boot volume, the devices key and data
isn't saved in the block_device_mapping in the database. This causes
a problem at detach time because the libvirt volume FC driver tries to
access the key to determine which LUNs in the kernel to remove.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1288360/+subscriptions
References