Add master config hook for 3.4 upgrade and fix facts ordering #2989
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.
When the
openshift_master_facts
role runs, it reads inopenshift_master_admission_plugin_config
andopenshift_master_kube_admission_plugin_config
. A subsequent run ofopenshift_facts
merges these two dictionaries by migrating local facts.So, when the
openshift_master_facts
role was added to the control plane upgrade right before we update the master config, these two facts were getting reset and weren't merged (becauseopenshift_facts
wasn't ran afterwards). This is extremely brittle but re-ordering roles around upgrade resolves the issue. Also, amaster_config_hook
wasn't getting set for the 3.4 upgrade. This has been added.