Navigating to Operate > Logs in VCF Operations displays the "Install Log Management" screen after a successful upgrade, even though the VCF Operations for Logs UI is directly accessible.
VCF Operations 9.1.x
This issue occurs because the legacy 9.0 Fleet Management appliance password expired during the upgrade workflow, preventing the system from executing the automated VM shutdown command. Consequently, the 9.0 Fleet LCM appliance remained powered on and continuously initiated inventory synchronizations, which repeatedly overwrote the new 9.1 Fleet LCM configuration in VCF Operations.
To resolve this issue, manually power off the legacy Fleet Management appliance and force an inventory sync for the VCF Operations for Logs 9.1 component:
VSP_MGMT_FQDN="<vcf-services-runtime-fqdn>"
VSP_USER="[email protected]"
VSP_PASS='<vsp-password>' # Same password as the vmware-system-user account
FLEET_LCM_FQDN="<fleet-lcm-fqdn>"Note:
<vcf-services-runtime-fqdn> with Fully qualified domain name of vcf-services runtime.<vsp-password> with a password of user vmware-system-user account<fleet-lcm-fqdn> with Fully qualified domain name of Fleet LCM.JWT=$(curl -k -s -X POST \
"https://${VSP_MGMT_FQDN}/api/v1/identity/token" \
-H "Content-Type: application/x-www-form-urlencoded" \
--data-urlencode "grant_type=password" \
--data-urlencode "username=${VSP_USER}" \
--data-urlencode "password=${VSP_PASS}" \
| jq -r '.access_token')echo "JWT: $JWT"VCF Operations for Logs component ID, run the command below. Search its component id in output.curl -sS -k -X GET "https://${FLEET_LCM_FQDN}/fleet-lcm/v1/components" \
-H "Authorization: Bearer ${JWT}" \
-H "Content-Type: application/json" | jq
curl -sS -k -X POST "https://${FLEET_LCM_FQDN}/fleet-lcm/v1/components/<OPS for logs-ID>?action=refresh" \
-H "Authorization: Bearer ${JWT}" \
-H "Content-Type: application/json" | jqNote: Replace <OPS for logs-ID> with the component ID received in the output of Step 3.iv.