Rabbitmq: Deploy the Rabbitmq OVA failed in ESXi 7 with unsupported version

Products

• Pivotal RabbitMQ
• VMware RabbitMQ
• VMware Tanzu RabbitMQ

Issue/Introduction

Customer got the following error message when deploy the Rabbitmq OVA.

 

Issues detected with selected template. Details: - -1:-1:VALUE_ILLEGAL: No supported hardware versions among [vmx-21]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].

 

 

 

Resolution

You should follow below KB to change the xml and use the supported hardware version:

https://knowledge.broadcom.com/external/article/315994/deploying-ova-file-is-failing-with-no-su.html

 

 

Below are the steps to change the hardware version in the ovf file.

 

Open .ovf file in text format and modify as below changes:

In the xml file you will notice

<vssd:VirtualSystemType>vmx-21</vssd:VirtualSystemType>

 

-Modify based on supported version mentioned  [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19] in error.

<vssd:VirtualSystemType>vmx-19</vssd:VirtualSystemType>

 

In this example, we changed the hardware type to 19 which is supported in this ESXi.

 

Save the xml file.

 

 

 

 

You should encounter the checksum error again. Please follow this guide to fix this issue finally.

 

 

When you modify an OVF file in a virtual machine deployment package, the checksum recorded in the .mf (Manifest) file will no longer match the altered OVF file. You must update the .mf file to reflect the new checksum. Here's how to do it:
Steps to Update the .mf File

• Verify the Current Structure

An OVF package typically contains:

• file.ovf: The OVF descriptor file.
• file.vmdk: Virtual disk file(s).
• file.mf: The manifest file containing checksums.
• file.cert (Optional): A certificate file for signing.

Open the .mf file to confirm its format. It looks like:

SHA256(file.ovf)= <checksum>
SHA256(file.vmdk)= <checksum>

• Generate a New Checksum for the OVF File

Use a checksum tool to calculate the new checksum for the modified OVF file.

• Linux/Mac:

sha256sum file.ovf

• Windows (using PowerShell):

Get-FileHash file.ovf -Algorithm SHA256

• The output will look something like:

8f8b37d89e77f1a1fefea5d1ffb24e78b1d79f1a4bce5e52e8a3b4794e87af68

• Update the .mf File

Replace the old checksum in the .mf file with the new one. For example:
SHA256(file.ovf)= 8f8b37d89e77f1a1fefea5d1ffb24e78b1d79f1a4bce5e52e8a3b4794e87af68
SHA256(file.vmdk)= <original checksum for the VMDK>
Important: Ensure the file paths and naming conventions in the .mf file match the actual files in your package.

• Verify the Manifest File

Recheck the format of the .mf file to ensure it matches the original syntax and includes checksums for all necessary files.

• Repackage the OVF

If you're using tools to repackage the OVF, you can bundle it back into an .ova file (optional).

• Linux/Mac:

tar -cvf file.ova file.ovf file.mf file.vmdk

• Windows (using a tar tool like 7-Zip):
• Select all the OVF package files.
• Add them to a tar archive with the .ova extension.

Verify the New Package

• Use tools like VMware Workstation, VirtualBox, or ovftool to ensure the updated package works correctly:

ovftool file.ovf

• Ensure no errors arise during the deployment of the virtual machine.