Error: "vmsp-platform: wrong resource state: InProgress" in the VCF Operations UI.
search cancel

Error: "vmsp-platform: wrong resource state: InProgress" in the VCF Operations UI.

book

Article ID: 451565

calendar_today

Updated On:

Products

VMware Cloud Foundation VCF Automation

Issue/Introduction

A similar error is observed in the VCF Operations UI. 

Platform Health Check. Status: FAILED Platform Health Check Error [platform-package-core : 1 of 1 resources are not ok: vmsp-platform: wrong resource state: InProgress - PackageDeployment generation is 20, but latest observed generation is 19;] [VCFMS-HEALTH-002]




The following error is observed when you run the following command on one of the Control Plane nodes. 

[ /home/vmware-system-user ]# kubectl get pd -Aw
NAMESPACE NAME AGE PHASE STATUS
salt-raas salt-raas 98d Successful successful package deployment
salt salt 98d Successful successful package deployment
telemetry telemetry-acceptor 98d Successful successful package deployment
vcf-fleet-depot vcf-fleet-depot 98d Successful successful package deployment
vcf-fleet-lcm vcf-fleet-lcm 98d Successful successful package deployment
vcf-sddc-lcm vcf-sddc-lcm 98d Successful successful package deployment
vidb-external vidb 98d Successful successful package deployment
vmsp-platform vmsp-platform 98d Failed failed to generate helmrelease for template proxy-service-9.1.1865: failed to unmarshal to helmrelease: error converting YAML to JSON: yaml: line 54: did not find expected alphabetic or numeric character

Environment

VMware Cloud Foundation 9.1.x

Cause

It is unsupported to add the "*" in the excludeDomain field when configuring a proxy on VCF Management Services or VCF Automation.

Resolution

  1. Identify a Control Plane node from the VCF Operations UI.

    VCF Operations UI > Build > Lifecycle > Components > VCF services runtime > Nodes


  2. SSH into the Control Plane Node with vmware-system-user 
  3. Elevate to root with sudo -i 
  4. Edit the vmsp-platform packageDeployment
    kubectl edit pd -n vmsp-platform vmsp-platform
  5. Find the peerProxy section

    /peerProxy
  6. Enter "Insert" mode with Shift + I 

  7. Remove the *  from the excludeDomains field. 

          peerProxy:
            credentialsEnabled: false
            excludeDomains: '*.example.com'
            host: #######.example.com
            port: 3128
            readTimeout: 30
            tlsEnabled: true
  8. Verify all packageDeployments are in a "sucessful" state. 

    root@vsp-6lq8s [ /home/vmware-system-user ]# kubectl get pd -A
    NAMESPACE         NAME                 AGE    PHASE        STATUS
    salt-raas         salt-raas            102d   Successful   successful package deployment
    salt              salt                 102d   Successful   successful package deployment
    telemetry         telemetry-acceptor   102d   Successful   successful package deployment
    vcf-fleet-depot   vcf-fleet-depot      102d   Successful   successful package deployment
    vcf-fleet-lcm     vcf-fleet-lcm        102d   Successful   successful package deployment
    vcf-sddc-lcm      vcf-sddc-lcm         102d   Successful   successful package deployment
    vidb-external     vidb                 102d   Successful   successful package deployment
    vmsp-platform     vmsp-platform        102d   Successful   successful package deployment
  9. Remove the proxy configuration with the vmsp-utility script

    Scripted process to configure a proxy on VCF Management Services and VCF Automation

  10. Configure the proxy configuration again with the vmsp-utility script

    Scripted process to configure a proxy on VCF Management Services and VCF Automation