Let's say the output of the oc get clusterversion command to YAML or JSON contains the following event.
In this example, the request was to get https://api.openshift.com.
~]$ oc get clusterversion -o yaml
status:
availableUpdates: null
conditions:
- lastTransitionTime: "2021-10-20T07:29:17Z"
message: 'Unable to retrieve available updates: Get "https://api.openshift.com/api/upgrades_info/v1/graph?arch=amd64&channel=stable-4.6&id=d527af50-a959-4f43-aee1-f270a1968962&version=4.6.8": Proxy Error'
reason: RemoteFailed
status: "False"
type: RetrievedUpdates
In this example, the request was to get https://access.redhat.com.
~]$ oc get clusterversion -o yaml
status:
availableUpdates: null
conditions:
- lastTransitionTime: "2021-12-15T07:00:11Z"
message: 'Unable to retrieve available updates: unexpected HTTP status: 504 Gateway Timeout'
reason: ResponseFailed
status: "False"
type: RetrievedUpdates
desired:
image: quay.io/openshift-release-dev/ocp-
release@sha256:d042aa235b538721a39989b13d7d9d3537af9b57e9fd10f485dd04461932ec85
url: https://access.redhat.com/errata/RHBA-2021:3395
version: 4.6.44
If you are unable to ping or lookup api.openshift.com or access.redhat.com, there might be an issue with your internal network, or with api.openshift.com or access.redhat.com.
~]$ nslookup api.openshift.com
Server: 10.14.17.5
Address: 10.14.17.5#53
** server can't find api.openshift.com: NXDOMAIN
The oc get pods command can be used to determine if the cluster-version-operator pod is running.
~]$ oc get pods --namespace openshift-cluster-version
NAMEÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â READYÂ Â STATUSÂ Â Â RESTARTSÂ Â AGE
cluster-version-operator-578cbbcfc7-pgs6m  1/1    Running  2         66d
The oc describe pod command can be used to determine if the cluster-version-operator pod has any interesting events.
~]$ oc describe pod cluster-version-operator-578cbbcfc7-pgs6m --namespace openshift-cluster-version
Events:Â Â Â Â Â Â Â Â Â <none>
The oc get clusteroperator command can be used to determine if any of the cluster operators are unavailable or degraded.
~]$ oc get clusteroperator
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE
authentication 4.6.8 True False False 3d2h
cloud-credential 4.6.8 True False False 363d
cluster-autoscaler 4.6.8 True False False 363d
config-operator 4.6.8 True False False 363d
console 4.6.8 True False False 13d
csi-snapshot-controller 4.6.8 True False False 66d
dns 4.6.8 True False False 234d
etcd 4.6.8 True False False 363d
image-registry 4.6.8 True False False 66d
ingress 4.6.8 True False False 66d
insights 4.6.8 True False False 363d
kube-apiserver 4.6.8 True False False 363d
kube-controller-manager 4.6.8 True False False 363d
kube-scheduler 4.6.8 True False False 363d
kube-storage-version-migrator 4.6.8 True False False 66d
machine-api 4.6.8 True False False 363d
machine-approver 4.6.8 True False False 363d
machine-config 4.6.8 True False False 66d
marketplace 4.6.8 True False False 66d
monitoring 4.6.8 True False False 66d
network 4.6.8 True False False 363d
node-tuning 4.6.8 True False False 234d
openshift-apiserver 4.6.8 True False False 66d
openshift-controller-manager 4.6.8 True False False 3d14h
openshift-samples 4.6.8 True False False 234d
operator-lifecycle-manager 4.6.8 True False False 363d
operator-lifecycle-manager-catalog 4.6.8 True False False 363d
operator-lifecycle-manager-packageserver 4.6.8 True False False 66d
service-ca 4.6.8 True False False 363d
storage 4.6.8 True False False 234d
Did you find this article helpful?
If so, consider buying me a coffee over at 