Open jperville opened 5 years ago
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
@jperville I could not replicate that issue. Een with a new server everything is labelled accordingly.
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.