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

CoCo pods in AWS stay in terminating state

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: High High
    • None
    • None
    • Operator, podvm
    • None
    • False
    • None
    • False
    • 0
    • 0

      Description

      Run the sig-kata automation on coco workloads with incluster trustee

      Tests fail until they time out or I manually kill the pods with --force

       

      for i in $(oc get ns | egrep 'e2e' | cut -d' ' -f1); do echo $i ;oc get -n $i pod,deploy;done
      e2e-test-kata-968jb

       

       

       

      NAME                                      READY   STATUS        RESTARTS   AGE
      pod/dep-63121-lr85v7b7-785bc76dc9-85r6t   0/1     Terminating   1          70m
      pod/dep-63121-lr85v7b7-785bc76dc9-z2hhj   0/1     Terminating   1          70m
      e2e-test-kata-d6m57
      NAME                                      READY   STATUS        RESTARTS   AGE
      pod/dep-60233-t19hy4k6-6cf578b49f-5gjv2   0/1     Terminating   0          64m

       

       

      controller-manager.logpeerpodconfig-ctrl-caa-daemon-1.logpeerpodconfig-ctrl-caa-daemon-2.log

      testrun.log

      testrun.log

       

      One of the podvms stays around

      OCP 4.17.8 on AWS.

      OSC GA 1.8.1

      trustee GA 0.2.0

       

              ssheribe@redhat.com Snir sheriber
              tbuskey-rh Tom Buskey
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: