For what it's worth it seems my build of docker was missing these fixes:

https://bugzilla.redhat.com/show_bug.cgi?id=1298363
https://bugzilla.redhat.com/show_bug.cgi?id=1302418

I'm going to do more upgrade testing today with the build that
includes that fix.  I think the copr already has these fixes.

On Wed, Mar 9, 2016 at 8:52 AM, Brenton Leanhardt <blean...@redhat.com> wrote:
> Yesterday on a system where I upgraded from Docker 1.8 to 1.9 I
> started hitting this problem with a previously working etcd container:
>
> https://github.com/docker/docker/issues/17691
>
> The only error I received when trying to run the container was "Could
> not find container for entity id <some long hash>".
>
> I feel like I've hit this twice.  The first time I thought it was
> self-inflicted so I didn't investigate more.
>
> On Wed, Mar 9, 2016 at 7:50 AM, Skarbek, John <john.skar...@ca.com> wrote:
>> Andy,
>>
>> In my case I’m running CentOS7 latest.
>>
>>
>>
>> --
>> John Skarbek
>>
>> On March 9, 2016 at 07:45:59, Andy Goldstein (agold...@redhat.com) wrote:
>>
>> What OS - Fedora/Centos/RHEL?
>>
>> Jhon/Dan, PTAL as this might be related to forward-journald.
>>
>> Andy
>>
>> On Wed, Mar 9, 2016 at 7:44 AM, Skarbek, John <john.skar...@ca.com> wrote:
>>>
>>> Andy,
>>>
>>> David had already file an issue
>>>
>>> Mar 09 12:40:07 js-router-001.ose.bld.f4tech.com systemd[1]: Starting
>>> Docker Application Container Engine...
>>> Mar 09 12:40:07 js-router-001.ose.bld.f4tech.com forward-journal[18500]:
>>> Forwarding stdin to journald using Priority Informational and tag docker
>>> Mar 09 12:40:08 js-router-001.ose.bld.f4tech.com forward-journal[18500]:
>>> time="2016-03-09T12:40:08.104822274Z" level=info msg="Firewalld running:
>>> false"
>>> Mar 09 12:40:08 js-router-001.ose.bld.f4tech.com forward-journal[18500]:
>>> time="2016-03-09T12:40:08.136388972Z" level=info msg="Default bridge
>>> (docker0) is assigned with an IP address 172.17.0.1/16. Daemon option --bip
>>> can be used to set a preferred IP address"
>>> Mar 09 12:40:08 js-router-001.ose.bld.f4tech.com forward-journal[18500]:
>>> time="2016-03-09T12:40:08.183636904Z" level=info msg="Loading containers:
>>> start."
>>> Mar 09 12:40:08 js-router-001.ose.bld.f4tech.com forward-journal[18500]:
>>> Mar 09 12:40:08 js-router-001.ose.bld.f4tech.com forward-journal[18500]:
>>> time="2016-03-09T12:40:08.183842066Z" level=info msg="Loading containers:
>>> done."
>>> Mar 09 12:40:08 js-router-001.ose.bld.f4tech.com forward-journal[18500]:
>>> time="2016-03-09T12:40:08.184069850Z" level=info msg="Daemon has completed
>>> initialization"
>>> Mar 09 12:40:08 js-router-001.ose.bld.f4tech.com forward-journal[18500]:
>>> time="2016-03-09T12:40:08.184116853Z" level=info msg="Docker daemon"
>>> commit="185277d/1.9.1" execdriver=native-0.2 graphdriver=devicemapper
>>> version=1.9.1
>>> Mar 09 12:40:08 js-router-001.ose.bld.f4tech.com forward-journal[18500]:
>>> time="2016-03-09T12:40:08.193532957Z" level=info msg="API listen on
>>> /var/run/docker.sock"
>>> Mar 09 12:40:08 js-router-001.ose.bld.f4tech.com systemd[1]:
>>> docker.service: Got notification message from PID 18499, but reception only
>>> permitted for main PID 18498
>>>
>>>
>>>
>>>
>>> --
>>> John Skarbek
>>>
>>> On March 9, 2016 at 07:41:03, Andy Goldstein (agold...@redhat.com) wrote:
>>>
>>> What is the output of 'sudo journalctl -u docker -e'?
>>>
>>> On Wed, Mar 9, 2016 at 3:38 AM, David Strejc <david.str...@gmail.com>
>>> wrote:
>>>>
>>>> I don't know where I could find right person for this issue so I am
>>>> trying to post it here as many people are reading this.
>>>>
>>>> Clean installation of Open Shift v3 via ansible is broken by simple yum
>>>> update as yum updates Docker from 1.8 to 1.9.1 and Docker is not starting
>>>> anymore.
>>>>
>>>> This is the message in logs:
>>>>
>>>> Mar 09 09:03:45 1.devcloud.cz systemd[1]: docker.service: Got
>>>> notification message from PID 7150, but reception only permitted for main
>>>> PID 7149
>>>>
>>>>
>>>> David Strejc
>>>> t: +420734270131
>>>> e: david.str...@gmail.com
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> users@lists.openshift.redhat.com
>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>>
>>>
>>> _______________________________________________
>>> users mailing list
>>> users@lists.openshift.redhat.com
>>>
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openshift.redhat.com_openshiftmm_listinfo_users&d=CwICAg&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=2_kN02gJlhscVfvV2RC2IaT4PbU3aXbeIvn7SmOh60k&s=VtI_OicOZR1K3k47Lnidb-zMLVVNJIPEnadtVHfyXN0&e=
>>
>>
>>
>> _______________________________________________
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>

_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to