Bug 1321622

Summary: [RFE] [Supportability] Should receive error/warning when adding misspelled or incorrect section to configuration files
Product: OpenShift Container Platform Reporter: Eric Jones <erjones>
Component: RFEAssignee: Michal Fojtik <mfojtik>
Status: CLOSED DEFERRED QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.0CC: aos-bugs, dma, ekuric, erjones, jokerman, mbarrett, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
OpenShift Enterprise 3.1
Last Closed: 2018-03-12 13:54:36 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:

Description Eric Jones 2016-03-28 16:24:08 UTC
- What is the nature and description of the request?  
As an admin I should get an error, or at least receive a warning message, when something in my configuration file does not match any known section.

- Why does the customer need this? (List the business requirements here)  
If a customer mistypes a section (`kubletArguments` vs `kubeletArguments`) nothing currently changes and the system uses the default settings, despite the fact that they are trying to make changes.

- How would the customer like to achieve this? (List the functional requirements here)  
Either receive an error message and have the service fail when restarted or at least receive a warning message in the logs suggesting that the system will continue to use the default settings as it does not recognize <INSERT_INCORRECT_SECTION_HERE>

- Is there already an existing RFE upstream or in Red Hat Bugzilla?  
Not that I could find  

- List any affected packages or components.  
OpenShift
atomic-openshift-node service
Kubernetes

Comment 2 Dan McPherson 2016-06-02 10:58:54 UTC
*** Bug 1339921 has been marked as a duplicate of this bug. ***

Comment 3 Dan McPherson 2017-02-22 15:02:30 UTC
*** Bug 1425839 has been marked as a duplicate of this bug. ***

Comment 4 Dan McPherson 2017-02-22 15:06:04 UTC
From: https://bugzilla.redhat.com/show_bug.cgi?id=1425839

An additional part of this request should be to output the settings being used (-secrets) so someone could diff changes from start to start.

Comment 7 Eric Rich 2018-03-12 13:54:36 UTC
This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.