Conflict [409]: Failed to post cluster state to

Products

• CloudHealth

Issue/Introduction

Reviewing the collector logs, seeing entire(s). 

ERROR -- : Conflict [409]: Failed to post cluster state to https://containers-api.edge.cloudhealthtech.com/v2/containers/kubernetes/state?cluster_id=<clusterName>&sample_time=<UTC TimeStamp>&k8s_object_type=resourcequotas&k8s_agent_version=1500&cluster_uid=<CHclusterName>&auth_token=API_TOKEN_REDACTED. Error: \{"messages":"Unable to collect. Cluster <clusterName>(UID: <uniqueID>) has been permanently deactivated."\}}

Resolution

Check the CloudHealth UI for the CH Cluster Name as Active or Deactivated.

1. Login to the Tenant.
2. Go to Setup > Containers > Clusters
3. Select "Deactivated" from ACTIVE CLUSTERS Dropdown to verify the cluster status.

The variable CHT_CLUSTER_NAME is a unique identifier in CloudHealth. "Deactivated" CloudHealth Clusters are not able to be reactivated. 

Redeploy a new collector in the existing Kubernetes cluster, using a unique CHT_CLUSTER_NAME.

Additional Information

Getting Started with Kubernetes

Inspect Collector Logs

For additional support or questions on deploying a CloudHealth collector open a support ticket at Support@Broadcom.