When you have time, you do something.
Tonight I was headed over the Ubuntu site to grab me the latest version because I was thinking of installing OpenStack when I noticed on their landing page and noticed “Get Ubuntu Core” ; yes something new.
But where is my Raspberry Pi? No worries they have OVF images I can use to deploy to my vCenter Lab here at home. So I started just this and encountered an issue I once had.
Lets walk you through my events.
Downloading the image
- Found myself on the Ubuntu Internet of Things landing page: http://www.ubuntu.com/internet-of-things
- Located the OVF section of the getting started page: http://developer.ubuntu.com/en/snappy/start/
- Downloaded the OVA image (x86): 15.04/stable
Deploying the OVF Template
- Using the vSphere Client, connected to vCenter (or stand alone ESXi host)
- Select server to deploy to and choose file > Deploy OVF Template
- Browse to the path were you downloaded your OVF image and select it
This is when I received the following error:
The following manifest file entry (line 1) is invalid: SHA256(core-stable-amd64-cloud.ovf)= d4b8922ed38a4eb9055576f7b46f8e92f463398298f3a42af942f25457d4d41c
Troubleshooting Step 1
- I extracted the OVA image (core-stable-amd64-cloud) with 7zip
- Once extracted attempted the steps detailed above “Deploying the OVF Template”
The same error was thrown once more.
Troubleshooting Step 2
Within the extracted folder exists the following file types: certificate, manifest, ovf (instruction / configuration) and disk image
- I remove the SHA256(core-stable-amd64-cloud.ovf)= d4b8922ed38a4eb9055576f7b46f8e92f463398298f3a42af942f25457d4d41c line from the .MF (manifest)
- Once removed I attempted the steps detailed above “Deploying the OVF Template”
It failed also, only this time the error started the the remaining SHA256 was also invalid.
Troubleshooting Step 3 – Third time is the charm
- Moved into the extracted OVA folder
- Deleted the .mf (manifest) file
- Followed steps above “Deploying the OVF Template” only this time using the OVF located in the extracted folder
This go around everything worked
So why did this happen?
The template was changed after its creation which invalidated the SHA256 key. I have made templates myself, only to have to edit something out such as removing a CD Rom reference which later caused me issues.
I hope this helps if you face this incident or something similar
Thanks for visiting – jermal
Also published here