Why does the Network status show an NHC001 error?

Virtual Private Cloud Classic infrastructure

When you check the status of your cluster's health by running the ibmcloud oc cluster health issues --cluster <CLUSTER_ID>, you see an error similar to the following example.

ID       Component   Severity   Description
NHC001   Network     Warning    Tigera operator has been reporting that Calico is in 'progressing' state for over an hour.

This warning means the Tigera operator has been reporting that Calico is stuck in a 'progressing' state, potentially due to component deployment delays or underlying issues.

Investigate the logs of the Tigera operator and Calico components to understand what is preventing Calico from reaching a healthy state.

1. Check Tigera status custom resources and conditions. Look for "conditions" with "Progressing": true.

   kubectl get tigerastatus -o yaml
   

   kubectl get tigerastatus calico -o yaml
   

2. Check Calico and Calico-typha components status by listing Calico pods in calico-system. namespace:

   kubectl get pods -n calico-system
   

   Check the rollout status of deployments and daemonset.

   kubectl rollout status deployment/calico-kube-controllers -n calico-system
   kubectl rollout status deployment/calico-typha -n calico-system
   kubectl rollout status daemonset/calico-node -n calico-system
   

3. If pods are not ready or stuck in Init or CrashLoopBackOff, get logs:

   kubectl logs <pod-name> -n calico-system
   

4. Wait for components to complete rollout. After addressing any issues (e.g., CrashLoopBackOff, image pull errors), wait a few minutes for Tigera to refresh the state.

5. For more information, see Controlling traffic with network policies and Debugging Calico components

6. If the issue continues, contact support for assistance. Open a support case. In the case details, be sure to include any relevant log files, error messages, or command outputs.