Loading...
Loading...
Observed Issues When Accessing VAMI and vCenter VAMI Access Errors Attempting to open VAMI returns the error message "Unable to get deployment status.” Unable to get deployment status vCenter Boot and Configuration Indicators. A file named failed appears in /var/log/firstboot/.The contents of the failed file indicate "Failed to configure network.”vCenter is unable to ping the DNS server. Application Management Logs The log /var/log/vmware/applmgmt/applmgmt.log contains the entry "INSTALL_IN_PROGRESS" ... INSTALL_IN_PROGRESS ... fbInstall.json File Anomalies The file fbInstall.json exists in /var/log/firstboot/ but may have incorrect permissions (not 644 ).The JSON content shows a "progress" value other than 100 or a "status" value other than "success.” { "progress": 85, "status": "in_progress" } Upgrade Directory Files In /var/log/vmware/upgrade/, the expected files Prechecks-succeeded, Exports-succeeded, and Import-succeeded are missing or not zero‑kilobytes in size.
Underlying Factors Leading to VAMI "Unable to get deployment status" DNS resolution failure VAMI cannot reach required services when the vCenter server cannot ping or resolve the DNS server.Network configuration error during first‑boot. In /var/log/firstboot/failed, the file shows "Failed to configure network.”Improper file permissions on /var/log/firstboot/fbInstall.json other than 644 (rw-r--r--) prevent the installation process from reading progress and status information.Installation shows in progress in the logs. The presence of "INSTALL_IN_PROGRESS" in /var/log/vmware/applmgmt/applmgmt.log shows that the deployment has not finished.Corrupted or incomplete fbInstall.json missing or malformed "progress" (not 100) or "status" (not "success") fields cause the VAMI to report an undefined deployment state.Missing zero‑byte marker files in /var/log/vmware/upgrade/ absence of Prechecks-succeeded, Exports-succeeded, or Import-succeeded indicates that prerequisite steps were not recorded as completed.
Access VAMI and Verify DNS Configuration. Initial access check Attempt to open the VAMI interface using the direct IP address: https://:5480/configurev2 If the error "Unable to get deployment status" appears, proceed with the steps below. DNS validation Confirm that the vCenter host can resolve and ping the DNS server.Clear the browser cache or try a different browser.Reference VxRail article VxRail: vCenter Unable to get deployment status for additional guidance. Caution: Incorrect DNS settings can prevent further deployment steps. Verify connectivity before proceeding. Inspect First‑Boot Logs for Network Errors. Locate the failure file. # List files in the firstboot log directory ls -l /var/log/firstboot/ # If a file named "failed" exists, display its contents cat /var/log/firstboot/failed If the file contains "Failed to configure network,” ensure the vCenter can ping the DNS server and correct any network misconfigurations. Check Application Management Status. Search for ongoing installation. # Look for the INSTALL_IN_PROGRESS flag grep -i "INSTALL_IN_PROGRESS" /var/log/vmware/applmgmt/applmgmt.log Validate fbInstall.json # Verify the file exists ls -l /var/log/firstboot/fbInstall.json # Confirm permissions are 644 (rw-r--r--) ls -ltrh /var/log/firstboot/fbInstall.json # Review the JSON content cat /var/log/firstboot/fbInstall.json In the JSON output, ensure: "progress" is set to 100 "status" is set to "success" Restart the applmgmt service if needed. # Stop the service service-control --stop applmgmt # Edit the JSON file (use vi or your preferred editor) to correct any incorrect values vi /var/log/firstboot/fbInstall.json # Start the service service-control --start applmgmt Note: Editing JSON files should be performed with caution. Always perform a backup the original file before making changes. Verify Upgrade Completion Files. Check for zero‑byte success markers. cd /var/log/vmware/upgrade/ ls -lh Expected files (0 KB each): Prechecks-succeeded Exports-succeeded Import-succeeded Create missing markers. # Add the files using the touch command. Replace <FILE_NAME> with one of the files above, e.g., Prechecks-succeeded Example: touch Prechecks-succeeded # Restart the lightweight VAMI web server Prior to 8.0U3: /sbin/service vami-lighttp restart 8.0U3 and above: systemctl restart cap-lighttpd.service Caution: Restarting vami-lighttp temporarily interrupts VAMI access. Perform this step during a maintenance window if possible. Final Verification Access VAMI at https:// :5480/configurev2 and confirm the deployment status loads without error.Run the following command to ensure that no installation is in progress: grep -i "INSTALL_IN_PROGRESS" /var/log/vmware/applmgmt/applmgmt.log || echo "No active installation" Confirm that the three success marker files exist and remain at 0 KB.Check network connectivity to the DNS server from the vCenter host. Note: If the issue persists after completing all steps, consult Broadcom article Accessing the VAMI returns an error "Unable to get deployment status"or open a Dell Support case.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.