Description of problem: If there is typo or misspelled configuration value in configuration files - restarting of service will not fail - even there is parameter in configuration file which is obviously wrong Version-Release number of selected component (if applicable): my test was with below packages atomic-openshift-clients-3.2.0.44-1.git.0.a4463d9.el7.x86_64 atomic-openshift-master-3.2.0.44-1.git.0.a4463d9.el7.x86_64 tuned-profiles-atomic-openshift-node-3.2.0.44-1.git.0.a4463d9.el7.x86_64 atomic-openshift-node-3.2.0.44-1.git.0.a4463d9.el7.x86_64 atomic-openshift-sdn-ovs-3.2.0.44-1.git.0.a4463d9.el7.x86_64 atomic-openshift-3.2.0.44-1.git.0.a4463d9.el7.x86_64 How reproducible: Here is example of my test - configure metrics following https://github.com/openshift/origin-metrics - misspell metricsPublicURL and write it as metricsPublicUrl - restart openshift master service - which will be successful - it is expected to see metrics tab in openshift interface - but it will not be there due to wrong parameter name in master configuration file Steps to Reproduce: see above Actual results: - systemctl restart atomic-openshift-master will work without error - thought there is wrong parameter in configuration file - metrics tab will not be visible in openshift web interface Expected results: systemctl restart atomic-openshift-master to fail ( and eventually point out where bad line is ) Additional info: none
I am reassigning this as its not an issue with the metrics components but rather an issue with how OpenShift is started.
*** This bug has been marked as a duplicate of bug 1321622 ***