Bug 1936030
| Summary: | Ingress operator performs spurious updates in response to API's defaulting of NodePort service's clusterIPs field | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Miciah Dashiel Butler Masters <mmasters> |
| Component: | Networking | Assignee: | Miciah Dashiel Butler Masters <mmasters> |
| Networking sub component: | router | QA Contact: | Hongan Li <hongli> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | aos-bugs |
| Version: | 4.8 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-27 22:51:38 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1937214 | ||
verified with 4.8.0-0.nightly-2021-03-15-203554 and passed.
just saw one "created NodePort service" message in the log.
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.8.0-0.nightly-2021-03-15-203554 True False 7h2m Cluster version is 4.8.0-0.nightly-2021-03-15-203554
$ oc -n openshift-ingress-operator logs deploy/ingress-operator -c ingress-operator | grep NodePort
2021-03-16T08:41:55.831Z INFO operator.ingress_controller ingress/controller.go:677 created NodePort service{"service": "&Service{ObjectMeta:{router-nodeport-nodeport openshift-ingress 6b76bca0-092e-4629-bb92-f4f4e276f18a 229482 0 2021-03-16 08:41:55 +0000 UTC <nil> <nil> map
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438 |
Description of problem: When the ingress operator reconciles an ingresscontroller that has the "NodePortService" endpoint publishing strategy type, the operator gets the ingresscontroller's nodeport service (if one exists) from the API to determine whether the operator needs to create or update the service. If the service does not exist, the operator creates it, and if the service does exist, the operator compares it with what the operator expects to get in order to determine whether an update is needed for that service. In this comparison, if the API has set a value for the service's clusterIPs field, the operator detects the update and tries to set the clusterIPs field back to the empty value. The operator should not update the service in response to API defaulting. Version-Release number of selected component (if applicable): The clusterIPs field is new in Kubernetes 1.20 (OpenShift 4.7). Steps to Reproduce: 1. Launch a new cluster. 2. Create an ingresscontroller with the "NodePortService" endpoint publishing strategy: oc create -f - <<'EOF' apiVersion: operator.openshift.io/v1 kind: IngressController metadata: name: nodeport namespace: openshift-ingress-operator spec: replicas: 1 domain: example.com endpointPublishingStrategy: type: NodePortService EOF 3. Check the ingress operator's logs: oc -n openshift-ingress-operator logs deploy/ingress-operator -c ingress-operator Actual results: The ingress operator's logs have "updated NodePort service" repeated several times. Expected results: The ingress operator should ignore the clusterIPs field's value and should not log "updated NodePort service" unless the service is updated outside of API defaulting.