Re: LDAP bindPassword in Ansible inventory

2017-10-23 Thread Lionel Orellana
Well adding this to the inventory file doesn't work (even if the files are copied to masters before hand). 'bindPassword': {'file': '/root/bindPassword.encrypted', 'keyFile': '/root/bindPassword.key'}, Is there any way to encrypt the bindPassword in the inventory file? On 21 October 2017 at

Re: Origin router and X-Forwarded-For

2017-10-23 Thread Aleksandar Lazic
Hi Marcello. on Mittwoch, 18. Oktober 2017 at 10:32 was written: > Hi Aleks, > I already configured the 4 values and if I miss the intermediate CA > into the destinationCACertificate field the Origin GUI shows to me a > warning related to the certificate. The export of the command is : Are

Re: Network issues with openvswitch

2017-10-23 Thread Aleksandar Lazic
Title: Re: Network issues with openvswitch Hi Yu Wei. Ah that's a good point. Do you have seen this doc? https://access.redhat.com/documentation/en-us/reference_architectures/2017/html/deploying_red_hat_openshift_container_platform_3.4_on_red_hat_openstack_platform_10/ Regards Aleks on

Re: Network issues with openvswitch

2017-10-23 Thread Yu Wei
My environment is setting up on VMs provided by openstack. It seemed that nodes not working were created from resource pool in which openstack has different version of ovs. As I have destroyed the environment and want to try again. I couldn't get more information now. Thanks, Jared, (韦煜）

Re: Network issues with openvswitch

2017-10-23 Thread Aleksandar Lazic
Title: Re: Network issues with openvswitch Hi Yu Wei. Interesting issue. What's the difference between the nodes which the connection work and the one from which the connection does not work? Please can you share some more Informations. I assume this is on aws, is the UDP port 4789 open from

Simulating hanging docker daemon

2017-10-23 Thread bahhooo
Hi everyone, We have recently the issue that the docker daemons are hanging on different nodes. Is there a way of causing docker daemon to hang manually so that we can examine its behavior and build accordingly a monitoring solution? Best Bahhoo ___

Re: DNS resolving problem - in pod

2017-10-23 Thread Łukasz Strzelec
Hello :) So, the problem seems to be in node :( I tested in pod with dns-utils on board I was not able to resolved svc name. I've performed the same tests directly on node where affected pod is running, and just like I thought , I'm not able to resolved the svc names either - connection time

Re: DNS resolving problem - in pod

2017-10-23 Thread Marko Lukša
Everything looks fine (except for the double nameserver entry, but that shouldn't cause any problems). Try running the following: oc run dnstest -it --restart Never --rm --image tutum/dnsutils bash And then try looking up your service through the container's default nameserver: dig

Re: No route to host when trying to connect to services

2017-10-23 Thread Łukasz Strzelec
Hello mate;) Did you solve this issue? I have pretty much the same problem. I noticed that when I restart origin-node.service it helps. But the problem is occuring frequently. Sometimes to solve it I have to restart whole docker engine. I've try to debug this issue, nothing found. The common

Re: DNS resolving problem - in pod

2017-10-23 Thread Łukasz Strzelec
Ok, let's see: I've checked the /etc/resolv.conf in pod: [image: Obraz w treści 2] the 10.111.208.195 is the node ip -on which the dnsmasq was started. What is strange the pod is obtaining duplicated entries. On node, the /etc/resolv.conf has entries: [image: Obraz w treści 3] The origin