Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-20487

Missing 'ping' executable file on s390x node in origin tests:[sig-network][Feature:EgressFirewall]

    XMLWordPrintable

Details

    • No
    • Multi-Arch Sprint 247, Multi-Arch Sprint 248, Multi-Arch Sprint 249
    • 3
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      1. [sig-network][Feature:EgressFirewall] egressFirewall should have no impact outside its namespace [Suite:openshift/conformance/parallel] 
      2. [sig-network][Feature:EgressFirewall] when using openshift ovn-kubernetes should ensure egressfirewall is created [Suite:openshift/conformance/parallel]
      
      The issue arises during the execution of the above tests and appears to be related to the image in use, specifically, the image located at https://quay.io/repository/redhat-developer/nfs-server?tab=tags&tag=1.1 (quay.io/redhat-developer/nfs-server:1.1). 
      This image does not include the 'ping' executable for the s390x architecture, leading to the following error in the prow job logs:
      ...
      msg: "Error running /usr/bin/oc --namespace=e2e-test-no-egress-firewall-e2e-6mg9v --kubeconfig=/tmp/configfile3768380277 exec dummy -- ping -c 1 8.8.8.8:\nStdOut>\ntime=\"2023-10-11T19:04:52Z\" level=error msg=\"exec failed: unable to start container process: exec: \\\"ping\\\": executable file not found in $PATH\"\ncommand terminated with exit code 255\nStdErr>\ntime=\"2023-10-11T19:04:52Z\" level=error msg=\"exec failed: unable to start container process: exec: \\\"ping\\\": executable file not found in $PATH\"\ncommand terminated with exit code 255\nexit status 255\n"
      ...
      
      Our suggest fix: build new s390x image that contains ping binary.

      Version-Release number of selected component (if applicable):

       

      How reproducible:

      The issue is reproducible when the test container (quay.io/redhat-developer/nfs-server:1.1) is scheduled on an s390x node, leading to test failures.

      Steps to Reproduce:

      1.Have a multi-arch cluster (x86 + s390x day2 worker node attached)
      2.Execute the two tests
      3.Try few times to make the pod assigned to s390x node

      Actual results from prow job:

      Run #0: Failed expand_less30s{  fail [github.com/openshift/origin/test/extended/networking/egress_firewall.go:70]: Unexpected error:
          <*fmt.wrapError | 0xc005924300>: 
          Error running /usr/bin/oc --namespace=e2e-test-no-egress-firewall-e2e-6r9zh --kubeconfig=/tmp/configfile3961753222 exec dummy -- ping -c 1 8.8.8.8:
          StdOut>
          time="2023-10-12T07:17:02Z" level=error msg="exec failed: unable to start container process: exec: \"ping\": executable file not found in $PATH"
          command terminated with exit code 255
          StdErr>
          time="2023-10-12T07:17:02Z" level=error msg="exec failed: unable to start container process: exec: \"ping\": executable file not found in $PATH"
          command terminated with exit code 255
          exit status 255
          
          {
              msg: "Error running /usr/bin/oc --namespace=e2e-test-no-egress-firewall-e2e-6r9zh --kubeconfig=/tmp/configfile3961753222 exec dummy -- ping -c 1 8.8.8.8:\nStdOut>\ntime=\"2023-10-12T07:17:02Z\" level=error msg=\"exec failed: unable to start container process: exec: \\\"ping\\\": executable file not found in $PATH\"\ncommand terminated with exit code 255\nStdErr>\ntime=\"2023-10-12T07:17:02Z\" level=error msg=\"exec failed: unable to start container process: exec: \\\"ping\\\": executable file not found in $PATH\"\ncommand terminated with exit code 255\nexit status 255\n",
              err: <*exec.ExitError | 0xc0059242e0>{
                  ProcessState: {
                      pid: 78611,
                      status: 65280,
                      rusage: {
                          Utime: {Sec: 0, Usec: 168910},
                          Stime: {Sec: 0, Usec: 60897},
                          Maxrss: 206428,
                          Ixrss: 0,
                          Idrss: 0,
                          Isrss: 0,
                          Minflt: 4199,
                          Majflt: 0,
                          Nswap: 0,
                          Inblock: 0,
                          Oublock: 0,
                          Msgsnd: 0,
                          Msgrcv: 0,
                          Nsignals: 0,
                          Nvcsw: 753,
                          Nivcsw: 149,
                      },
                  },
                  Stderr: nil,
              },
          }
      occurred
      Ginkgo exit error 1: exit with code 1}

      Expected results:

      Passed

      Additional info:

      This issue pertains to a specific bug on the s390x architecture and additionally impacts the libvirt-s390x prow job.

      Attachments

        Issue Links

          Activity

            People

              apuranda Amrut Purandare
              chinchen CHING HAN CHEN
              Florian Leber Florian Leber
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: