-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
4.19
-
None
-
None
-
Proposed
-
False
-
Description of problem:
After loading the cluster using kube-burner-ocp node-density-heavy workload. I deleted the objects and the network operator became in a degraded state
https://kube-burner.github.io/kube-burner-ocp/latest/#node-density-heavy
Version-Release number of selected component (if applicable):
4.19.0-0.nightly-2025-03-03-170005
How reproducible:
Unknown
Steps to Reproduce:
1. Create Azure Ipsec cluster with 4.19.0-0.nightly-2025-03-03-170005
2. Load cluster with node-density-heavy objects with 245 pods per node
3. Check cluster operators
4. Delete namespaces create from node-density-heavy workload
5. Check cluster operators, network operator
Actual results:
03-04 18:27:51.483 ClusterID: 9f09ec64-3bdc-4631-9f3b-2109c8a3706f
03-04 18:27:51.483 ClientVersion: 4.19.0-202502250109.p0.g554ecb2.assembly.stream-554ecb2
03-04 18:27:51.483 ClusterVersion: Stable at "4.19.0-0.nightly-2025-03-03-170005"
03-04 18:27:51.483 ClusterOperators:
03-04 18:27:51.483 clusteroperator/network is degraded because DaemonSet "/openshift-ovn-kubernetes/ovn-ipsec-host" rollout is not making progress - pod ovn-ipsec-host-kg7c8 is in CrashLoopBackOff State
Expected results:
Cluster operators are all available without error after object deletion
Additional info:
https://jenkins-csb-openshift-qe-mastern.dno.corp.redhat.com/job/scale-ci/job/e2e-benchmarking-multibranch-pipeline/job/must-gather/690/console
