Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1744580

Summary:	MachineConfig updates cause unexpected results for static pod manifests
Product:	OpenShift Container Platform	Reporter:	Sam Batschelet <sbatsche>
Component:	Machine Config Operator	Assignee:	Antonio Murdaca <amurdaca>
Status:	CLOSED ERRATA	QA Contact:	Micah Abbott <miabbott>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	lsm5, mnguyen
Target Milestone:	---
Target Release:	4.2.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:	2019-10-16 06:37:16 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 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. ***