Medium Description
OSC 1.5.0-19 installed with peerpodsEnabled.
Steps to reproduce
<What actions did you take to hit the bug?>
1. Create a pod with kata-remote-cc in the openshift-sandboxed-containers-operator namespace
2. create a new namespace e2e-test-kata-6m4gw
3. Create same pod in this namespace.
Expected result
The pod is Running. A 2nd podVM is in azure
Actual result
Pod will never leave Pending state
pod/tpb-exapod 0/1 Pending 0 7m59s
oc delete pod/tpb-exapod -n openshift-sandboxed-containers-operator has no effect
Additional helpful info
oc events -n e2e-test-kata-6m4gw
LAST SEEN TYPE REASON OBJECT MESSAGE
18m (x5 over 24m) Warning FailedScheduling Pod/60dx8d4jexample 0/6 nodes are available: 3 Insufficient kata.peerpods.io/vm, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/6 nodes are available: 3 No preemption victims found for incoming pod, 3 Preemption is not helpful for scheduling..
13m Warning FailedScheduling Pod/60dx8d4jexample skip schedule deleting pod: e2e-test-kata-6m4gw/60dx8d4jexample
88s (x5 over 8m59s) Warning FailedScheduling Pod/tpb-exapod 0/6 nodes are available: 3 Insufficient kata.peerpods.io/vm, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/6 nodes are available: 3 No preemption victims found for incoming pod, 3 Preemption is not helpful for scheduling..
- is documented by
-
HCIDOCS-103 Add note not to create workloads in OSC operator namespace
-
- Closed
-
- is related to
-
-
- Closed
-
