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

Default ingress check not working

    XMLWordPrintable

Details

    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      This is a clone of issue OCPBUGS-15613. The following is the description of the original issue:

      Description of problem:

      The chk_default_ingress.sh script for keepalived is not correctly matching the default ingress pod name anymore. The pod name in a recently deployed dev-scripts cluster is router-default-97fb6b94c-wfxfk which does not match our grep pattern of router-default-[[:xdigit:]]\\{10}-[[:alnum:]]
      {5}{
      }. The main issue seems to be that the first id is only 9 digits, not 10.

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

      4.14

      How reproducible:

      Unsure, but has been seen at least twice

      Steps to Reproduce:

      1. Deploy recent nightly build
      2. Look at chk_default_ingress status
      3.
      

      Actual results:

      Always failing, even on nodes with the default ingress pod

      Expected results:

      Passes on nodes with default ingress pod

      Additional info:

       

      Attachments

        Issue Links

          Activity

            People

              bnemec@redhat.com Benjamin Nemec
              openshift-crt-jira-prow OpenShift Prow Bot
              Zhanqi Zhao Zhanqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: