Transitioning cluster from using baselines to vSphere Lifecycle Manager Images using the VcfBaselineClusterTransition.ps1 PowerShell Script CLI script is failing - VCF 9.1.1
search cancel

Transitioning cluster from using baselines to vSphere Lifecycle Manager Images using the VcfBaselineClusterTransition.ps1 PowerShell Script CLI script is failing - VCF 9.1.1

book

Article ID: 456672

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

  • The environment is being upgraded from VCF 5.x to VCF 9.1.1.
  • The other components have been upgraded to VCF 9.1.1, and the next components to upgrade are the ESX hosts.
  • Baselines are currently being used in the environment, per this documentation - any clusters that use baselines must be transitioned to using vSphere Lifecycle Manager Images before ESX can be upgraded to 9.x. 
  • The VcfBaselineClusterTransition.ps1 script described here is being used to do the transition.
  • From the script menu - option 3 - Check existing cluster(s)/standalone hosts(s)' vLCM image compliance - has been run.
  • When option 4 - Transition vLCM baseline Cluster/standalone host to vLCM image management - is run it fails with an error:

[ERROR] An unexpected error occurred.
[ERROR] DD.MM.YYYY hh:mm:ss    Invoke-VcfUpdateCluster        500: Internal server error calling UpdateCluster: {"message":"Image compliance result for cluster with ID: ####-####-####-####-#### is in INCOMPATIBLE state", "errorCode":"CLUSTER_IMAGE_COMPLIANCE_INCOMPATIBLE", "arguments": ["####-####-####-####-####"], "referenceToken":"####"}

  • In the VcfBaselineClusterTransition-MM-DD-YYYY.log log file that is generated this entry is observed:

"EntityName": "host_in_cluster_fqdn",  
      "ComponentType": "",  
      "ComplianceStatus": "",  
      "Severity": "ERROR",  
      "ComponentCurrentVersion": "",  
      "ComponentTargetVersion": "",  
      "ComponentName": "",  
      "ComponentVendor": "",  
      **"Message": "Live Patch cannot be performed together with live removal of VIB(s) VMware_bootbank_spherelet_#.#.#-####, VMware_bootbank_vmware-fdm_#.#.#-#.#.#.####.",**  
      "Impact": "MAINTENANCE_MODE_REQUIRED"

Environment

VCF 9.1.1

Cause

  • Live patching being enabled in the vSphere Lifecycle Manager cluster remediation settings is blocking the transition.

Resolution

Temporarily disable live patching in the vSphere Lifecycle Manager cluster remediation settings vSphere UI page:

  1. Navigate to this page on the vSphere UI > hamburger icon top left > Lifecycle Manager > Remediation Settings > Clusters
  2. Click EDIT.
  3. Untick "Enable Live Patch".
  4. Click SAVE.
  5. In the VcfBaselineClusterTransition.ps1 script run the below:
    1. option 3 - Check existing cluster(s)/standalone hosts(s)' vLCM image compliance
    2. option 4 - Transition vLCM baseline Cluster/standalone host to vLCM image management
  6. The transition is expected to complete successfully.
  7. Live patching can again be enabled as required.