Bug 1683762

Summary: Changes to clusteringress.spec.routeSelector are not applied
Product: OpenShift Container Platform Reporter: Dan Mace <dmace>
Component: NetworkingAssignee: Miciah Dashiel Butler Masters <mmasters>
Networking sub component: router QA Contact: Hongan Li <hongli>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs, mmasters
Version: 4.1.0   
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 10:44:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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