[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: "manifest unknown" test flakes



Graham's issue appears to be similar.

On Wed, Jun 8, 2016 at 9:43 AM, Clayton Coleman <ccoleman redhat com> wrote:
> There is a flake issue open in origin
>
> On Jun 8, 2016, at 9:42 AM, Steve Kuznetsov <skuznets redhat com> wrote:
>
> Do we have an issue or BZ open  to track this?
>
> On Wed, Jun 8, 2016 at 9:34 AM, Luke Meyer <lmeyer redhat com> wrote:
>>
>> It's not a flake for me, it's happening every time. I just fired up a
>> Centos 7 devenv AMI and it had docker 1.9. And FWIW it doesn't look like
>> Fedora 23 has shipped 1.10 yet either.
>>
>> On Tue, Jun 7, 2016 at 11:07 PM, Clayton Coleman <ccoleman redhat com>
>> wrote:
>>>
>>> Yes, but you do not need v2 metadata.
>>>
>>> I just saw this flake again on a PR.  We need to dig into this but it
>>> seems to be happening more on 1.10.
>>>
>>> On Jun 7, 2016, at 10:54 PM, Steve Kuznetsov <skuznets redhat com> wrote:
>>>
>>> The image needs to be pushed with a Docker client 1.10+ to generate the
>>> V2 metadata if I understand it correctly.
>>>
>>> Steve
>>>
>>> On Jun 7, 2016 10:27 PM, "Ben Parees" <bparees redhat com> wrote:
>>>>
>>>>
>>>>
>>>> On Tue, Jun 7, 2016 at 9:48 PM, Clayton Coleman <ccoleman redhat com>
>>>> wrote:
>>>>>
>>>>> We are building and pushing our images with Docker 1.10 for Origin (but
>>>>> possibly not in all AMIs, depending on the test job).  The last set of
>>>>> pushed images (alpha.1) was pushed from Docker 1.9.
>>>>>
>>>>> This might just be docker flaking, but we'd probably need more info
>>>>> from the Docker logs.
>>>>
>>>>
>>>> is the issue here that that ruby-22-centos7 image itself needs to be
>>>> rebuild/pushed from docker 1.10?
>>>>
>>>> if so (and if our AMIs are on docker 1.10) i can kick off a fresh round
>>>> of our s2i image build/push job to refresh everything.
>>>>
>>>>
>>>>>
>>>>>
>>>>> On Tue, Jun 7, 2016 at 9:41 PM, Luke Meyer <lmeyer redhat com> wrote:
>>>>>>
>>>>>> I've seen this twice in logging tests, in the ruby STI builder today
>>>>>> and in the origin image last week, so I'm wondering if it's a trend.
>>>>>>
>>>>>>
>>>>>> https://ci.openshift.redhat.com/jenkins/job/test-origin-aggregated-logging/381/artifact/origin/artifacts/logs/container-ruby-sample-build-1-build-sti-build.log
>>>>>>
>>>>>> Pulling Docker image
>>>>>> centos/ruby-22-centos7 sha256:e5ebb014d02b5a7faa7b83f6c58f4cc4eb9892edbf61172e59f2ae1999982dc2
>>>>>> ...
>>>>>> I0608 01:08:34.707737       1 glog.go:50] An error was received from
>>>>>> the PullImage call: manifest unknown: manifest unknown
>>>>>>
>>>>>> The closest thing I could find under issues is
>>>>>> https://github.com/openshift/origin/issues/9122 where it was reportedly due
>>>>>> to the image being pushed by docker 1.10.
>>>>>>
>>>>>> Is someone pushing our images to dockerhub with docker 1.10?
>>>>>>
>>>>>> Builds run on CentOS7, don't think that AMI has docker 1.10 yet.
>>>>>>
>>>>>> _______________________________________________
>>>>>> dev mailing list
>>>>>> dev lists openshift redhat com
>>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> dev mailing list
>>>>> dev lists openshift redhat com
>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Ben Parees | OpenShift
>>>>
>>>>
>>>> _______________________________________________
>>>> dev mailing list
>>>> dev lists openshift redhat com
>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>>
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev lists openshift redhat com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>
>>
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]