3 Replies Latest reply on Nov 12, 2018 6:01 AM by jeffprice1

    ova fails to import, seems related to the BootOrderSection tag in the ovf

    jeffprice1 Lurker

      I've got an ova file that I've created with packer (via this plugin) that imports fine into my local vCenter managed vSphere cluster. I'm on version 6.5. I've got reports that a customer was unable to import this ova into their similar cluster. I don't have any information about what version they're running. Locally, I was able to reproduce their error on an unrelated vSphere 6.5 instance that isn't under vCenter management.

       

      When I try to import the ova, when I'm at the end ready to let it upload the ova, I get the following message:

      screenshot-2018-10-16-16-54-54.png

      If I continue anyway, the "upload" completes immediately and produces a VM that takes up no space and won't boot. After 5 minutes of thinking, vSphere seems to decide that it's broken and automatically deletes it.

       

      Interestingly, I tracked it down to the following bit of xml in the ovf file inside the ova:

         <vmw:BootOrderSection vmw:instanceId="8" vmw:type="disk">

       

         <Info>Virtual hardware device boot order</Info>

         </vmw:BootOrderSection>

      If I remove this, update the sha256 value in the manifest file, and re-tar the ova file, that one works fine on both of my environments.

      I've attached the entire ovf file from my ova for reference, including what I believe to be the offending BootOrderSection tag.

       

      Any one have any idea what's wrong with my standalone vSphere environment, or my customer's vCenter cluster that isn't showing up on my local vCenter cluster?