Description of problem: ----------------------- Error while uploading vhd image to azure portal. Here is the snippet. This is blocking us in qualifying the gluster + azure. [byarlaga@bky opt]$ azure vm image create rhgs-3.1.3 --location "East US" --os linux ~/Downloads/RHGS-3.1.3-3.x86_64.vhd info: Executing command vm image create + Retrieving storage accounts warn: The total size of blocks 10242 Mb is different warn: from declared VHD size 10240.453125 Mb info: VHD size : 10 GB info: Uploading 1861632.5 KB error: Object conectix����������HwaWi2k�@� QF?�������elG��!��@�` has no method 'on' info: Error information has been recorded to /home/blr/byarlaga/.azure/azure.err [byarlaga@bky opt]$ cat /home/blr/byarlaga/.azure/azure.err 2016-06-01T09:39:41.915Z: [TypeError: Object conectix����������HwaWi2k�@� QF?�������elG��!��@�` has no method 'on'] TypeError: Object conectix����������HwaWi2k�@� QF?�������elG��!��@�` has no method 'on' at /usr/lib/node_modules/azure-cli/node_modules/azure-storage/lib/common/services/storageserviceclient.js:431:35 at /usr/lib/node_modules/azure-cli/node_modules/azure-storage/lib/common/services/storageserviceclient.js:557:5 at SharedKey.signRequest (/usr/lib/node_modules/azure-cli/node_modules/azure-storage/lib/common/signing/sharedkey.js:84:3) at BlobService.StorageServiceClient._buildRequestOptions (/usr/lib/node_modules/azure-cli/node_modules/azure-storage/lib/common/services/storageserviceclient.js:539:27) at operation (/usr/lib/node_modules/azure-cli/node_modules/azure-storage/lib/common/services/storageserviceclient.js:262:10) at /usr/lib/node_modules/azure-cli/node_modules/azure-storage/lib/common/services/storageserviceclient.js:470:9 at BlobService.filter (/usr/lib/node_modules/azure-cli/node_modules/azure-storage/lib/common/services/storageserviceclient.js:828:7) at BlobService.StorageServiceClient._performRequest (/usr/lib/node_modules/azure-cli/node_modules/azure-storage/lib/common/services/storageserviceclient.js:453:8) at BlobService.StorageServiceClient.performRequestOutputStream (/usr/lib/node_modules/azure-cli/node_modules/azure-storage/lib/common/services/storageserviceclient.js:193:8) at BlobService._createPages (/usr/lib/node_modules/azure-cli/node_modules/azure-storage/lib/services/blob/blobservice.js:4673:10) [byarlaga@bky opt]$ ls -lh ~/Downloads/RHGS-3.1.3-3.x86_64.vhd -rw-r--r--. 1 byarlaga byarlaga 1.8G Jun 1 15:08 /home/blr/byarlaga/Downloads/RHGS-3.1.3-3.x86_64.vhd [byarlaga@bky opt]$ Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Is the VHD being uploaded a "fixed" or "expandable" VHD? Azure requires fixed and will give an error message similar to the above if an expandable VHD is used.
Hi Joshua, Could you please let us know on how to find out whether the image is a "fixed" or "expandable" one. This images is built using a kickstart configuration file, so you might probably be asking about such a parameter inside kickstart file.
I'm assuming you are pointing kickstart at a drive image you've already created. This article covers VHD creation and the differences: https://technet.microsoft.com/en-us/library/gg318052(v=ws.10).aspx To use a VHD with Azure, it must be created as "fixed".
Additional comments from Microsoft: We are aware of this is issue and applies to dynamic VHD’s only. At this point I would recommend you to use the GO utility<https://github.com/Microsoft/azure-vhd-utils-for-go> to upload dynamic VHD’s or convert their dynamic VHD’s to fixed VHD’s before uploading using the CLI.
I will try these steps and update.
Couple of updates WRT this : ============================ 1. I am able to upload the image using the vhd command what's mentioned in comment# 9, but this helps only in fixing the format and uploading the images. I could not find a way to deploy vm's using this (during vm creation it asks for image name which is not equal to the vhd name). 2. While 'azure vm image create' command does the upload, it creates a tag for the image using which we can spin off the vm's. We can convert the image format to fixed and proceed and that's not a problem anymore. 3. I installed a vm using ISO on libvirt with qcow2 format and converted that to a vhd and uploaded it to portal. Could spin a vm out of this but its getting transitioning to dracut prompt. Not sure what's the problem here and would need some time to get around this. I had filed a microsoft support ticket and following the steps mentioned. The qcow2 image that RCM provided still has issues of login and couple of error messages which i think are not fixed yet.
I am currently blocker at https://bugzilla.redhat.com/show_bug.cgi?id=1341560#c11 Point (3). The vm is transitioning to dracut prompt during boot up.
I am currently blocked at https://bugzilla.redhat.com/show_bug.cgi?id=1341560#c11 Point (3). The vm is transitioning to dracut prompt during boot up.
Does that mean that, the vhd image , that got converted from RHGS ISO has issues? (dracut prompt)
Please find the latest fine tuned RHGS-3.1.3-RHEL-7 VHD image. https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=501782
I am trying with the latest image and update the status.
The latest image https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=501782 works. Created a gluster cluster and ran some basic tests. I will update the documents with the steps.
Marking this bug as verified for RHEL-7 image.