Uipathctl health check failure due to issue with versions

What to do if uipathctl health check fails due to issue with versions?

Issue Description

When using uipathctl health * for AS diagnostics or health checks, if the error "Error: cannot set versions into contest from cluster: failed to load versions from secret: vendor charts object is illegal: name, version and ref cannot be nil but found" appears, it could be issue with the versions configured in the AS as opposed to versions.json.

Resolution

To confirm the issue:

  1. Execute "kubectl get secret -n uipath uipath-versions -o jsonpath='{.data.versions\.json}' | base64 -d | jq"
  2. Compare the output with versions.json

If there are any differences with respect to keys and values:

  1. Copy the text of versions.json to a text editor, remove spaces and newlines (If the jump server is Linux, execute cat versions.json | jq -c | base64)
  2. Base64 encode it
  3. Execute "kubectl edit secret -n uipath uipath-versions"
  4. Replace the value of versions.json key in the secret with the base64 encoded text
  5. Save the secret
  6. Run the uipath health check again to confirm if the issue is resolved