Upgrading to Cloud Director 10.6 using the command "vamicli update --install latest" keeps running indefinitely

Products

• VMware Cloud Director

Issue/Introduction

• Unable to upgrade or deploy vCloud 10.6 Appliance 
• Upgrade from version 10.5.1.1 when running the command "vamicli update --install latest" , it will get stuck without completing
• The firstboot.log reports warning. 

2024-07-01 09:15:28 | Checking for all required OVF parameters, for VCD Configuration Phase
Please provide NFS mount
Please provide Administrator password
Please provide DB password
Please provide Administrator's email
Please provide Administrator's full name
Please provide Administrator's installation ID
Please provide system name
Not all required ovf parameters were provided, aborting Cloud Director configuration phase
2024-07-01 09:15:29 | [WARNING] Not all required parameters for VCD configuration were provided.
2024-07-01 09:15:29 | For more details, see: /opt/vmware/var/log/vcd/configure-vcd.log
2024-07-01 09:15:29 | Please complete the appliance configuration using the appliance management UI.

The configure-vcd.log shows a failure.

2024-07-01 09:15:28 | check-vcd-params.sh | Checking ovf parameters needed for proper Cloud Director configuration ...
2024-07-01 09:15:29 | check-vcd-params.sh | nfs_mount ovf parameter not specified
2024-07-01 09:15:29 | check-vcd-params.sh | admin_pwd ovf parameter not specified
2024-07-01 09:15:29 | check-vcd-params.sh | db_pwd ovf parameter not specified
2024-07-01 09:15:29 | check-vcd-params.sh | admin_email ovf parameter not specified
2024-07-01 09:15:29 | check-vcd-params.sh | admin_fname ovf parameter not specified
2024-07-01 09:15:29 | check-vcd-params.sh | inst_id ovf parameter not specified
2024-07-01 09:15:29 | check-vcd-params.sh | sys_name ovf parameter not specified
2024-07-01 09:15:29 | check-vcd-params.sh | Number of missing parameters: 7
2024-07-01 09:15:29 | check-vcd-params.sh | [ERROR] Not all required ovf parameters were provided, aborting Cloud Director configuration phase

Environment

VMware Cloud Director 10.5.1.1

Cause

This issue can occur if Cloud Director is in a private network and no internet access available. This causes several rpms not been installed correctly

 

Resolution

This is a known issue which Broadcom is aware of and will be fixed in a future release of VMware Cloud Director.

To resolve this issue, contact Broadcom Support and note this Article ID (373507) in the problem description. For more information, see Creating and managing Broadcom support cases