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

HCP cluster upgrade to 4.19 from 4.18.26 creates a service of type loadbalencer with name router, thereby blocking the upgrade

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.19.z, 4.20.z, 4.21.0, 4.22.0
    • HyperShift
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • x86_64
    • Production
    • None
    • Rejected
    • None
    • In Progress
    • Bug Fix
    • Hide
      This update corrects the route labeling logic for HCP router infrastructure, preventing the creation of an additional loadbalancer service. This change allows the upgrade from 4.18 to 4.19 to proceed without being blocked by additional loadbalancer service creation.
      Show
      This update corrects the route labeling logic for HCP router infrastructure, preventing the creation of an additional loadbalancer service. This change allows the upgrade from 4.18 to 4.19 to proceed without being blocked by additional loadbalancer service creation.
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-75930. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-70152. The following is the description of the original issue:
      —
      Description of problem:

      
After triggering an upgrade for a HCP cluster from 4.18.26 to 4.19, a service of type loadbalencer gets created with name router. Since this service does not get an IP from an IPaddressPool, the cluster gets stuck here and upgrade does not get triggered. This service is created automatically and blocks upgrade from getting triggered.

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

      
upgrade from 4.18 to 4.19
ClientVersion: 4.18.22
ACM Version: 2.14.1
MCE Version: 2.9.1

      How reproducible:

      
2 attempts out of 2 (100%)

      Steps to Reproduce:

          1. start the upgrade
    2. service of type loadbalancer with name router is created
    3. upgrade plocked

      Actual results:

      Expected results:

      
upgrade completes

      Additional info:

              asegurap1@redhat.com Antoni Segura Puimedon
              rhn-support-brstone Brian Stone
              None
              Antoni Segura Puimedon
              Yu Li Yu Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: