docker registry backed with glusterfs gives Internal Server Error during builds on 3.7.14

Hi All, Previously, I had a permission denied problem when I changed the registry from NFS to glusterfs MANUALLY AFTER an ansible installation following the documentation. But then I had to reinstall for other reasons, and this time around I specified the gluster volume to use in the inventory

Re: Pods stuck on Terminating status

Hi Rodrigo, Restarting master services did not help either.. I tried afterwards again with grace period and force delete. Stil no luck. Bahho On 16 March 2018 at 21:29, Rodrigo Bersa wrote: > Bahhoo, > > I believe that the namespace will get stuck also. 'Cause it will

Re: origin-clients v3.7.1-1 provides binary for v3.10.0-aplha.0

And of course openshift ansible experiments the same issue : https://github.com/openshift/openshift-ansible/issues/7567 On Mon, Mar 19, 2018 at 4:37 PM, Jean-Francois Chevrette < jchev...@redhat.com> wrote: > Hi, > > it appears the origin-clients v3.7.1-1 as provided in the centos paas > repos

origin-clients v3.7.1-1 provides binary for v3.10.0-aplha.0

Hi, it appears the origin-clients v3.7.1-1 as provided in the centos paas repos [1] is actually providing binaries for v3.10.0-aplha.0 I have opened this bug: https://bugs.centos.org/view.php?id=14594 It was also reported in openshift/origin a few days ago: https://github.com/