Bug 1578725
| Summary: | etcd system container code should be cleaned up | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> |
| Component: | Installer | Assignee: | Michael Gugino <mgugino> |
| Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.10.0 | CC: | aos-bugs, jokerman, mmccomas, wmeng |
| Target Milestone: | --- | ||
| Target Release: | 3.11.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-10-11 07:20:00 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
Johnny Liu
2018-05-16 09:48:04 UTC
If we don't consider this to be a 3.10 blocker i'm fine, but if we go that route I think we should block the install when we detect hosts with `containerized=true` or `openshift_use_system_containers=true` After discussion within the team we've decided that this code is necessary to facilitate upgrade and can only be removed in 3.11. This is already complete for 3.11. Verified this bug with openshift-ansible-3.11.0-0.10.0.git.0.91bb588None.noarch, and PASS. Only node_system_container is left, the other are removed. # grep system_container * -r|grep -v openshift-ansible.spec playbooks/openshift-node/private/registry_auth.yml: tasks_from: node_system_container_install.yml roles/openshift_node/tasks/node_system_container.yml:- import_tasks: node_system_container_install.yml roles/openshift_node/tasks/systemd_units.yml: import_tasks: node_system_container.yml 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:2652 |