Already fixed as part of ovn21.12-21.12.0-25.el8fdp
[smalleni@localhost kubelet-density]$ ./kube-burner init -c kubelet-density/kubelet-density.yml INFO[2022-03-09 11:30:56] 🔥 Starting kube-burner (0.15.2@1a59017bd3e97f98c5fdcca80b906be31250b465) with UUID 9d3fd660-b74f-496b-85cc-2422cea716a3 FATA[2022-03-09 11:30:56] Error reading configuration file kubelet-density/kubelet-density.yml: kubelet-density/kubelet-density.yml is not a valid URL [smalleni@localhost kubelet-density]$ ./kube-burner init -c kubelet-density.yml INFO[2022-03-09 11:31:02] 🔥 Starting kube-burner (0.15.2@1a59017bd3e97f98c5fdcca80b906be31250b465) with UUID 86a8511a-9724-4f53-9b18-cee641fefba3 true INFO[2022-03-09 11:31:02] 📁 Creating indexer: elastic INFO[2022-03-09 11:31:03] 📈 Creating measurement factory INFO[2022-03-09 11:31:03] Registered measurement: podLatency INFO[2022-03-09 11:31:03] Preparing create job: kubelet-density INFO[2022-03-09 11:31:03] Job kubelet-density: 2000 iterations with 1 Pod replicas INFO[2022-03-09 11:31:03] Job kubelet-density: 2000 iterations with 1 Service replicas INFO[2022-03-09 11:31:03] Triggering job: kubelet-density INFO[2022-03-09 11:31:04] Creating Pod latency watcher for kubelet-density INFO[2022-03-09 11:31:05] QPS: 50 INFO[2022-03-09 11:31:05] Burst: 50 INFO[2022-03-09 11:31:05] Running job kubelet-density INFO[2022-03-09 11:33:18] Waiting 3h0m0s for actions to be completed INFO[2022-03-09 11:33:22] Actions in namespace kubelet-density completed INFO[2022-03-09 11:33:22] Finished the create job in 137.641136757 seconds INFO[2022-03-09 11:33:22] Verifying created objects INFO[2022-03-09 11:33:25] pods found: 2000 Expected: 2000 INFO[2022-03-09 11:33:25] services found: 2000 Expected: 2000 INFO[2022-03-09 11:33:25] Stopping measurement: podLatency INFO[2022-03-09 11:33:25] Evaluating latency thresholds INFO[2022-03-09 11:33:25] Avg Ready latency (3235ms) meets the configured threshold: 4s INFO[2022-03-09 11:33:25] Writing latency metrics in collected-metrics/kubelet-density-podLatency.json INFO[2022-03-09 11:33:25] Writing latency metrics in collected-metrics/kubelet-density-podLatency-summary.json INFO[2022-03-09 11:33:26] Indexing [2000] documents in kube-burner INFO[2022-03-09 11:33:28] Indexing finished in 1.927s: created=2000 INFO[2022-03-09 11:33:28] Indexing [4] documents in kube-burner INFO[2022-03-09 11:33:28] Indexing finished in 467ms: created=4 INFO[2022-03-09 11:33:28] Job kubelet-density took 145.45 seconds INFO[2022-03-09 11:33:28] Writing to: collected-metrics/kubelet-density-metadata.json INFO[2022-03-09 11:33:28] Indexing metadata information for job: kubelet-density INFO[2022-03-09 11:33:28] Indexing [1] documents in ripsaw-kube-burner INFO[2022-03-09 11:33:28] Indexing finished in 74ms: created=1 INFO[2022-03-09 11:33:28] Finished execution with UUID: 86a8511a-9724-4f53-9b18-cee641fefba3 INFO[2022-03-09 11:33:28] 👋 Exiting kube-burner [smalleni@localhost kubelet-density]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-0.nightly-2022-03-07-110955 True False 40m Cluster version is 4.9.0-0.nightly-2022-03-07-110955
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.9.24 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:0798