Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-2069

kata pods fail to start due to taints

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: High High
    • OSC 1.4.0
    • OSC 1.4.0
    • Operator
    • None
    • False
    • None
    • False
    • Kata Sprint #234
    • 0
    • 0

      Description

      Trying to launch the standard automation pod workload Pod-common.jsonon a cluster (OCP 4.12 or OCP 4.13 on gcp or azure) running OSC 1.4.0-7

      Steps to reproduce

      <What actions did you take to hit the bug?>
      1. build cluster
      2. apply catalog for brew 1.4.0-7 & ICSP
      3. apply the pod workload

      Expected result

      See the pod running

      Actual result

      The pod is pending.

      oc get pod/v9zom8cgexample -o yaml

       

      status:
        conditions:
        - lastProbeTime: null
          lastTransitionTime: "2023-03-08T15:15:34Z"
          message: '0/6 nodes are available: 3 node(s) didn''t match Pod''s node affinity/selector,
            3 node(s) had untolerated taint {node-role.kubernetes.io/master: }, 6 Insufficient
            cpu. preemption: 0/6 nodes are available: 3 No preemption victims found for
            incoming pod, 3 Preemption is not helpful for scheduling.'
          reason: Unschedulable
          status: "False"
          type: PodScheduled
        phase: Pending
        qosClass: BestEffort 
      

      Impact

      Cannot run pods with kata

      Env

       

      Additional helpful info

      OSC 1.4.0-5 works

              jfreiman Jens Freimann
              tbuskey-rh Tom Buskey
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: