-
Bug
-
Resolution: Cannot Reproduce
-
Low
-
None
-
OSC 1.5.2
-
None
-
False
-
None
-
False
-
-
-
0
-
0
-
High
OCP 4.14 OSC 1.5.2 for testing upgrades
2 azure-image-creation pods ran simultaneously
One created
/subscriptions/../resourceGroups/tbuskey-240418-2-xspxg-rg/providers/Microsoft.Compute/images/peer-pod-vmimage-6375b0
the other created
/subscriptions/.../resourceGroups/tbuskey-240418-2-xspxg-rg/providers/Microsoft.Compute/images/peer-pod-vmimage-2a36ba
(the full log was not captured)
This was the one that got put into the peer-pod-cm
Once kataconfig finished installing, there was an ARM vm left running.
I was able to run a kata workload, but the kata-remote pods were stuck on ContainerCreating
logs & events from the peerpodconfig-ctrl-caa-daemon pods
peerpodconfig-ctrl-caa-daemon1.logpeerpodconfig-ctrl-caa-daemon2.logpeerpodconfig-ctrl-caa-daemon3.log
peerpodconfig-ctrl-caa-daemon.event1.logpeerpodconfig-ctrl-caa-daemon.event3.log peerpodconfig-ctrl-caa-daemon.event3.log