-
Bug
-
Resolution: Done
-
Normal
-
4.13, 4.12, 4.14, 4.15, 4.16, 4.17
-
Moderate
-
None
-
5
-
OSDOCS Sprint 258
-
1
-
False
-
Description of problem:
When attempting to annotate ingress controller and route, first create the route without the annotation and then annotate using OC command or apply annotated route yaml. if you attempt to add the annotation without the route not being present an error occurs
Version-Release number of selected component (if applicable):
OCP-4.16 and OCP-4.17
How reproducible:
Always
Steps to Reproduce:
1. Navigate to ingress controller doc, converting HTTP header case: https://docs.openshift.com/container-platform/4.16/networking/ingress-operator.html#nw-ingress-converting-http-header-case_configuring-ingress 2. Attempt step 2 for the annotation (route is not available) 3. Attempt to apply route YAML, get an error
Actual results:
oc annotate routes/my-application haproxy.router.openshift.io/h1-adjust-case=true Error from server (NotFound): routes.route.openshift.io "my-application" not found oc apply -f route.yaml error: unable to decode "route.yaml": json: cannot unmarshal bool into Go struct field ObjectMeta.metadata.annotations of type string
Expected results:
my-application route should successfully be annotated
Additional info:
should add a portion to create the my-application route using YAML below first, then use oc command/ apply yaml to annotate route apiVersion: route.openshift.io/v1 kind: Route metadata: name: my-application namespace: default spec: to: kind: Service name: my-application
- links to
(2 links to)