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)
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 patching- for-APITestCase .patch: Cherry-picked from devicename- creating- server- with-image- boot-to- volume. patch:
.
* New update for the Ubuntu Cloud Archive.
.
horizon (3:14.0.2-0ubuntu4) cosmic; urgency=medium
.
* d/p/*-monkey-
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-
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)