[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: cloud-archive Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: cinder Milestone: grizzly-1 => 2013.1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
This bug was fixed in the package nova - 2012.2.1+stable-20121212 -a99a802e-0ubuntu1 --- nova (2012.2.1+stable-20121212-a99a802e-0ubuntu1) quantal-proposed; urgency=low * Ubuntu updates: - debian/control: Ensure novaclient is upgraded with nova, require python-keystoneclient >= 1:2.9.0. (LP: #1073289) - d/p/avoid_setuptools_git_dependency.patch: Refresh. * Dropped patches, applied upstream: - debian/patches/CVE-2012-5625.patch: [a99a802] * Resynchronize with stable/folsom (b55014ca) (LP: #1085255): - [a99a802] create_lvm_image allocates dirty blocks (LP: #1070539) - [670b388] RPC exchange name defaults to 'openstack' (LP: #1083944) - [3ede373] disassociate_floating_ip with multi_host=True fails (LP: #1074437) - [22d7c3b] libvirt imagecache should handle shared image storage (LP: #1075018) - [e787786] Detached and deleted RBD volumes remain associated with insance (LP: #1083818) - [9265eb0] live_migration missing migrate_data parameter in Hyper-V driver (LP: #1066513) - [3d99848] use_single_default_gateway does not function correctly (LP: #1075859) - [65a2d0a] resize does not migrate DHCP host information (LP: #1065440) - [102c76b] Nova backup image fails (LP: #1065053) - [48a3521] Fix config-file overrides for nova-dhcpbridge - [69663ee] Cloudpipe in Folsom: no such option: cnt_vpn_clients (LP: #1069573) - [6e47cc8] DisassociateAddress can cause Internal Server Error (LP: #1080406) - [22c3d7b] API calls to dis-associate an auto-assigned floating IP should return proper warning (LP: #1061499) - [bd11d15] libvirt: if exception raised during volume_detach, volume state is inconsistent (LP: #1057756) - [dcb59c3] admin can't describe all images in ec2 api (LP: #1070138) - [78de622] Incorrect Exception raised during Create server when metadata over 255 characters (LP: #1004007) - [c313de4] Fixed IP isn't released before updating DHCP host file (LP: #1078718) - [f4ab42d] Enabling Return Reservation ID with XML create server request returns no body (LP: #1061124) - [3db2a38] 'BackupCreate' should accept rotation parameter greater than or equal to zero (LP: #1071168) - [f7e5dde] libvirt reboot sometimes fails to reattach volumes (LP: #1073720) - [ff776d4] libvirt: detaching volume may fail while terminating other instances on the same host concurrently (LP: #1060836) - [85a8bc2] Used instance uuid rather than id in remove-fixed-ip - [42a85c0] Fix error on invalid delete_on_termination value - [6a17579] xenapi migrations fail w/ swap (LP: #1064083) - [97649b8] attach-time field for volumes is not updated for detach volume (LP: #1056122) - [8f6a718] libvirt: rebuild is not using kernel and ramdisk associated with the new image (LP: #1060925) - [fbe835f] live-migration and volume host assignement (LP: #1066887) - [c2a9150] typo prevents volume_tmp_dir flag from working (LP: #1071536) - [93efa21] Instances deleted during spawn leak network allocations (LP: #1068716) - [ebabd02] After restarting an instance volume is lost (LP: #1071069) - [a369303] xen volume auto device selection always picks xvdb (LP: #1061944) - [8d1095c] Calls to to_xml() to generate XML for a soft deleted flavor fail (LP: #1073736) - [1857821] nova-manage doesn't validate the key value supplied to update the quota (LP: #1064359) - [6ae32f0] Compute manager doesn't update 'host' field when it tries to run a VM (LP: #1073600) - [284f6ea] Host field set too early during builds (LP: #1060255) - [395511f] finish_resize failures result in NoneType exception (LP: #1071595) - [85ccf80] confirm_resize mgr call requires admin context (LP: #1071600) - [2dceffa] Only return the last N lines of the console log (LP: #1081436) - [9c7a711] console auth does not work with memcache, unicode error (LP: #1057279) - [b27f7ef] disk path not exists when using LXC with libvirt_images_type=lvm (LP: #1079113) - [1351c6b] nova-api now requires quantumclient (LP: #1070509) - [612f404] nova-api now requires quantumclient (LP: #1070509) - [7e8a166] nova-compute (folsom) fails to start, compute_driver is None (LP: #1081836) - [182ca80] Nova API does not work with QuantumV2 API subclasses (LP: #1070045) - [55d1412] 413 error code doesn't always provide Retry-After (LP: #1079387) - [1581505] Snapshotting LXC instance fails (LP: #1058273) - [197398f] Stop network.api import on network import - [b874d21] Scheduler Race Condition at high volume (LP: #1073956) - [3316e1f] Nic Ordering not guaranteed with Quantum API (LP: #1064524) - [ab7e37e] Stable oslo (aka common) update - [3f7788c] update nova to report quantum floating IPs (LP: #1023169) - [d3fd05b] metadata service throws 500
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
This bug was fixed in the package cinder - 2012.2.1-0ubuntu1 --- cinder (2012.2.1-0ubuntu1) quantal-proposed; urgency=low * Ubuntu updates: - Cinder should suggest ceph-common, not python-ceph (LP: #1065901): - debian/control: cinder-volume Suggests: python-ceph -> ceph-common * Resynchronize with stable/folsom (87d839a5) (LP: #1085255): - [f990ff0] Remove unused python-daemon dependency - [940f363] Detached and deleted RBD volumes remain associated with insance (LP: #1083818) - [7f34ba3] After folsom upgrade, instances can no longer access existing volumes. (LP: #1065702) - [1c99b24] Jenkins jobs fail because of incompatibility between sqlalchemy- migrate and the newest sqlalchemy-0.8.0b1 (LP: #1073569) - [d12d4b6] Add SIGPIPE handler to subprocess execution in rootwrap and utils.execute (LP: #1053364) - [ce5e002] Set defaultbranch in .gitreview to stable/folsom -- Adam GandelmanTue, 04 Dec 2012 09:19:29 -0800 ** Changed in: cinder (Ubuntu Quantal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Tags removed: in-stable-folsom -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Branch linked: lp:ubuntu/quantal-proposed/nova -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
Hello Adam, or anyone else affected, Accepted nova into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nova/2012.2.1+stable-20121212 -a99a802e-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nova (Ubuntu Quantal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Branch linked: lp:ubuntu/quantal-proposed/cinder -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
Hello Adam, or anyone else affected, Accepted cinder into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cinder/2012.2.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cinder (Ubuntu Quantal) Status: Confirmed => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: nova (Ubuntu Raring) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: nova/folsom Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: cinder/folsom Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-folsom -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Branch linked: lp:~openstack-ubuntu-testing/cinder/precise-folsom -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: cinder Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: nova/folsom Milestone: None => 2012.2.1 ** Changed in: cinder/folsom Milestone: None => 2012.2.1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: cloud-archive Importance: Undecided => High ** Changed in: cloud-archive Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: nova (Ubuntu Quantal) Status: New => Confirmed ** Tags added: cloud-archive -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-folsom- proposed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Branch linked: lp:~openstack-ubuntu-testing/nova/quantal-folsom- proposed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Also affects: nova/folsom Importance: Undecided Status: New ** Changed in: nova Status: In Progress => Invalid ** Changed in: nova/folsom Status: New => Fix Committed ** Changed in: nova/folsom Importance: Undecided => High ** Changed in: nova/folsom Assignee: (unassigned) => John Griffith (john-griffith) ** Also affects: cinder/folsom Importance: Undecided Status: New ** Changed in: cinder/folsom Importance: Undecided => High ** Changed in: cinder/folsom Status: New => Fix Committed ** Changed in: cinder/folsom Assignee: (unassigned) => John Griffith (john-griffith) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
Cinder Fix in Raring as of 2013.1~g1~20121101.361-0ubuntu1 ** Also affects: cinder (Ubuntu) Importance: Undecided Status: New ** Changed in: cinder (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Also affects: nova (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: cinder (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: nova (Ubuntu Raring) Importance: High Status: Confirmed ** Also affects: cinder (Ubuntu Raring) Importance: Undecided Status: Fix Released ** Changed in: cinder (Ubuntu Quantal) Status: New => Confirmed ** Changed in: cinder (Ubuntu Quantal) Importance: Undecided => Critical ** Changed in: cinder (Ubuntu Quantal) Importance: Critical => High ** Changed in: nova (Ubuntu Quantal) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Branch linked: lp:~openstack-ubuntu-testing/cinder/quantal-folsom- proposed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
Reviewed: https://review.openstack.org/15157 Committed: http://github.com/openstack/cinder/commit/7f34ba39abcaa4f885d7448b427148fab4e49892 Submitter: Jenkins Branch:stable/folsom commit 7f34ba39abcaa4f885d7448b427148fab4e49892 Author: John Griffith 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 Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
Reviewed: https://review.openstack.org/14790 Committed: http://github.com/openstack/cinder/commit/524c7fa6dfade6efcabda19b105d58cab8c434e2 Submitter: Jenkins Branch:master commit 524c7fa6dfade6efcabda19b105d58cab8c434e2 Author: John Griffith Date: Wed Oct 24 16:28:02 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: I8224824b793c98a9767c5d8dd741d892be720c4f Fixes: bug 1065702 ** Changed in: cinder Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: cinder Milestone: None => grizzly-1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: cinder Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
Fix proposed to branch: master Review: https://review.openstack.org/14615 ** Changed in: nova Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: nova (Ubuntu) Status: New => Confirmed ** Changed in: nova Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
I used the block_device_mapping table to figure out what to rename. Just throwing that out there for people who need to change their existing volumes before a fix is put out. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: cinder Assignee: (unassigned) => John Griffith (john-griffith) ** Changed in: nova Assignee: (unassigned) => John Griffith (john-griffith) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
Looks like migrations for block_device_mapping:connection_info and volumes:provider_location are the two that are missing. Looking at a possible solution. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Tags added: openstack-ubuntu-upgrade -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Also affects: cinder Importance: Undecided Status: New ** Changed in: cinder Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
ugh, this is nasty. Looks like we need a migration for this. For backport we could add a translation using the ec2_id table to convert from the old name to the new one. Some testing needs to be done to figure out if the new iqns are actually there in all cases or if there is a case where the old iqn will exist. ** Changed in: nova Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in 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/nova/+bug/1065702/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
