We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I found this issue while trying to deploy OSE v3.10 in all-in-one VM using the ng recipes from this cookbook.
My problem: the OSE v3.10 chef-run stops at execute["Wait for TSB API to become available"].
The reason:
create_template_service_broker
openshift_create_node_config
apiserver
openshift-template-service-broker
node-role.kubernetes.io/master=true
master_config_post
By manually running oc label node MASTERNODE node-role.kubernetes.io/master=true it becomes possible to continue provisioning the node.
oc label node MASTERNODE node-role.kubernetes.io/master=true
The text was updated successfully, but these errors were encountered:
@jperville I could not replicate that issue. Een with a new server everything is labelled accordingly.
Sorry, something went wrong.
IshentRas
No branches or pull requests
I found this issue while trying to deploy OSE v3.10 in all-in-one VM using the ng recipes from this cookbook.
My problem: the OSE v3.10 chef-run stops at execute["Wait for TSB API to become available"].
The reason:
create_template_service_broker
action of theopenshift_create_node_config
LWRPapiserver
daemonset in theopenshift-template-service-broker
namespacenode-role.kubernetes.io/master=true
node selectornode-role.kubernetes.io/master=true
label is set on master nodes much further in the run list, when themaster_config_post
recipe executes.By manually running
oc label node MASTERNODE node-role.kubernetes.io/master=true
it becomes possible to continue provisioning the node.The text was updated successfully, but these errors were encountered: