-
Bug
-
Resolution: Cannot Reproduce
-
High
-
None
-
OSC 1.10.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
Kata Sprint #270
-
0
OCP 4.18 Azure
OSC version osc-test-fbc-on-push-j5hv6-build-image-index
job.batch/osc-podvm-image-creation finished successfully
completionTime: "2025-06-24T15:40:25Z" conditions: - lastProbeTime: "2025-06-24T15:40:25Z" lastTransitionTime: "2025-06-24T15:40:25Z" message: Reached expected number of succeeded pods reason: CompletionsReached status: "True" type: SuccessCriteriaMet - lastProbeTime: "2025-06-24T15:40:25Z" lastTransitionTime: "2025-06-24T15:40:25Z" message: Reached expected number of succeeded pods reason: CompletionsReached status: "True" type: Complete failed: 1 ready: 0 startTime: "2025-06-24T15:18:10Z" succeeded: 1 terminating: 0 uncountedTerminatedPods: {}
Kataconfig shows that it is still in process
status: conditions: - lastTransitionTime: "2025-06-24T18:09:18Z" message: Creating Pod VM Image reason: PodVMImageJobRunning status: "True" type: InProgress kataNodes: installed: - tbuskey-250624-1-klckr-worker-eastus3-rv6pt - tbuskey-250624-1-klckr-worker-eastus2-fnpn6 nodeCount: 2 readyNodeCount: 2 runtimeClasses: - kata waitingForMcoToStart: false
It used to show a pod for podvm-creation was completed, but I don't think one was run
The empty AZURE_IMAGE_ID in peer-pods-cm is deleted instead of updated with the images
