FibreChannel detach fails with missing devices key

[Walt Boring]

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.

[OpenStack Infra (hudson-openstack)]

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

[Xing Yang (xing-yang)]

Walt, this is fix now, right?

[Yang Ye (ccyangye)]

I think this is because FCSAN is the only driver that will update connection_info in connect_volume(volume.py).
In live-migration, pre_live_migration will refresh connection_info in destination host, and saved to db before do connect_volume.
So live-migration will lost devices&device_path info, but I'm not sure why FCSAN need to update in connection_volume.

IMO, we should update connecion_info after connect_volume and refresh again in _rollback_live_migration at source host when failed.

[Yang Ye (ccyangye)]

Btw, could anyone tell me the meaning of connection_info?

[Markus Zoeller (markus_z) (mzoeller)]

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