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 fix overlay mounts for CoreOS in Openshift 4.6.
Currently with this fix nodes are created and joined into cluster which enables installation of Openshift with Contrail.
However, installation cannot report complete status as there's a problem in machineconfigpool resource for master.
Openshift by deault consumes all machineconfigs for both master and worker nodes and then create another machine config resource which is a rendered ignition config for CoreOS used in final node boot.
MachineConfigPool resources lookup for these rendered configs and then use some internal logic to define whether created node is properly configured.
However, currently machineconfigpool for master nodes report that nodes are not configured properly as it cannot find rendered machineconfig for master nodes. It is so, because it tries to lookup rendered config with uuid number which is not the same as uuid of actually rendered machineconfig.
It may be debugged by exporting kubeconfig and running
kubectl get machineconfig -A
.This command outputs all machineconfigs in the cluster and at the end there are machine configs called
master-rendered-<uuid>
which is rendered master config for nodes.Looking into another command
kubectl get machineconfigpool -A
you may notice that machineconfigpool master has not ready state which is the reason why installation is not completed due to install binary, but the cluster works.