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

False logs in "var/log/agent/agent-tui.log " ping to "quay.io"

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      The `agent-gather` collected from the nodes will show the ping failure to the `quay.io` whereas in reality no one can ping to quay.io as it seems.
      
      ~~~~
      level=warning msg="ReleaseImageHostPing check failed with error: PING quay.io (35.170.31.10) 56(84) bytes of data.\n\n--- quay.io ping statistics ---\n4 packets transmitted, 0 received, 100% packet loss, time 3109ms\n\n"
      ~~~~
      
      Ex: From any machine connected to internet can't ping to quay.io or IP's of it.
      
      ~~~
      $ ping -c 4 quay.io
      PING quay.io (3.217.61.179) 56(84) bytes of data.--- quay.io ping statistics ---
      4 packets transmitted, 0 received, 100% packet loss, time 3102ms
      ~~~
      
       The curl command do produce a productive output.
      
      This misleads the logs checks for the support engineers, hence these logs either shall be omitted or  precised more with other tools.

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

      Any    

      How reproducible:

          ping quay.io 

       

      Actual results:

      The ping never works and 100% packet loss happens always.    

      Expected results:

      There shall be another measure to do the connectivity check with quay.io    

      Additional info:

          

              rwsu1@redhat.com Richard Su
              rhn-support-pkhedeka Parikshit Khedekar
              None
              None
              Manoj Hans Manoj Hans
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: