Bug 1683762 - Changes to clusteringress.spec.routeSelector are not applied
Summary: Changes to clusteringress.spec.routeSelector are not applied
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.1.0
Assignee: Miciah Dashiel Butler Masters
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-27 18:12 UTC by Dan Mace
Modified: 2022-08-04 22:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-04 10:44:39 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-ingress-operator pull 147 0 None closed Improve and expand checks in deploymentConfigChanged 2020-08-11 21:20:51 UTC
Red Hat Product Errata RHBA-2019:0758 0 None None None 2019-06-04 10:44:45 UTC

Description Dan Mace 2019-02-27 18:12:49 UTC 
Description of problem:

Changes to the clusteringress.spec.routeSelector field are not applied to the cluster.


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


How reproducible:

`oc edit -n openshift-ingress-operator/default` and set a new value for `.spec.routeSelector`.


Actual results:

The ingress-operator does not update the router deployment with the new route selector value.

Expected results:

The routers for the clusteringress should be redeployed using the new route selector value.

Additional info:
Comment 3 Hongan Li 2019-03-14 07:08:58 UTC 
verified with 4.0.0-0.nightly-2019-03-13-233958 and the issue has been fixed.

add routeSelector below to ingresscontroller and the deployment is updated accordingly:
```
spec:
  routeSelector:
    matchLabels:
      route: red
```

$ oc get deployment -n openshift-ingress -o yaml | grep route=red -B 1
          - name: ROUTE_LABELS
            value: route=red
Comment 5 errata-xmlrpc 2019-06-04 10:44:39 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0758
Note You need to log in before you can comment on or make changes to this bug.