https://github.com/openshift/openshift-ansible/issues/2648
On Mon, Oct 24, 2016 at 8:57 AM, Philippe Lafoucrière
wrote:
> For the record, I'm pretty sure that's the issue blocking us from upgrading
> to 1.3.X (the symptoms are exactly the same + this issue
> https://github.com/openshift/origin/is
For the record, I'm pretty sure that's the issue blocking us from upgrading
to 1.3.X (the symptoms are exactly the same + this issue
https://github.com/openshift/origin/issues/11164).
We're using ansible to upgrade, and this change is part of it (yes, we
should run ansible more often).
___
Adding Scott.
On Sun, Oct 23, 2016 at 9:00 AM, Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com> wrote:
> Looks like the problem comes from https://github.com/
> openshift/openshift-ansible/pull/2411/files
> Where the registry is considered as secure, but it still listen using http
> o
Looks like the problem comes from
https://github.com/openshift/openshift-ansible/pull/2411/files
Where the registry is considered as secure, but it still listen using http
only.
This folder shouldn't be empty if I understand correctly:
-bash-4.2# ls -l /etc/docker/certs.d/
total 0
It's definitely ansible :(
We have updated by hand all nodes, and after an ansible run, the wrong
config is back
We'll investigate from here
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/us
Ok found it.
The docker config has been altered on all nodes:
grep OPTIONS /etc/sysconfig/docker
OPTIONS=' --selinux-enabled --log-driver=json-file --log-opt max-size=50m'
Where it should be
OPTIONS=' --selinux-enabled --insecure-registry=172.30.0.0/16
--log-driver=json-file --log-opt max-size
Hi,
We have updated the OS of our nodes last night, nothing fancy, and since,
all projects with built images are failing. This is absolutely scary:
- The site are unavailable, the pod are failing with "Image pull back off"
- We can't deploy anymore
- We can't rollback anymore
- We can't build any
