Re: TSB fails to start

2018-03-20 Thread Tim Dudgeon
I'm just using the default SDN. This seems to be some issue with Origin 3.7.  Switching back to 3.6.1 works fine. I'm struggling to work out what is going on as it is not very reproducible (and 3.7 is broken at present). Tim On 20/03/18 08:10, Joel Pearson wrote: Are you using calico or

Re: TSB fails to start

2018-03-20 Thread Joel Pearson
Are you using calico or something like that? If so why not consider a regular overlay network just to get it working? On Thu, 15 Mar 2018 at 5:26 am, Tim Dudgeon wrote: > A little more on this. > One the nodes that are not working the file >

Re: TSB fails to start

2018-03-14 Thread Tim Dudgeon
A little more on this. One the nodes that are not working the file /etc/cni/net.d/80-openshift-network.conf is not present. This seems to cause errors like this in the origin-node service: Mar 14 18:21:45 zzz-infra.openstacklocal origin-node[17833]: W0314 18:21:45.711715   17833 cni.go:189]

Re: TSB fails to start

2018-03-01 Thread Tim Dudgeon
Thanks for the suggestions, but I don't think its either of these. 1. an infra region is defined 2. I tried specifically setting the openshift_template_service_broker_namespaces property as you suggested but it makes no difference. In fact I believe that if it is not set it defaults to using

Re: TSB fails to start

2018-03-01 Thread Tim Dudgeon
Yes, I think it is related to DNS. On a similar, but working, OpenStack environment ` netstat -tunlp | grep ...` shows this: tcp    0  0 127.0.0.1:53 0.0.0.0:*   LISTEN  16957/openshift tcp    0  0 10.128.0.1:53 0.0.0.0:*   LISTEN 

Re: TSB fails to start

2018-02-28 Thread Gaurav Ojha
Hi, I had a similar issue when setting up OpenShift through the playbooks. What solved it for me was realizing that I had not defined my node with region infra which is required for the router and registry to run (link here