-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.16.z
-
None
-
Important
-
No
-
False
-
Description of problem:
upgrade osus 5.0.2 to osus 5.0.3, no metadataURI and metadata help container is added, but there will be an meta route created. // before upgrade # ./oc get route NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD sample-route sample-route-openshift-update-service.apps.jliu416.qe.devcluster.openshift.com sample-policy-engine policy-engine edge/None None // after upgrade # ./oc get route NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD sample-meta-route sample-meta-route-openshift-update-service.apps.jliu416.qe.devcluster.openshift.com sample-metadata metadata edge/None None sample-route sample-route-openshift-update-service.apps.jliu416.qe.devcluster.openshift.com sample-policy-engine policy-engine edge/None None # ./oc get po NAME READY STATUS RESTARTS AGE graph-data-tag-digest 1/1 Running 0 3m4s sample-69f4c766cd-hmdbw 2/2 Running 0 20m updateservice-operator-5f7c6595d-4krvn 1/1 Running 0 21m
Version-Release number of selected component (if applicable):
5.0.3-9
How reproducible:
always
Steps to Reproduce:
1. install osus 5.0.2
2. upgrade it to osus 5.0.3
3.
Actual results:
There is unexpected meta route after upgrade 5.0.2 osus without meta container to 5.0.3
Expected results:
No meta route since no meta container
Additional info:
more details refers to https://issues.redhat.com/browse/OTA-1299?focusedId=25066311&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-25066311