Scenario 6: Operands Remain Healthy After Restart

Objective: Verify restarted operands function correctly and the HostedCluster remains Available.

Cluster: brcox-88531-hc on Azure dev mgmt cluster — HCP namespace: clusters-brcox-88531-hc

Release image: registry.build10.ci.openshift.org/ci-ln-1qhpr62/release:latest (CNO PR #3030 + HyperShift PR #8751)

Note: Checked immediately after Scenario 5's second rollout (annotation set to 2026-06-17T11:52:52Z).

Overall Scenario 6: PASS

Step	Check	Result	Evidence
1	Restart triggered via `restart-date`	PASS	Two restarts performed (Scenarios 2 and 5); checking health after most recent
2	All CNO operands Running/Ready	PASS	All 4 pods: Ready=true, Restarts=0, Status=Running
3	All deployments successfully rolled out	PASS	All 4 deployments report "successfully rolled out"
4	HCP `Available=True`, `Degraded=False`	PASS	Available=True, Degraded=False, network.operator Available=True
5	HostedCluster `Available=True`, not progressing	PASS	Available=True, Progressing=False, ClusterVersionAvailable=True

Evidence

Step 2 — All CNO operands healthy (captured at 11:56 UTC)

$ oc get pods -n clusters-brcox-88531-hc \
    -o custom-columns='NAME:.metadata.name,READY:.status.containerStatuses[0].ready,RESTARTS:.status.containerStatuses[0].restartCount,STATUS:.status.phase' \
    | grep -E 'NAME|cloud-network-config-controller|multus-admission|network-node-identity|ovnkube-control-plane'
NAME                                                  READY   RESTARTS   STATUS
cloud-network-config-controller-68bbc58f96-brmrw      true    0          Running
multus-admission-controller-6b96956cdc-cdz2h          true    0          Running
network-node-identity-575487f6f7-f42vf                true    0          Running
ovnkube-control-plane-55f85bf477-z8sks                true    0          Running

Step 3 — All deployments rolled out

$ oc rollout status deployment/cloud-network-config-controller -n clusters-brcox-88531-hc
deployment "cloud-network-config-controller" successfully rolled out

$ oc rollout status deployment/multus-admission-controller -n clusters-brcox-88531-hc
deployment "multus-admission-controller" successfully rolled out

$ oc rollout status deployment/network-node-identity -n clusters-brcox-88531-hc
deployment "network-node-identity" successfully rolled out

$ oc rollout status deployment/ovnkube-control-plane -n clusters-brcox-88531-hc
deployment "ovnkube-control-plane" successfully rolled out

Step 4 — HCP conditions

$ oc get hcp brcox-88531-hc -n clusters-brcox-88531-hc \
    -o jsonpath='{range .status.conditions[*]}{.type}{"\t"}{.status}{"\t"}{.message}{"\n"}{end}' \
    | grep -E "Available|Degraded"
EtcdAvailable                                        True
KubeAPIServerAvailable                               True    Kube APIServer deployment is available
Degraded                                             False
Available                                            True
ClusterVersionAvailable                              True    Done applying 5.0.0-0-2026-06-17-110400-test-ci-ln-1qhpr62-latest
DataPlaneConnectionAvailable                         True    All is well
ControlPlaneConnectionAvailable                      True    All is well
network.operator.openshift.io/Degraded               False
network.operator.openshift.io/Available               True

Step 5 — HostedCluster conditions

$ oc get hostedcluster brcox-88531-hc -n clusters \
    -o jsonpath='{range .status.conditions[*]}{.type}{"\t"}{.status}{"\n"}{end}' \
    | grep -E "Available|Progressing|Degraded"
ClusterVersionAvailable          True
ClusterVersionProgressing        False
Degraded                         False
EtcdAvailable                    True
KubeAPIServerAvailable           True
DataPlaneConnectionAvailable     True
ControlPlaneConnectionAvailable  True
Available                        True
IgnitionEndpointAvailable        True
Progressing                      False

← Scenario 5 Dashboard →