-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.19.z, 4.20.z, 4.21.0
-
Incidents & Support
-
False
-
-
None
-
None
-
None
-
x86_64
-
Production
-
None
-
None
-
None
-
Customer Escalated
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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:
- clones
-
OCPBUGS-69866 HCP cluster upgrade to 4.19 from 4.18.26 creates a service of type loadbalencer with name router, thereby blocking the upgrade
-
- POST
-
- is cloned by
-
OCPBUGS-70152 HCP cluster upgrade to 4.19 from 4.18.26 creates a service of type loadbalencer with name router, thereby blocking the upgrade
-
- POST
-
- is depended on by
-
OCPBUGS-69866 HCP cluster upgrade to 4.19 from 4.18.26 creates a service of type loadbalencer with name router, thereby blocking the upgrade
-
- POST
-
- links to