Skip to content
New issue

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

Broken Template Service Broker Deployment with all-in-one VM #289

Open
jperville opened this issue Dec 19, 2018 · 1 comment
Open

Broken Template Service Broker Deployment with all-in-one VM #289

jperville opened this issue Dec 19, 2018 · 1 comment
Assignees
Labels

Comments

@jperville
Copy link
Collaborator

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:

  • the ng_master.rb recipe invoked the create_template_service_broker action of the openshift_create_node_config LWRP
  • that action instantiates a apiserver daemonset in the openshift-template-service-broker namespace
  • then polls the apiserver service using curl until the apiserver is ready
  • the apiserver does not become ready on time, because its daemonset pod template has a node-role.kubernetes.io/master=true node selector
  • this label node-role.kubernetes.io/master=true label is set on master nodes much further in the run list, when the master_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.

@IshentRas
Copy link
Owner

@jperville I could not replicate that issue. Een with a new server everything is labelled accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants