Bug 1317851
Summary: | openvswitch isn't restart during upgrade | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Anping Li <anli> |
Component: | Cluster Version Operator | Assignee: | Brenton Leanhardt <bleanhar> |
Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.2.0 | CC: | aos-bugs, bleanhar, jdetiber, jokerman, mmccomas, tdawson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openshift-ansible-3.0.67-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-12 16:33:10 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
Anping Li
2016-03-15 11:10:14 UTC
Basically, I think the following needs to happen: On upgrade from 3.1 -> 3.2, we will need to modify the systemd unit files for the containerized components to include the latest dependencies and ordering prior to restarting services/docker on the hosts. Brenton, One thing that I'm wondering about, would it make sense to re-apply the systemd unit templates in this case rather than modifying parts of the files on disk? We could use the relative path to the templates from the roles (or a symlink in the upgrade playbook directory). Yeah, that would probably make more sense. How much refactoring would be needed to make that possible? Would we create separate roles for the systemd units or are you saying simply to create a new task in the upgrade playbooks that reuse the existing templates and set any needed variable appropriately? I'm suggesting using the existing templates in the roles directories from the upgrade playbooks. The easiest way would probably be to symlink the templates into the upgrade subdirectory. I found this bug have been fixed in atomic-openshift-utils-3.0.64, shall we move it to ON_QA? We're having to do a bit of refactoring to the way the systemd units are installed. I'd prefer to retest this bug once I'm done with that. The openvswitch can be restarted on openshift-ansible-3.0.67-1 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/RHSA-2016:1064 |