Bug 1731152

Summary: Configuring the node via BOOTSTRAP_CONFIG_NAME on atomic-openshift-node does not update node-config.yaml
Product: OpenShift Container Platform Reporter: gerodrig
Component: NodeAssignee: Seth Jennings <sjenning>
Status: CLOSED NOTABUG QA Contact: Sunil Choudhary <schoudha>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, gblomqui, jokerman, mmccomas
Target Milestone: ---   
Target Release: 3.11.z   
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-07-26 08:52:27 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 gerodrig 2019-07-18 13:10:30 UTC 
Description of problem:
When configuring a node with a custom map via BOOTSTRAP_CONFIG_NAME on atomic-openshift-node the node-config.yaml does not get updated
The synching pod is not working.

How reproducible:
100% on the costumer's environment

Steps to Reproduce:
1. Follow https://access.redhat.com/solutions/4035601 to use a custom config map for a node

Actual results:
node-config.yaml is not updated with the changes on the custom configmap

Expected results:
node-config.yaml gets updated with the changes on the custom configmap

Additional info: