[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
I'm using Openstack-ansible 18.1.8 to deploy Horizon. Where I use the source for the application. In the installed code I also see that this has not been fixed in the 18.1.8. At what version of OSA has this been fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Changed in: horizon (Ubuntu Xenial) Assignee: Eric Desrochers (slashd) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
This bug was fixed in the package horizon - 3:13.0.1-0ubuntu6~cloud0 --- horizon (3:13.0.1-0ubuntu6~cloud0) xenial-queens; urgency=medium . * New update for the Ubuntu Cloud Archive. . horizon (3:13.0.1-0ubuntu6) bionic; urgency=medium . * d/p/drop-devicename-creating-server-with-image-boot-to-volume.patch: When creating a server using an image boot source to new volume, horizon specified device_name 'vda'. If for instance we use an image with disk_bus type scsi, horizon will name the device_name as 'vda' when it should be 'sda'. As per BDMv2 documentation, it's best to not specify device_name. (LP: #1822129) ** Changed in: cloud-archive/queens Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
This bug was fixed in the package horizon - 3:14.0.2-0ubuntu4~cloud0 --- horizon (3:14.0.2-0ubuntu4~cloud0) bionic-rocky; urgency=medium . * New update for the Ubuntu Cloud Archive. . horizon (3:14.0.2-0ubuntu4) cosmic; urgency=medium . * d/p/*-monkey-patching-for-APITestCase.patch: Cherry-picked from upstream stable/rocky branch to fix unit tests for plugin dashboards (LP: #1806053). . horizon (3:14.0.2-0ubuntu3) cosmic; urgency=medium . * d/p/drop-devicename-creating-server-with-image-boot-to-volume.patch: When creating a server using an image boot source to new volume, horizon specified device_name 'vda'. If for instance we use an image with disk_bus type scsi, horizon will name the device_name as 'vda' when it should be 'sda'. As per BDMv2 documentation, it's best to not specify device_name. (LP: #1822129) ** Changed in: cloud-archive/rocky Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
This bug was fixed in the package horizon - 3:12.0.3-0ubuntu1~cloud2 --- horizon (3:12.0.3-0ubuntu1~cloud2) xenial-pike; urgency=medium . * d/p/drop-devicename-creating-server-with-image-boot-to-volume.patch: When creating a server using an image boot source to new volume, horizon specified device_name 'vda'. If for instance we use an image with disk_bus type scsi, horizon will name the device_name as 'vda' when it should be 'sda'. As per BDMv2 documentation, it's best to not specify device_name. (LP: #1822129) ** Changed in: cloud-archive/pike Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
This bug was fixed in the package horizon - 3:14.0.2-0ubuntu4 --- horizon (3:14.0.2-0ubuntu4) cosmic; urgency=medium * d/p/*-monkey-patching-for-APITestCase.patch: Cherry-picked from upstream stable/rocky branch to fix unit tests for plugin dashboards (LP: #1806053). horizon (3:14.0.2-0ubuntu3) cosmic; urgency=medium * d/p/drop-devicename-creating-server-with-image-boot-to-volume.patch: When creating a server using an image boot source to new volume, horizon specified device_name 'vda'. If for instance we use an image with disk_bus type scsi, horizon will name the device_name as 'vda' when it should be 'sda'. As per BDMv2 documentation, it's best to not specify device_name. (LP: #1822129) -- Corey Bryant Thu, 09 May 2019 14:49:48 -0400 ** Changed in: horizon (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: horizon (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
This bug was fixed in the package horizon - 3:13.0.1-0ubuntu6 --- horizon (3:13.0.1-0ubuntu6) bionic; urgency=medium * d/p/drop-devicename-creating-server-with-image-boot-to-volume.patch: When creating a server using an image boot source to new volume, horizon specified device_name 'vda'. If for instance we use an image with disk_bus type scsi, horizon will name the device_name as 'vda' when it should be 'sda'. As per BDMv2 documentation, it's best to not specify device_name. (LP: #1822129) -- Eric Desrochers Wed, 17 Apr 2019 09:42:39 +0100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
[VERIFICATION COSMIC] I deployed a openstack env (including the horizon package found in cosmic-proposed: 14.0.2-0ubuntu4) [Test #1] Expected result: /dev/sda * Updated an image with the right metadata values: $ glance image-update --property hw_disk_bus='scsi' --property hw_scsi_model='virtio-scsi' * Launched an instance using the image updated above * Instance overview revealed: Volumes Attached b326f759-1cf5-409f-b7a5-0e19cbfd6232 on /dev/sda As expected ^ I confirm the fix works as expected for boot to image instance launch [Test #2] Expected result : /dev/vda * Launched an instance using the image without metadata value. * Instance overview revealed: Volumes Attached f18b6ad2-a18a-46ac-9c7e-33b55cd9f243 on /dev/vda ** Tags removed: verification-needed-cosmic verification-rocky-needed ** Tags added: verification-done-cosmic verification-rocky-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
[VERIFICATION BIONIC] I deployed a openstack env (including the horizon package found in bionic-proposed) [Test #1] Expected result: /dev/sda * Updated an image with the right metadata values: $ glance image-update --property hw_disk_bus='scsi' --property hw_scsi_model='virtio-scsi' * Launched an instance using the image updated above * Instance overview revealed: Volumes Attached Attached To ffbac3d9-ceea-4277-9878-7402bb7ba91c on /dev/sda As expected ^ I confirm the fix works as expected for boot to image instance launch [Test #2] Expected result : /dev/vda * Launched an instance using the image without metadata value. * Instance overview revealed: Volumes Attached Attached To ba214e38-bc05-4a22-ba6b-1c88f6f7be2f on /dev/vda ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-queens-needed ** Tags added: verification-queens-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
Hello Eric, or anyone else affected, Accepted horizon into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/horizon/3:14.0.2-0ubuntu4 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 on 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: horizon (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: horizon (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
Adding another tag ^ as in the non-cloud world, we normally use 'verification-done-$RELEASE' and not 'verification-$RELEASE-done'. That way I make sure one of the 2 tags will trigger what it needs to trigger ;) - Eric ** Tags added: verification-done-pike -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
[VERIFICATION PIKE] I deployed a pike openstack env (including the horizon package found in -proposed) [Test #1] Expected result: /dev/sda * Updated an image with the right metadata values: $ glance image-update --property hw_disk_bus='scsi' --property hw_scsi_model='virtio-scsi' * Launched an instance using the image updated above * Instance overview revealed: Volumes Attached Attached To 850806bd-4c97-4925-bda9-dfe744403f47 on /dev/sda As expected ^ I confirm the fix works as expected for boot to image instance launch [Test #2] Expected result : /dev/vda * Launched an instance using the image without metadata value. * Instance overview revealed: Volumes Attached Attached To b44eb145-f86f-47fa-a2d2-908bea7384cc on /dev/vda ** Tags removed: verification-pike-needed ** Tags added: verification-pike-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
New horizon package versions including this fix have been uploaded to the cosmic (rocky) and bionic (queens) unapproved queues where they are awaiting SRU team review: https://launchpad.net/ubuntu/cosmic/+queue?queue_state=1_text=horizon https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text=horizon And also uploaded to pike-staging: https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/pike- staging/+packages?field.name_filter=horizon ** Changed in: cloud-archive/stein Status: Confirmed => Fix Released ** Changed in: cloud-archive/rocky Importance: Undecided => Medium ** Changed in: cloud-archive/rocky Status: Confirmed => Triaged ** Changed in: cloud-archive/queens Importance: Undecided => Medium ** Changed in: cloud-archive/queens Status: Confirmed => Triaged ** Changed in: cloud-archive/pike Importance: Undecided => Medium ** Changed in: cloud-archive/pike Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
The pike, queens, rocky patches are all queued up in the package source and ready to upload once the current version that is in -proposed is tested and moved to -updates. It looks like we'll need an ocata patch as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
lp1822129-xenial.debdiff ** Patch added: "lp1822129-xenial.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/horizon/+bug/1822129/+attachment/5256281/+files/lp1822129-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Also affects: horizon (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: horizon (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: horizon (Ubuntu Xenial) Status: New => In Progress ** Changed in: horizon (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
lp1822129-cosmic.debdiff ** Patch added: "lp1822129-cosmic.debdiff" https://bugs.launchpad.net/ubuntu/bionic/+source/horizon/+bug/1822129/+attachment/5256277/+files/lp1822129-cosmic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
lp1822129-bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
lp1822129-bionic.debdiff ** Patch added: "lp1822129-bionic.debdiff" https://bugs.launchpad.net/ubuntu/bionic/+source/horizon/+bug/1822129/+attachment/5256278/+files/lp1822129-bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
Openstack patches are tracked in bug 1560965 (this LP is for the SRU part) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Merge proposal linked: https://code.launchpad.net/~slashd/ubuntu/+source/horizon/+git/horizon/+merge/366119 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Changed in: horizon (Ubuntu Cosmic) Status: New => In Progress ** Changed in: horizon (Ubuntu Bionic) Status: New => In Progress ** Changed in: horizon (Ubuntu Cosmic) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: horizon (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: horizon (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: horizon (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: cloud-archive/rocky Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: cloud-archive/queens Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: cloud-archive/pike Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: cloud-archive/stein Status: In Progress => Confirmed ** Changed in: cloud-archive/rocky Status: New => Confirmed ** Changed in: cloud-archive/queens Status: New => Confirmed ** Changed in: cloud-archive/pike Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
This bug was fixed in the package horizon - 3:15.0.0~rc1-0ubuntu2 --- horizon (3:15.0.0~rc1-0ubuntu2) disco; urgency=medium [ Corey Bryant ] * Revert commited quilt patches. * Re-import orig tarball to fix broken svg files. [ Karl Williams ] * d/theme/ubuntu/_styles.scss: Fixing white bar on top of login page (LP: #1818770). [ Sahid Orentino Ferdjaoui] * d/theme/ubuntu/img: Replacing the corrupted PNG image image-background-pattern.png (LP: #1821896) [ Eric Desrochers ] * d/p/drop-devicename-creating-server-with-image-boot-to-volume.patch: When creating a server using an image boot source to new volume, horizon specified device_name 'vda'. If for instance we use an image with disk_bus type scsi, horizon will name the device_name as 'vda' when it should be 'sda'. As per BDMv2 documentation, it's best to not specify device_name. (LP: #1822129) -- Corey Bryant Mon, 01 Apr 2019 15:59:34 -0400 ** Changed in: horizon (Ubuntu Disco) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
This is fixed upstream via the following - bug: https://bugs.launchpad.net/nova/+bug/1560965 gerrit review: https://review.openstack.org/#/c/644982. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
As discussed on irc, coreyb will do the sponsoring. ** Changed in: cloud-archive/stein Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: cloud-archive/stein Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Merge proposal linked: https://code.launchpad.net/~slashd/ubuntu/+source/horizon/+git/horizon/+merge/365364 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Description changed: [IMPACT] Horizon hardcoded 'vda' no matter what (legacy code) for boot volume scenarios. Meaning that if for instance we use an image with scsi decoration[1] horizon will name the device_name as 'vda' when it should be 'sda'. Inside the instance, it will be 'sda' but horizon will show 'vda', if you then attach a second volume the volume will be seen as 'sda' in horizon, but 'sdb' in the instance and so on ... creating a inconsistency, and can also cause in certain circumstance VM to have issue to successfully reboot, hanging with "No bootable device". There is 2 functions (thus fixes) separated as follow: * setFinalSpecBootImageToVolume() which already uses BDMv2, in this case it was just a matter to remove the 'device_name' attribute as suggested per documentation[2]. This function take care of boot image from volume scenario. -> https://review.openstack.org/#/c/644982/ * setFinalSpecBootFromVolumeDevice() which currently uses BDMv1 (legacy), in this case an upgrade to BDMv2 without setting up a 'device_name' attribute is sufficient to fix the issue. This function take care of booting from existing volume and snapshot. -> https://review.openstack.org/648328/ Basically, with theses 2 fixes, it is no longer relying on "vol_device_name= 'vda'" as it was before as it is no longer needed since Liberty (again as per documentation) An instance with scsi decoration will properly show 'sda' and without will show 'vda'.'vda' will still be taken when it's the right thing to do, but not because it is hardcorded like it used to before these fixes. [1] - scsi meta decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' [2]- https://docs.openstack.org/nova/stein/user/block-device-mapping [TEST CASE] Here's some use case I can think of With fix 1 in setFinalSpecBootImageToVolume(): * Test #1: Use scsi meta data image decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance should starts with /dev/sda as root device, instead of 'dev/vda' * Test #2: Use no scsi meta data image decoration 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance will remain with /dev/vda as root device. No behaviour change here. With fix 2 in setFinalSpecBootFromVolumeDevice(): * Test #1: Creating a server using an existing volume or volume snapshot. [POTENTIAL REGRESSION] * none expected, we basically leave nova to determine the device_name instead of having it force for Horizon by removing the 'device_name' attribute, and we also take benefit of it to upgrade some part of the code from legacy BDMv1 in flavor of BDMv2. * Note: This will not fix device name inconsistency already created instance, but will fix newly created instance after having applied the package from where these fixes have been first introduced. * Both fixes aren't dependant and can be SRU'd separately. [OTHER INFORMATION] * Upstream bug: https://bugs.launchpad.net/nova/+bug/1560965 * Upstream git-review: # Taking care of bootimagefromvolume https://review.openstack.org/644982/ https://github.com/openstack/horizon/commit/4788c4d2f59b8aa08e5f599a6d2c327b6004dc0c # Taking care of existing volume and snapshot https://review.openstack.org/648328/ + + * Upstream Cherry Pick request: + https://review.openstack.org/#/q/I9d114c2c2e6736a8f1a8092afa568f930b656f0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
Special note: https://wiki.ubuntu.com/OpenStack/CorePackages For horizon, we bundle the xstatic code alongside the upstream release tarball, so horizon has 2 orig tarballs. This requires the use of debuild: debuild -S -sa To generate a new xstatic orig tarball (see horizon/debian/README.source): ./debian/rules refresh-xstatic Re-generating xstatic files for stable releases can be problematic. The general recommendation is to download the existing xstatic orig tarball from Launchpad and rename it accordingly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
"lp1822129-disco.debdiff" ** Patch added: "lp1822129-disco.debdiff" https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1822129/+attachment/5251739/+files/lp1822129-disco.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
debdiff for Horizon disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Description changed: [IMPACT] Horizon hardcoded 'vda' no matter what (legacy code) for boot volume scenarios. Meaning that if for instance we use an image with scsi decoration[1] horizon will name the device_name as 'vda' when it should be 'sda'. Inside the instance, it will be 'sda' but horizon will show 'vda', if you then attach a second volume the volume will be seen as 'sda' in horizon, but 'sdb' in the instance and so on ... creating a inconsistency, and can also cause in certain circumstance VM to have issue to successfully reboot, hanging with "No bootable device". - There is 2 functions separated as follow: + There is 2 functions (thus fixes) separated as follow: - * setFinalSpecBootImageToVolume() which already uses BDMv2, in this case - it was just a matter to remove the 'device_name' attribute as suggested - per documentation[2]. This function take care of boot image from volume - scenario. + * setFinalSpecBootImageToVolume() which already uses BDMv2, in this case it was just a matter to remove the 'device_name' attribute as suggested per documentation[2]. This function take care of boot image from volume scenario. + -> https://review.openstack.org/#/c/644982/ - * setFinalSpecBootFromVolumeDevice() which currently uses BDMv1 - (legacy), in this case an upgrade to BDMv2 without setting up a - 'device_name' attribute is sufficient to fix the issue. This function - take care of booting from existing volume and snapshot. + * setFinalSpecBootFromVolumeDevice() which currently uses BDMv1 (legacy), in this case an upgrade to BDMv2 without setting up a 'device_name' attribute is sufficient to fix the issue. This function take care of booting from existing volume and snapshot. + -> https://review.openstack.org/648328/ Basically, with theses 2 fixes, it is no longer relying on "vol_device_name= 'vda'" as it was before as it is no longer needed since Liberty (again as per documentation) An instance with scsi decoration will properly show 'sda' and without will show 'vda'.'vda' will still be taken when it's the right thing to do, but not because it is hardcorded like it used to before these fixes. [1] - scsi meta decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' [2]- https://docs.openstack.org/nova/stein/user/block-device-mapping [TEST CASE] Here's some use case I can think of With fix 1 in setFinalSpecBootImageToVolume(): * Test #1: Use scsi meta data image decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance should starts with /dev/sda as root device, instead of 'dev/vda' * Test #2: Use no scsi meta data image decoration 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance will remain with /dev/vda as root device. No behaviour change here. With fix 2 in setFinalSpecBootFromVolumeDevice(): * Test #1: Creating a server using an existing volume or volume snapshot. [POTENTIAL REGRESSION] * none expected, we basically leave nova to determine the device_name instead of having it force for Horizon by removing the 'device_name' attribute, and we also take benefit of it to upgrade some part of the code from legacy BDMv1 in flavor of BDMv2. * Note: This will not fix device name inconsistency already created instance, but will fix newly created instance after having applied the package from where these fixes have been first introduced. * Both fixes aren't dependant and can be SRU'd separately. [OTHER INFORMATION] * Upstream bug: https://bugs.launchpad.net/nova/+bug/1560965 * Upstream git-review: # Taking care of bootimagefromvolume https://review.openstack.org/644982/ https://github.com/openstack/horizon/commit/4788c4d2f59b8aa08e5f599a6d2c327b6004dc0c # Taking care of existing volume and snapshot https://review.openstack.org/648328/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Description changed: [IMPACT] Horizon hardcoded 'vda' no matter what (legacy code) for boot volume scenarios. Meaning that if for instance we use an image with scsi decoration[1] horizon will name the device_name as 'vda' when it should be 'sda'. Inside the instance, it will be 'sda' but horizon will show 'vda', if you then attach a second volume the volume will be seen as 'sda' in horizon, but 'sdb' in the instance and so on ... creating a inconsistency, and can also cause in certain circumstance VM to have issue to successfully reboot, hanging with "No bootable device". There is 2 functions separated as follow: * setFinalSpecBootImageToVolume() which already uses BDMv2, in this case it was just a matter to remove the 'device_name' attribute as suggested per documentation[2]. This function take care of boot image from volume scenario. * setFinalSpecBootFromVolumeDevice() which currently uses BDMv1 (legacy), in this case an upgrade to BDMv2 without setting up a 'device_name' attribute is sufficient to fix the issue. This function take care of booting from existing volume and snapshot. Basically, with theses 2 fixes, it is no longer relying on "vol_device_name= 'vda'" as it was before as it is no longer needed since Liberty (again as per documentation) An instance with scsi decoration will properly show 'sda' and without will show 'vda'.'vda' will still be taken when it's the right thing to do, but not because it is hardcorded like it used to before these fixes. [1] - scsi meta decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' [2]- https://docs.openstack.org/nova/stein/user/block-device-mapping [TEST CASE] Here's some use case I can think of + With fix 1 in setFinalSpecBootImageToVolume(): + * Test #1: Use scsi meta data image decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance should starts with /dev/sda as root device, instead of 'dev/vda' * Test #2: Use no scsi meta data image decoration 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance will remain with /dev/vda as root device. No behaviour change here. - * Test #3: - This above also applies to boot from existing volume and snapshot. + With fix 2 in setFinalSpecBootFromVolumeDevice(): + + * Test #1: + Creating a server using an existing volume or volume snapshot. [POTENTIAL REGRESSION] * none expected, we basically leave nova to determine the device_name instead of having it force for Horizon by removing the 'device_name' attribute, and we also take benefit of it to upgrade some part of the code from legacy BDMv1 in flavor of BDMv2. * Note: This will not fix device name inconsistency already created instance, but will fix newly created instance after having applied the package from where these fixes have been first introduced. + + * Both fixes aren't dependant and can be SRU'd separately. [OTHER INFORMATION] * Upstream bug: https://bugs.launchpad.net/nova/+bug/1560965 * Upstream git-review: # Taking care of bootimagefromvolume https://review.openstack.org/644982/ https://github.com/openstack/horizon/commit/4788c4d2f59b8aa08e5f599a6d2c327b6004dc0c # Taking care of existing volume and snapshot https://review.openstack.org/648328/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Description changed: [IMPACT] Horizon hardcoded 'vda' no matter what (legacy code) for boot volume scenarios. Meaning that if for instance we use an image with scsi decoration[1] horizon will name the device_name as 'vda' when it should be 'sda'. Inside the instance, it will be 'sda' but horizon will show 'vda', if you then attach a second volume the volume will be seen as 'sda' in horizon, but 'sdb' in the instance and so on ... creating a inconsistency, and can also cause in certain circumstance VM to have issue to successfully reboot, hanging with "No bootable device". There is 2 functions separated as follow: * setFinalSpecBootImageToVolume() which already uses BDMv2, in this case it was just a matter to remove the 'device_name' attribute as suggested per documentation[2]. This function take care of boot image from volume scenario. * setFinalSpecBootFromVolumeDevice() which currently uses BDMv1 (legacy), in this case an upgrade to BDMv2 without setting up a 'device_name' attribute is sufficient to fix the issue. This function take care of booting from existing volume and snapshot. Basically, with theses 2 fixes, it is no longer relying on "vol_device_name= 'vda'" as it was before as it is no longer needed since Liberty (again as per documentation) An instance with scsi decoration will properly show 'sda' and without will show 'vda'.'vda' will still be taken when it's the right thing to do, but not because it is hardcorded like it used to before these fixes. [1] - scsi meta decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' [2]- https://docs.openstack.org/nova/stein/user/block-device-mapping [TEST CASE] Here's some use case I can think of - * Test #1 : - Use Xen as hypervisor - - 1. Go to the Horizon dashboard and launch an instance - 2. Select "Boot from image (creates a new volume)" as Instance Boot Source - - Expected result: - Instance should starts with /dev/xvda as root device, instead of 'dev/vda' - - * Test #2: + * Test #1: Use scsi meta data image decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance should starts with /dev/sda as root device, instead of 'dev/vda' * Test #3: Use no scsi meta data image decoration 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance will remain with /dev/vda as root device. No behaviour change here. - * Test #4: + * Test #3: This above also applies to boot from existing volume and snapshot. [POTENTIAL REGRESSION] * none expected, we basically leave nova to determine the device_name instead of having it force for Horizon by removing the 'device_name' attribute, and we also take benefit of it to upgrade some part of the code from legacy BDMv1 in flavor of BDMv2. * Note: This will not fix device name inconsistency already created instance, but will fix newly created instance after having applied the package from where these fixes have been first introduced. [OTHER INFORMATION] * Upstream bug: https://bugs.launchpad.net/nova/+bug/1560965 * Upstream git-review: # Taking care of bootimagefromvolume https://review.openstack.org/644982/ https://github.com/openstack/horizon/commit/4788c4d2f59b8aa08e5f599a6d2c327b6004dc0c # Taking care of existing volume and snapshot https://review.openstack.org/648328/ ** Description changed: [IMPACT] Horizon hardcoded 'vda' no matter what (legacy code) for boot volume scenarios. Meaning that if for instance we use an image with scsi decoration[1] horizon will name the device_name as 'vda' when it should be 'sda'. Inside the instance, it will be 'sda' but horizon will show 'vda', if you then attach a second volume the volume will be seen as 'sda' in horizon, but 'sdb' in the instance and so on ... creating a inconsistency, and can also cause in certain circumstance VM to have issue to successfully reboot, hanging with "No bootable device". There is 2 functions separated as follow: * setFinalSpecBootImageToVolume() which already uses BDMv2, in this case it was just a matter to remove the 'device_name' attribute as suggested per documentation[2]. This function take care of boot image from volume scenario. * setFinalSpecBootFromVolumeDevice() which currently uses BDMv1 (legacy), in this case an upgrade to BDMv2 without setting up a 'device_name' attribute is sufficient to fix the issue. This function take care of booting from existing volume and snapshot. Basically, with theses 2 fixes, it is no longer relying on "vol_device_name= 'vda'" as it was before as it is no longer needed since Liberty
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** No longer affects: horizon (Ubuntu Xenial) ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/pike Importance: Undecided Status: New ** Also affects: cloud-archive/stein Importance: Undecided Status: New ** Also affects: cloud-archive/rocky Importance: Undecided Status: New ** Also affects: cloud-archive/queens Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Description changed: [IMPACT] Horizon hardcoded 'vda' no matter what (legacy code) for boot volume scenarios. Meaning that if for instance we use an image with scsi decoration[1] horizon will name the device_name as 'vda' when it should be 'sda'. Inside the instance, it will be 'sda' but horizon will show 'vda', if you then attach a second volume the volume will be seen as 'sda' in horizon, but 'sdb' in the instance and so on ... creating a inconsistency, and can also cause in certain circumstance VM to have issue to successfully reboot, hanging with "No bootable device". There is 2 functions separated as follow: * setFinalSpecBootImageToVolume() which already uses BDMv2, in this case it was just a matter to remove the 'device_name' attribute as suggested per documentation[2]. This function take care of boot image from volume scenario. * setFinalSpecBootFromVolumeDevice() which currently uses BDMv1 (legacy), in this case an upgrade to BDMv2 without setting up a 'device_name' attribute is sufficient to fix the issue. This function take care of booting from existing volume and snapshot. Basically, with theses 2 fixes, it is no longer relying on "vol_device_name= 'vda'" as it was before as it is no longer needed since Liberty (again as per documentation) An instance with scsi decoration will properly show 'sda' and without will show 'vda'.'vda' will still be taken when it's the right thing to do, but not because it is hardcorded like it used to before these fixes. [1] - scsi meta decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' [2]- https://docs.openstack.org/nova/stein/user/block-device-mapping [TEST CASE] Here's some use case I can think of * Test #1 : Use Xen as hypervisor 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance should starts with /dev/xvda as root device, instead of 'dev/vda' * Test #2: Use scsi meta data image decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance should starts with /dev/sda as root device, instead of 'dev/vda' * Test #3: Use no scsi meta data image decoration 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance will remain with /dev/vda as root device. No behaviour change here. * Test #4: This above also applies to boot from existing volume and snapshot. [POTENTIAL REGRESSION] * none expected, we basically leave nova to determine the device_name instead of having it force for Horizon by removing the 'device_name' - attribute, and we also take benefit of it to promote some part of the - code from legacy BDMv1 to BDMv2. This will fix the inconsistency that - annoy Horizon users for quite some time now. + attribute, and we also take benefit of it to upgrade some part of the + code from legacy BDMv1 in flavor of BDMv2. - * Note: This will not fix already created instance, but will fix newly - created instance after having applied the package from where these fixes - have been first introduced. + * Note: This will not fix device name inconsistency already created + instance, but will fix newly created instance after having applied the + package from where these fixes have been first introduced. [OTHER INFORMATION] * Upstream bug: https://bugs.launchpad.net/nova/+bug/1560965 * Upstream git-review: # Taking care of bootimagefromvolume https://review.openstack.org/644982/ https://github.com/openstack/horizon/commit/4788c4d2f59b8aa08e5f599a6d2c327b6004dc0c # Taking care of existing volume and snapshot https://review.openstack.org/648328/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
