Bug 1687976
| Summary: | UPGRADE: dns node resolver container is not updated | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Derek Carr <decarr> |
| Component: | Networking | Assignee: | Dan Mace <dmace> |
| Networking sub component: | router | QA Contact: | Hongan Li <hongli> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | aos-bugs, dmace, sponnaga, trankin |
| Version: | 4.1.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Node resolver uses openshift-cli image and the image update is not handled by the operator
Consequence: After Cluster upgrade, openshift still has old openshift-cli image.
Fix: Update DNS operator to handle openshift-cli image update.
Result: Cluster upgrade will move the openshift-cli image to the new version as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:45:33 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
Derek Carr
2019-03-12 19:39:24 UTC
verified with upgrading from 4.0.0-0.nightly-2019-03-15-043409 to 4.0.0-0.nightly-2019-03-18-200009 and the issue has been fixed.
before upgrade:
$ oc get deployment -n openshift-dns-operator -o yaml | grep quay
value: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b9e3107ae30e589be00c2c28fab543e0c05a1dff5188de479cf37693834eabe1
value: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:bf1f556c9abacfa8ed8a2eacb10d47c5c369c4217d866e8a88cdccf2be33d17a
image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:e8855628583840d826092c00fdbab15aa1129bd127c5545a988da5ce0ca67487
$ oc get ds -n openshift-dns -o yaml | grep quay
image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b9e3107ae30e589be00c2c28fab543e0c05a1dff5188de479cf37693834eabe1
image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:bf1f556c9abacfa8ed8a2eacb10d47c5c369c4217d866e8a88cdccf2be33d17a
after upgrade:
$ oc get deployment -n openshift-dns-operator -o yaml | grep quay
value: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b9e3107ae30e589be00c2c28fab543e0c05a1dff5188de479cf37693834eabe1
value: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0d489c04afac2d3b088bd9139deae1c0bbb267ba132576e41f261da9bcc41360
image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:05e305037ad450a37c9e142580854e61d102161dad6d1e3d42856aea1f9ece0b
$ oc get ds -n openshift-dns -o yaml | grep quay
image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b9e3107ae30e589be00c2c28fab543e0c05a1dff5188de479cf37693834eabe1
image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0d489c04afac2d3b088bd9139deae1c0bbb267ba132576e41f261da9bcc41360
# oc adm release info --pullspecs "registry.svc.ci.openshift.org/ocp/release:4.0.0-0.nightly-2019-03-18-200009" | grep cli
cli quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0d489c04afac2d3b088bd9139deae1c0bbb267ba132576e41f261da9bcc41360
The container dns-node-resolver is updated after upgrading.
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 |