DO NOT MERGE Consistently downcase the masterKubeConfig path #299
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a short fix for a bug I encountered when trying to provision a node whose fqdn contains uppercase letters (eg.
MY-OSE-SERVER.example.com
).The symptoms
The chef run failed with a broken origin-node service.
The interesting snippet was in the origin-node service logs :
The investigation
Apparently, the cookbook downcases the path of the master kube config path when it creates it on the disk, but it does not downcase the path when referencing that file in /etc/origin/node/node-config.yaml.
The fix
The fix is just to downcase the masterKubeConfig entry in the template that is rendered into /etc/origin/node/node-config.yaml
Before this PR:
After this PR: