Red Hat Bugzilla – Bug 1472972
[RFE] The azure image as built cannot be used in azure.
Last modified: 2017-08-17 14:22:56 EDT
Description of problem: Azure has two requirements that our build process is not meeting. First, the disk has to be a fixed size. Second, the fixed size needs to be exactly divisible by 1mb. This is what we are telling our customers to do, if they can find the article. https://access.redhat.com/node/2984371/ Version-Release number of selected component (if applicable): Been around for a while. How reproducible: Try to upload the azure image and create an appliance from it. Steps to Reproduce: 1. Take standard azure image - cfme-azure-5.x.x.x-1.x86_64.vhd 2. Upload as is to azure. 3. Actual results: The disk and VM is unusable. Expected results: We seem to be getting complaints on this on a weekly basis. Mostly of the people who run into this feel we should just correctly size the vhd at build time. Additional info: This requirement was in classic mode. For a year, it wasn't a requirement in Resource Manager mode. Sometime in the spring the re-implemented the requirement.
I show that a gzipped aligned vdf file is 1/10th the size of the standard download and should be the default offering. qemu-img info --output=json -f vpc cfme-azure-5.8.0.17-1.x86_64_fixed.vhd { "virtual-size": 34361835520, "filename": "cfme-azure-5.8.0.17-1.x86_64_fixed.vhd", "format": "vpc", "actual-size": 3158839296, "dirty-flag": false } 33G - cfme-azure-5.8.0.17-1.x86_64_fixed.vhd 317M - cfme-azure-5.8.0.17-1.x86_64_fixed.vhd.gz
https://github.com/ManageIQ/manageiq-appliance-build/pull/222