Unable to integrate Fleet Management with VCF Operations
search cancel

Unable to integrate Fleet Management with VCF Operations

book

Article ID: 417122

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • Attempting to connect Fleet Management to VCF Operations following Register the VCF Operations fleet management Appliance with VCF Operations, certificate prompt is accepted and the wizard disappears while leaving the status of Fleet Management in 'not connected' state.



  • In /var/log/vrlcm/vmware_vrlcm.log on the Fleet Management appliance, you notice following errors during service account creation:
    INFO vrlcm[1344] [pool-3-thread-85] [c.v.v.l.d.v.VropsEndpoint] – Continue if authorized
    INFO vrlcm[1344] [pool-3-thread-85] [c.v.v.l.p.c.v.t.VropsCreateServiceAccountTask] – Initialized VCF Ops Master Config
    INFO vrlcm[1344] [pool-3-thread-85] [c.v.v.l.d.v.VropsEndpoint] – Request to create service account in Ops : {
    "username" : "username",
    "password" : "password",
    "key" : "key"
    }
    
    INFO vrlcm[####] [pool-3-thread-70] [c.v.v.l.d.v.VropsEndpoint]  -- Create service account Response Code : 500 :: Response Body : {"error_message_key":"security.password.does_not_meet_requirements","error_arguments":KXKXKXKX,"error_message":"New password YXYXYXYX not meet complexity requirements."}
    ERROR vrlcm[[####]] [pool-3-thread-70] [c.v.v.l.p.c.v.t.VropsCreateServiceAccountTask]  -- Error occurred while creating service account Error occurred while creating service account
    INFO vrlcm[[####]] [pool-3-thread-70] [c.v.v.l.p.a.s.Task]  -- Injecting task failure event. Error Code : 'LCMVROPSYSTEM30020', Retry : 'true', Causing Properties : '{ CAUSE ::  }'
    java.lang.RuntimeException: Error occurred while creating service account
    
     
  • Similarly, in /storage/log/vcops/log/casa/casa.log on the VCF Operations appliance, you notice the following errors:
    INFO casa 1709 [ops@4413 threadId="397714" threadName="Thread-45196" requestId=" "] [com.vmware.vcops.casa.fleetmanagement.lcm.LCMInternalService.doLcmCallWithResponse:153] - Request successful for GET request to <https://FleetManagement-URL/lcm/request/api/v2/requests/#####-#####-#####-#####-#####>
    INFO casa 1709 [ops@4413 threadId="397714" threadName="Thread-45196" requestId=" "] [com.vmware.vcops.casa.fleetmanagement.FleetManagementNodeService.run:261] - ADD-FLEET-MANAGEMENT-NODE-WORKFLOW: LCM node state is: FAILED
    ERROR casa 1709 [ops@4413 threadId="397714" threadName="Thread-45196" requestId=" "[com.vmware.vcops.casa.fleetmanagement.FleetManagementNodeService.run:267] - Registration failed
    INFO casa 1709 [ops@4413 threadId="397714" threadName="Thread-45196" requestId=" "][com.vmware.vcops.casa.fleetmanagement.FleetManagementNodeService.run:284] - ADD-FLEET-MANAGEMENT-NODE-WORKFLOW: Cleanup: Closing restTemplate

Environment

VCF Operations 9.x
VCF Fleet Management 9.x

Cause

This issue occurs when there is a stale reference for Fleet Management service account in VCF Operations, originating from past failed attempts.

Resolution

Follow the below steps to resolve the issue:
  1. SSH to Fleet management appliance as root user
  2. Convert the VCF Operations admin credentials to base64 format using following command:
    echo -n 'admin:<VCF_Ops_admin_password>' | base64
  3. Run the following API against VCF Operations to delete service account from the Fleet management appliance:
    curl -k --location --request DELETE 'https://<VCF_OPS_FQDN_IP>/casa/auth/users' \--header 'Accept: application/json' \--header 'Content-Type: application/json' \--header 'Authorization: Basic <base64>' \--data '{ "username": "username reported in vmware_vrlcm.log", "key": "key reported in vmware_vrlcm.log"}'
  4. Login to the admin UI of VCF Operations as admin user ( https://<VCF_OPS_FQDN_IP>/admin )
  5. Connect the Fleet Management to VCF Operations following  Register the VCF Operations fleet management Appliance with VCF Operations.

Additional Information

If the issue persists,  please open a Support Request with Broadcom Technical Support and note this Article ID (417122) in the problem description. For more information, see Creating and managing Broadcom support cases.