[Bug 1970795] Re: jammy-server-cloudimg-amd64.ova does not create cdrom device on vsphere

[Łukasz Zemczak]

Hello Jim, or anyone else affected,

Accepted livecd-rootfs into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.764.1 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, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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: livecd-rootfs (Ubuntu Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1970795

Title:
  jammy-server-cloudimg-amd64.ova does not create cdrom device on
  vsphere

Status in cloud-images:
  In Progress
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Jammy:
  Fix Committed
Status in livecd-rootfs source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

   * Ubuntu jammy OVA images will not have a CD-ROM drive by default
  when imported by vmware

  [Test Plan]

  * having the free vmware-player (or vsphere)

  * file: import the ova

  * open settings and check for the presence of the CD-ROM drive

  [Where problems could occur]

   * The change is limited only to the OVA template, so other image generation should not be affected
   
   * This is a revert to a previous bus mapping, prior to adding the serial port. From this bug, getting the bus mapping wrong will have vmware to keep discarding that config.

  * virtualbox doesn't appear to use that setting. There is a small risk
  that another hypervisor not mentioned here loses cdrom in the same way
  if it relies on the cdrom being only on a SCSI bus.

  
  [Original description]

  jammy-server-cloudimg-amd64.ova does not create cdrom device when
  deploying on vsphere 7.

  VMware vsphere injects properties like user-data or ssh keys to the VM
  by means of an iso image mounted on the first CDROM device at boot.

  jammy-server-cloudimg-amd64.ova apparently does not include a cdrom in
  the OVF spec. In order to use the .ova image, a cdrom device has to be
  added before boot.

  Prior versions of ubuntu server (such as focal-server-cloudimg-
  amd64.ova) included the cdrom device in the OVF spec. So this is a
  change from prior practice. Wondering if cdrom could be included
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1970795/+subscriptions