SHA256 checksum for ovf in xenial-server-cloudimg-amd64.ova has incorrect path
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
High
|
Chris Glass | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned | ||
Yakkety |
Fix Released
|
High
|
Unassigned |
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://
## Requires version newer than 5.0.32_
$ vboxmanage -version
5.1.18_
$ vboxmanage import xenial-
0%...10%
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Digest mismatch (VERR_NOT_EQUAL): 'ubuntu-
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportApp
## 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-
Failed to import appliance C:/Users/
Digest mismatch (VERR_NOT_EQUAL): 'ubuntu-
Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: ApplianceWrap
Interface: IAppliance {8398f026-
The ubuntu-
SHA256(
SHA256(
After changing ".ovf.ovf" to ".ovf" and saving the file inside the .ova, importing the .ova works.
Related branches
- Robert C Jennings (community): Approve
- Dan Watkins (community): Approve
- Philip Roche (community): Approve
- Ubuntu Core Development Team: Pending requested
-
Diff: 25 lines (+2/-2)2 files modifiedlive-build/ubuntu-cpc/hooks/041-vmdk-ova-image.binary (+1/-1)
live-build/ubuntu-cpc/hooks/042-vagrant.binary (+1/-1)
- Ubuntu Core Development Team: Pending requested
-
Diff: 196 lines (+66/-15)8 files modifieddebian/changelog (+13/-0)
live-build/ubuntu-cpc/functions (+7/-0)
live-build/ubuntu-cpc/hooks/033-disk-image-uefi.binary (+1/-1)
live-build/ubuntu-cpc/hooks/034-disk-image-ppc64el.binary (+1/-1)
live-build/ubuntu-cpc/hooks/041-vmdk-ova-image.binary (+21/-5)
live-build/ubuntu-cpc/hooks/042-vagrant.binary (+19/-6)
live-build/ubuntu-cpc/hooks/ovf/ubuntu-ova-v1-cloudcfg-vmdk.tmpl (+2/-1)
live-build/ubuntu-cpc/hooks/ovf/ubuntu-ova-v1-vmdk.tmpl (+2/-1)
Changed in cloud-images: | |
status: | New → Confirmed |
Changed in cloud-images: | |
assignee: | nobody → Chris Glass (tribaal) |
Changed in cloud-images: | |
status: | Confirmed → In Progress |
importance: | Undecided → High |
description: | updated |
description: | updated |
Changed in livecd-rootfs (Ubuntu): | |
importance: | Undecided → High |
Changed in livecd-rootfs (Ubuntu Xenial): | |
importance: | Undecided → High |
Changed in livecd-rootfs (Ubuntu Yakkety): | |
importance: | Undecided → High |
tags: | added: id-587c9d1faefa1389c5543492 |
tags: | added: id-5878b7f940cb3d1226960cd7 |
Changed in cloud-images: | |
status: | In Progress → Fix Released |
Hi,
I hit the same issue. Can you share me the steps you used to modify the .ova?
Thanks.