Bug 1744580 - MachineConfig updates cause unexpected results for static pod manifests
Summary: MachineConfig updates cause unexpected results for static pod manifests
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.2.0
Assignee: Antonio Murdaca
QA Contact: Micah Abbott
URL:
Whiteboard:
: 1734483 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-22 13:21 UTC by Sam Batschelet
Modified: 2019-11-12 22:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:37:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 1075 0 None None None 2019-08-22 13:28:43 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:37:27 UTC

Description Sam Batschelet 2019-08-22 13:21:35 UTC
Description of problem: When a MC update is made the MCD will append the extension `mcdorig`[1] to the file being replaced on disk.


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


How reproducible: always


Steps to Reproduce:
1. Update static pod manifest, for example, etcd-member.yaml with MC removing a container such as etcd-metrics.
2. After update review Kube logs and running containers you should see the manifest with mcdorig being consumed by the kubelet and etcd-metrics running.
3. 

Actual results: original static-pod spec overrides MC change.


Expected results: MC update is authoritative and the canonical spec.


Additional info:

[1] https://github.com/openshift/machine-config-operator/pull/797

Comment 3 errata-xmlrpc 2019-10-16 06:37:16 UTC
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:2922

Comment 4 Sam Batschelet 2019-11-12 22:34:08 UTC
*** Bug 1734483 has been marked as a duplicate of this bug. ***


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