[Bug 1656293] Re: OVF metadata for Ubuntu is wrong

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.440

---------------
livecd-rootfs (2.440) zesty; urgency=medium

  [ Steve Langasek ]
  * live-build/ubuntu-cpc/functions: don't call sleep as part of
    umount_settle; udevadm settle is synchronous and there's no reason to
    sleep after it.
  * live-build/ubuntu-cpc/functions: umount_partition: don't call
    umount_settle for each submount; just unmount them one by one and
    settle at the end.
  * Support passing IMAGE_TARGETS in the environment, to limit which images
    are output as part of a build; particularly useful for ubuntu-cpc builds
    which output multiple image types.

  [ Nishanth Aravamudan ]
  * live-build/ubuntu-cpc/hooks/061-open-iscsi.chroot: generate iSCSI
    Initiator Name at first iscsid run for cloud images to ensure it is
    unique (LP: #1444992).

  [ Brian Murray ]
  * Fix the OVF's metadata to include Ubuntu specific identifiers and
    descriptions instead of the generic Linux ones. Thanks to Chris Glass.
    (LP: #1656293)
  * Add replace_grub_root_with_label function thereby consolidating multiple
    uses of the same calls to sed. Thanks to Dan Watkins.

  [ Adam Conrad ]
  * Set device_tree_address for the new kernel in the RPi bootloader config.txt

 -- Adam Conrad <adconrad at ubuntu.com>  Thu, 23 Mar 2017 11:39:22 -0600

** Changed in: livecd-rootfs (Ubuntu)
       Status: New => Fix Released

-- 
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/1656293

Title:
  OVF metadata for Ubuntu is wrong

Status in cloud-images:
  In Progress
Status in livecd-rootfs package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  * Ubuntu images are identified generically as 32- or 64-bit Linux with
  a 2.6 kernel rather than Ubuntu 32-/64-bit images.  Tools that consume
  the images can not perform OS-specific actions based on the current
  metadata.

  [Test Case]

  $ apt-get install virtualbox

  $ wget http://cloud-images.ubuntu.com/xenial/current/xenial-server-
  cloudimg-amd64.ova

  $ vboxmanage import --dry-run xenial-server-cloudimg-amd64.ova
  ...
  Virtual system 0:
   0: Suggested OS type: "Linux26_64"
      (change with "--vsys 0 --ostype <type>"; use "list ostypes" to list all possible values)
  ...

  We would expect the following after the fix:
  Virtual system 0:
   0: Suggested OS type: "Ubuntu_64"

  [Regression Potential]

   * Low: A user downloads the image with the change and checks the OS
  type field to see that Ubuntu is a marked as a generic 2.6 kernel
  Linux image and now we will have changed "Linux26_*" to "Ubuntu_*".

  [Original Description]
  The OVF files produced by cloud-images currently contain:

  <OperatingSystemSection ovf:id="100" vmw:osType="other3xLinux64Guest">
        <Info>The kind of installed guest operating system</Info>
  </OperatingSystemSection>

  The OVF specification has entries for Ubuntu, and that usually allows
  client machines to customize the host using whatever their method is.

  The specific entries for Ubuntu 64 bits are:
  - ovf:id: 94
  - ovf:osType: ubuntu64Guest

  The specific entries for Ubuntu 32 bits are:
  - ovf:id: 93
  - ovf:osType: ubuntu32Guest

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