Stale upgrade plan components appear in the VCF Operations lifecycle 9.1 interface. as Log Management lifecycle interface after a failed VCF 9.1 installation or upgrade cleanup.
Ready for upgrade Prechecks failed" and target versions such as 9.1.0.0.########. Attempting to re-run prechecks or resume the upgrade results in a VCF_LCM_FLEET_UPGRADE_400_INVALID_UPGRADE_PLAN_SPEC error.Internal Server Error" related to binaries may be present:Unable to retrieve information about required binaries. Internal Server Error for service fleet-upgrade-service. Verify logs for service fleet-upgrade-service.VCF Operations 9.1
VCF Automation 9.1
A stale upgrade_plan_component ID remains in the Fleet Lifecycle database (vcffleetlcmdb) after the cleanup_component.py script is executed. The UI renders these orphaned records as undefined tasks because the primary inventory references have been removed, but the task metadata persists.
Login into VCF Operations and go to Lifecycle > Build > VCF Management > Component > VCF services runtime
Identify a Control Plane node IP:
Copy the attached script to the SDDC Manager /home/vcf/ directory.
python cleanup_upgrade_plan_component.pyProvide the VSP services runtime Control Plane node IP from step 2 when prompted.Provide the vmware-system-user password when prompted. Follow the script instructions to identify and cleanup the stale upgrade_plan_component id.