Reviewed: https://review.openstack.org/15157
Committed:
http://github.com/openstack/cinder/commit/7f34ba39abcaa4f885d7448b427148fab4e49892
Submitter: Jenkins
Branch: stable/folsom
commit 7f34ba39abcaa4f885d7448b427148fab4e49892
Author: John Griffith <john.griff...@solidfire.com>
Date: Wed Oct 31 16:43:09 2012 -0600
Detect and fix issues caused by vol ID migration
The migration from volume ID to UUID neglected to update the
provider_location
field on the volume. As a result the iqn and volume name no long match and
existing volumes are no longer able to be attached after an upgrade
(essex -> folsom and then nova-vol->cinder).
This patch adds a method to the volume driver that will check for the
mismatch of volume name in the iqn during service start up. If
detected it will update the provider_location field in the database
to include the new ID. Also it will create a symlink to the device backing
file that also has the correct naming convention.
Note: We don't disturb an connections that are currently attached.
For this case we add a check in manager.detach and do any provider_location
cleanup that's needed at that time. This ensures that connections
persist on restarts of tgtd and reboot.
Change-Id: I4683df4ef489972752dc58cb4e91d458a79a8ef2
Fixes: bug 1065702enter the commit message for your changes. Lines starting
** Tags added: in-stable-folsom
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1065702/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
