Bug 1731152 - Configuring the node via BOOTSTRAP_CONFIG_NAME on atomic-openshift-node does not update node-config.yaml
Summary: Configuring the node via BOOTSTRAP_CONFIG_NAME on atomic-openshift-node does ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.11.z
Assignee: Seth Jennings
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-18 13:10 UTC by gerodrig
Modified: 2019-07-26 08:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-26 08:52:27 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Article) 4035601 None None None 2019-07-18 13:26:58 UTC

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:


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