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

network-tools pod-run-netns-command failed to get netns pid

XMLWordPrintable

    • Moderate
    • Yes
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Run network-tools pod-run-netns-command, failed to get netns pid     

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

      4.16.0-0.nightly-2024-02-26-013420    

      How reproducible:

      always    

      Steps to Reproduce:

      1. create namespace test, create pod under the namespace
      % oc new-project test
      % oc apply -f pod2.yaml 
      pod/hello-pod2 createds
      % oc get pod -n test
      NAME         READY   STATUS    RESTARTS   AGE
      hello-pod2   1/1     Running   0          7m
      
      2. run network-tools pod-run-netns-command locally 

      Actual results:

      There is error message "ERROR: Can't get netns pid".
      
      $ ./network-tools pod-run-netns-command -it  test hello-pod2 
      Starting pod/qiowang-022910-pl4sf-worker-c-6sxhr-debug ...
      To use host binaries, run `chroot /host`
      
      
      Removing debug pod ...
      error: non-zero exit code from debug container
      ERROR: Can't get netns pid.         <-- error shows
      Running interactive shell for network-tools container.
      To run commands for pod netnamespace use
      
      
      nsenter -n -t parse error: Invalid numeric literal at line 1, column 10
      time="2024-02-29T05:54:18Z" level=error msg="flag provided but not defined: -all," <command>
      
      
      Starting pod/qiowang-022910-pl4sf-worker-c-6sxhr-debug ...
      To use host binaries, run `chroot /host`
      Pod IP: 10.0.128.4
      If you don't see a command prompt, try pressing enter.

      Expected results:

      run command successfuly

      Additional info:

       

            rhn-support-arghosh Arnab Ghosh
            rh-ee-qiowang Qiong Wang
            Qiong Wang Qiong Wang
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: