On 07/18/2016 07:07 PM, Philippe Lafoucrière wrote:
> We're using postgres 9.5.
> It was working fine before the upgrade. Unfortunately, we upgraded
> atomic AND Openshift at the same time, so I can't tell if it's a problem
> with docker 1.10 or openshift 1.2.1.
> I'd tend to say Docker 1.10, but w
We're using postgres 9.5.
It was working fine before the upgrade. Unfortunately, we upgraded atomic
AND Openshift at the same time, so I can't tell if it's a problem with
docker 1.10 or openshift 1.2.1.
I'd tend to say Docker 1.10, but we need to isolate this first.
Thanks,
Philippe
Sorry, wrong thread, disregard my reply.
On Mon, Jul 18, 2016 at 12:59 PM, Scott Dodson wrote:
> We've worked around this change by checking for those booleans and
> setting each if they exist.
> https://github.com/openshift/openshift-ansible/pull/2166
>
> On Mon, Jul 18, 2016 at 12:56 PM, Josh B
On 07/18/2016 09:59 AM, Scott Dodson wrote:
> We've worked around this change by checking for those booleans and
> setting each if they exist.
> https://github.com/openshift/openshift-ansible/pull/2166
What version of Postgres is in this container?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
We've worked around this change by checking for those booleans and
setting each if they exist.
https://github.com/openshift/openshift-ansible/pull/2166
On Mon, Jul 18, 2016 at 12:56 PM, Josh Berkus wrote:
> On 07/15/2016 08:59 AM, Philippe Lafoucrière wrote:
>> We're having a potential issue. One
On 07/15/2016 08:59 AM, Philippe Lafoucrière wrote:
> We're having a potential issue. One postgresql service is not starting
> on the beta cluster:
>
> FATAL: could not open shared memory segment "/PostgreSQL.1804289383":
> Permission denied
>
> We need to investigate that, but it could be rela
On Mon, Jul 11, 2016, at 09:56 AM, Scott Dodson wrote:
> That commit is mostly related to the fact that we cannot
> upgrade/downgrade docker on atomic host like can on RHEL so abort the
> docker upgrade playbook early.
For short term fixes, it is however possible to use `atomic host deploy` to
re
https://docs.openshift.org/latest/dev_guide/shared_memory.html
fixed the issue, but It seems something changed regarding /dev or shm
docker mounts between 1.2.0 and 1.2.1.
Can someone confirm?
___
users mailing list
users@lists.openshift.redhat.com
htt
We're having a potential issue. One postgresql service is not starting on
the beta cluster:
FATAL: could not open shared memory segment "/PostgreSQL.1804289383":
Permission denied
We need to investigate that, but it could be related to docker mounts
(especially /dev/shm)
___
I confirm: it's fixed :)
thanks!
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
We pulled that into v1.2.1 along with the security update. Can you
give that a try?
On Thu, Jul 14, 2016 at 11:11 AM, Philippe Lafoucrière
wrote:
>
> On Tue, Jul 12, 2016 at 5:22 PM, Scott Dodson wrote:
>>
>> I'll see if I can get openshift/node:v1.2.0 rebuilt with this fix but
>> you can also r
On Tue, Jul 12, 2016 at 5:22 PM, Scott Dodson wrote:
> I'll see if I can get openshift/node:v1.2.0 rebuilt with this fix but
> you can also rebuild the node image placing the docker wrapper script
> in /usr/local/bin
>
Any news on this?
Thanks
___
user
Testing it right away.
Thanks guys :)
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
https://github.com/openshift/origin/pull/9046 is the real fix for this.
I'll see if I can get openshift/node:v1.2.0 rebuilt with this fix but
you can also rebuild the node image placing the docker wrapper script
in /usr/local/bin
On Tue, Jul 12, 2016 at 4:36 PM, Philippe Lafoucrière
wrote:
> Goo
Good catch Scott:
[plafoucriere@atomic-test-node-1 origin]# docker info
/usr/bin/docker-current: error while loading shared libraries:
libseccomp.so.2: cannot open shared object file: No such file or directory
___
users mailing list
users@lists.opensh
Maybe this is another bug? Can you exec into your node container and
try to run `docker info` and see what errors it yields?
On Tue, Jul 12, 2016 at 2:13 PM, Philippe Lafoucrière
wrote:
>
> On Tue, Jul 12, 2016 at 10:27 AM, Scott Dodson wrote:
>>
>> Lets say openshift-ansible for now.
>
>
> ok t
On Tue, Jul 12, 2016 at 10:27 AM, Scott Dodson wrote:
> Lets say openshift-ansible for now.
>
ok thanks
> I suspect that adding `-v /etc/sysconfig/docker:/etc/sysconfig/docker`
> to ExecStart in /etc/systemd/system/origin-node.service will fix this,
> also verify that you've got `-v
> /usr/bin
Lets say openshift-ansible for now.
I suspect that adding `-v /etc/sysconfig/docker:/etc/sysconfig/docker`
to ExecStart in /etc/systemd/system/origin-node.service will fix this,
also verify that you've got `-v
/usr/bin/docker-current:/usr/bin/docker-current` too but the current
installer should ta
On Mon, Jul 11, 2016 at 9:56 AM, Scott Dodson wrote:
> That commit is mostly related to the fact that we cannot
> upgrade/downgrade docker on atomic host like can on RHEL so abort the
> docker upgrade playbook early.
>
Ok, I get it now, thanks.
Anyway, we couldn't fix our beta cluster, and had
That commit is mostly related to the fact that we cannot
upgrade/downgrade docker on atomic host like can on RHEL so abort the
docker upgrade playbook early.
On Sun, Jul 10, 2016 at 2:45 PM, Philippe Lafoucrière
wrote:
> Sounds like docker 1.10 is a bad idea, I found this commit:
>
> https://gith
Sounds like docker 1.10 is a bad idea, I found this commit:
https://github.com/openshift/openshift-ansible/commit/b377f9d85df11c532281c213eda1869596642204
I was probably running openshift-ansible with a wrong tag :(
___
users mailing list
users@lists.
We have updated our beta cluster to latest atomic centos:
-bash-4.2# atomic host status
TIMESTAMP (UTC) VERSIONID OSNAME
REFSPEC
* 2016-07-07 21:23:41 7.20160707 cd47a72eb5 centos-atomic-host
centos-atomic-host:centos-atomic-host/7/x86_64/standard
Thanks Tobias for the detailed help!
I should have thought of running again ansible, I was focused on the error.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Hi,
that's a known problem with known fix, but maybe some publicity around
it might be good.
> We have tried to update our atomic host centos 7, with the
> tree 3c3786d1dd (from the tree e39c28570a), but deployments are all
> failing after the updates on the nodes:
>
> Error syncing pod, skippi
Hi,
We have tried to update our atomic host centos 7, with the tree 3c3786d1dd
(from the tree e39c28570a), but deployments are all failing after the
updates on the nodes:
Error syncing pod, skipping: failed to "SetupNetwork" for "some_deploy"
with SetupNetworkError: "Failed to setup network for p
25 matches
Mail list logo
