Bug 1401401 - [REF] preserve systemd configuration in upgrade
Summary: [REF] preserve systemd configuration in upgrade
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-05 07:17 UTC by Anping Li
Modified: 2019-01-31 16:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-31 16:00:40 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Anping Li 2016-12-05 07:17:10 UTC
Description of problem:
openshift-ansible will update the systemd configuration. For example: when migrate to docker-1.12, TasksMax=infinity was added to /usr/lib/systemd/system/docker.service  and  docker-sdn-ovs.conf was removed. 

For the purpose of Rollback, it is better to backup the systemd configuration files before upgrade.



Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
Steps to Reproduce:
1. install OCP 3.3 
    save the /usr/lib/systemd/system/docker.service
             /usr/lib/systemd/system/docker.service.d/docker-sdn-ovs.conf
2. upgrade to OCP 3.4
3. check the  systemd configure file again.
  save the /usr/lib/systemd/system/docker.service
           /usr/lib/systemd/system/docker.service.d/docker-sdn-ovs.conf

Actual results:
The systemd configure file are modified. but the origin configuation file weren't saved.

Expected results:


Additional info:

Comment 1 Scott Dodson 2016-12-05 14:43:47 UTC
Anping,

If you were to downgrade packages aren't both of those restored?

--
Scott

Comment 2 Anping Li 2016-12-06 01:31:41 UTC
Some configuration are written by ansible template. For example: atomic-openshift-master-api.  
For containerized Env, no package can be restored.

Comment 3 Scott Dodson 2019-01-31 16:00:40 UTC
There appear to be no active cases related to this bug. As such we're closing this bug in order to focus on bugs that are still tied to active customer cases. Please re-open this bug if you feel it was closed in error or a new active case is attached.


Note You need to log in before you can comment on or make changes to this bug.