-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.6.0
-
None
-
False
-
False
-
Quay Enterprise
-
Description of problem:
Deploy Quay by operator 3.5 with managed route, after quay operator uprade from 3.5 to 3.6, the Quay app hostname is changed.
Version-Release number of selected component (if applicable):
quay-operator-bundle-container-v3.6.0-38
- Index image v4.5: registry-proxy.engineering.redhat.com/rh-osbs/iib:113687
Index image v4.6: registry-proxy.engineering.redhat.com/rh-osbs/iib:113690
Index image v4.7: registry-proxy.engineering.redhat.com/rh-osbs/iib:113691
Index image v4.8: registry-proxy.engineering.redhat.com/rh-osbs/iib:113693
Index image v4.9: registry-proxy.engineering.redhat.com/rh-osbs/iib:113695
How reproducible:
always
Steps to Reproduce:
1. Install 3.5 operator, create quayregistry CR, check quay app route
2. Upgrade operator from 3.5 to 3.6 via OLM
3. Check 3.6 operator status, check quay app route
Actual results:
the route hostname is changed
3.5: registry-quay-quay35.router-default.apps.dyan924.qe.devcluster.openshift.com
3.6: registry-quay-quay35.apps.dyan924.qe.devcluster.openshift.com
Expected results:
route hostname keeps the same one
Additional info:
- relates to
-
PROJQUAY-2921 Quay App route hostname is changed when upgrade from 3.4.7 to 3.6.2
- Closed