group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1627931@xxxxxxxxxxxxxxxxxx>]

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

---------------
livecd-rootfs (2.435.2) yakkety; urgency=medium

  [ Chris Glass ]
  * Fix the manifest generation in OVA files so that ovf files don't have
    double extensions.  (LP: #1627931)
  * Fix the OVF's metadata to include Ubuntu specific identifiers and
    descriptions instead of the generic Linux ones.  (LP: #1656293)
  [ Daniel Watkins ]
  * Add replace_grub_root_with_label function thereby consolidating multiple
    uses of the same calls to sed.

 -- Robert C Jennings <robert.jennings@xxxxxxxxxx>  Fri, 17 Mar 2017
13:46:47 -0500

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1627931

Title:
  SHA256 checksum for ovf in xenial-server-cloudimg-amd64.ova has
  incorrect path

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

Bug description:
  [Impact]

   * Users will be unable to import OVA disk images with tools that
  check the manifest to verify file checksums

  [Test Case]

  $ apt-get install virtualbox

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

  ## Requires version newer than 5.0.32_Ubuntur112930  in zesty)
  $ vboxmanage -version
  5.1.18_Ubuntur114002

  $ vboxmanage import  xenial-server-cloudimg-amd64.ova
  0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
  Progress state: VBOX_E_FILE_ERROR
  VBoxManage: error: Appliance import failed
  VBoxManage: error: Digest mismatch (VERR_NOT_EQUAL): 'ubuntu-xenial-16.04-cloudimg.ovf.ovf' not found in the 2nd manifest
  VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
  VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 886 of file VBoxManageAppliance.cpp

  ## Expecting import success
  "Successfully imported the appliance."

  [Regression Potential]

   * Very low: If a tool is checking the manifest and has been modified
  to strip a duplicate ".ovf" from the name to allow the current image
  to work but also removed handing for valid files it would fail (but we
  know this is not true as there exists in the manifest a file that is
  already specified with the correct filename).

  [Original Description]

  Opening the current "xenial-server-cloudimg-amd64.ova" file from
  cloud-images.ubuntu.com in VirtualBox produces this error:

      Failed to import appliance C:/Users/Jesse/Downloads/xenial-server-
  cloudimg-amd64.ova.

      Digest mismatch (VERR_NOT_EQUAL): 'ubuntu-
  xenial-16.04-cloudimg.ovf.ovf' not found in the 2nd manifest.

      Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
      Component: ApplianceWrap
      Interface: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}

  The ubuntu-xenial-16.04-cloudimg.mf inside the .ova has this contents:

      SHA256(ubuntu-xenial-16.04-cloudimg.vmdk)= 1a9d4ebadf89aa3a12a20f9933b5f88e3b0edcb00fa286c653356bc2ff9d4a29
      SHA256(ubuntu-xenial-16.04-cloudimg.ovf.ovf)= eaca73e5217e0d12f1b5bfbbec039f445c89b807d0c5aba11f842639abb40d35

  After changing ".ovf.ovf" to ".ovf" and saving the file inside the
  .ova, importing the .ova works.

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