[SRU] leave device name empty so that nova can determine it instead

debdiff for Horizon disco

"lp1822129-disco.debdiff"

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.

As discussed on irc, coreyb will do the sponsoring.

This is fixed upstream via the following -
bug: https://bugs.launchpad.net/nova/+bug/1560965
gerrit review: https://review.openstack.org/#/c/644982.

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 <email address hidden> Mon, 01 Apr 2019 15:59:34 -0400

Openstack patches are tracked in bug 1560965 (this LP is for the SRU part)

lp1822129-cosmic.debdiff

lp1822129-bionic.debdiff

lp1822129-xenial.debdiff

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.

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&queue_text=horizon
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=horizon

And also uploaded to pike-staging:

https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/pike-staging/+packages?field.name_filter=horizon

Hello Eric, or anyone else affected,

Accepted horizon into pike-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:pike-proposed
  sudo apt-get update

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-pike-needed to verification-pike-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-pike-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!

[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' <IMAGE>

* 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

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

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.

Hello Eric, or anyone else affected,

Accepted horizon into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/horizon/3:13.0.1-0ubuntu6 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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.

Hello Eric, or anyone else affected,

Accepted horizon into rocky-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:rocky-proposed
  sudo apt-get update

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-rocky-needed to verification-rocky-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-rocky-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!

Hello Eric, or anyone else affected,

Accepted horizon into queens-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:queens-proposed
  sudo apt-get update

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-queens-needed to verification-queens-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-queens-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!

[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' <IMAGE>

* 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

[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' <IMAGE>

* 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

The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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 <email address hidden> Thu, 09 May 2019 14:49:48 -0400

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 <email address hidden> Wed, 17 Apr 2019 09:42:39 +0100

The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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)

The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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)

The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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)

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?