Bug 1559799
Summary: | etcd image wasn't updated to comply with osm_etcd_image during the upgrade | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | liujia <jiajliu> |
Component: | Cluster Version Operator | Assignee: | Michael Gugino <mgugino> |
Status: | CLOSED ERRATA | QA Contact: | liujia <jiajliu> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.9.0 | CC: | aos-bugs, jokerman, mmccomas, vwalek, wmeng |
Target Milestone: | --- | ||
Target Release: | 3.10.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: | 2018-07-30 19:10:48 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
liujia
2018-03-23 09:57:33 UTC
*** Bug 1560975 has been marked as a duplicate of this bug. *** Currently, we don't support changing etcd image during upgrade. It looks like we parse the existing image name from a config file on the disk, perform some regex/sed against it, and use that to update the existing etcd image with a new version. Work around for now is to update the image string on ExecStart= line in /etc/systemd/system/{{ etcd_service }}.service to the registry you want prior to upgrade. We should implement this feature. In Master, this can now be set with etcd_image Verified on openshift-ansible-3.10.0-0.50.0.git.0.bd68ade.el7.noarch. after upgrade: # docker images|grep etcd registry.access.redhat.com/rhel7/etcd latest 924412659272 2 weeks ago 256 MB registry.reg-aws.openshift.com:443/rhel7/etcd latest 1c65d1efd289 11 months ago 233 MB Since upgrade failed (track in another issue), for this issue, osm_etcd_image take effect now. Verify this bug. 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-2018:1816 |