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

chk_default_ingress perma-failing

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • Done
    • Bug Fix
    • Hide
      One of the keepalived health check scripts was failing due to missing permissions. This could cause the ingress VIP to be misplaced when sharded ingress services are in use. The necessary permission was added back to the container so the check will work correctly now.
      Show
      One of the keepalived health check scripts was failing due to missing permissions. This could cause the ingress VIP to be misplaced when sharded ingress services are in use. The necessary permission was added back to the container so the check will work correctly now.
    • None
    • None
    • None
    • None

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

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

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

      Description of problem:

      The chk_default_ingress script used by keepalived to determine where the ingress VIP should be located is perma-failing at least back to 4.17. In clusters with sharded ingress, this can cause the VIP to be placed on a node hosting a shard and not the default ingress, which breaks access to core ingress services.

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

      Initially reported against 4.17.23, but also present on 4.19.

      How reproducible:

      Always

      Steps to Reproduce:

          1. Deploy on-prem IPI cluster
          2. Check keepalived logs on the node holding the ingress VIP
          3.
          

      Actual results:

          chk_default_ingress check failing

      Expected results:

      chk_default_ingress check passing    

      Additional info:

          It looks like this is a permission problem. The chroot into /host is failing.

       

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

                Created:
                Updated:
                Resolved: