[feedhenry-dev] ASB problem ?

[David Martin]

Looks like the apb yaml that's in the LABEL could be invalid.
Seems like you spotted this already Matthias :)
https://github.com/feedhenry/fh-sync-server-apb/pull/1

I'll verify this and push to the feedhenry org

On 13 October 2017 at 21:36, David Martin <davmarti at redhat.com> wrote:

> I'm seeing this now in a fresh ec2 instance and install of mcp.
>
> [2017-10-13T20:32:06.704Z] [DEBUG] Registry::imageToSpec
> [2017-10-13T20:32:06.847Z] [ERROR] Something went wrong loading decoded
> spec yaml, YAML error: line 18: did not find expected key
> [2017-10-13T20:32:06.847Z] [ERROR] unable to retrieve spec data for image
> - YAML error: line 18: did not find expected key
> [2017-10-13T20:32:06.847Z] [ERROR] unable to fetch specs for registry dh -
> YAML error: line 18: did not find expected key
> [2017-10-13T20:32:06.847Z] [WARNING] registry: 0x14ca600 was unable to
> complete bootstrap - YAML error: line 18: did not find expected key
> [2017-10-13T20:32:06.847Z] [ERROR] Failed to bootstrap on startup!
> [2017-10-13T20:32:06.847Z] [ERROR] all registries failed on bootstrap
>
> It's configured to use the feedhenry dockerhub org.
> Is there a oddly/old format apb image in the feedhenry org?
>
> From the order of images in the logs, it looks like its failing
> on feedhenry/fh-sync-server-apb.
> Is there a way to omit images, or could we remove this image for now to
> prevent people having issues?
>
> On 13 October 2017 at 09:48, Matthias Wessendorf <mwessend at redhat.com>
> wrote:
>
>> nope - that was not the issue.
>>
>> I;ve deleted two "inprogress" repos ... from my hub accoiunt:
>> * fh-sync-server-abp
>> * kafka-apb
>>
>> Those were "inprogress", and did cause the entie ASB to fail
>>
>> We are on an older version - have to check if an "invalid" ABP really
>> crashes the entire POD on their latests ...
>>
>> Thanks for the email - I've now "unblocked" myself
>>
>> On Fri, Oct 13, 2017 at 10:42 AM, David Martin <davmarti at redhat.com>
>> wrote:
>>
>>> Is it possible the decoded spec yaml from a Docker image is invalid?
>>>
>>> e.g. the thing in this kind of label
>>> https://github.com/feedhenry/aerogear-digger-apb/blob/master
>>> /Dockerfile#L4-L24
>>>
>>> LABEL "com.blah.apb.spec"=someencodedyamlthatsactuallyinvalid
>>>
>>>
>>> On 13 October 2017 at 08:06, Matthias Wessendorf <mwessend at redhat.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> anybody seen this problem before ?
>>>>
>>>> [2017-10-13T07:01:14.351Z] [ERROR] Something went wrong loading decoded
>>>> spec yaml, YAML error: line 17: did not find expected key
>>>> [2017-10-13T07:01:14.351Z] [ERROR] unable to retrieve spec data for
>>>> image - YAML error: line 17: did not find expected key
>>>> [2017-10-13T07:01:14.351Z] [ERROR] unable to fetch specs for registry
>>>> dh - YAML error: line 17: did not find expected key
>>>> [2017-10-13T07:01:14.352Z] [WARNING] registry: 0x14ca600 was unable to
>>>> complete bootstrap - YAML error: line 17: did not find expected key
>>>> [2017-10-13T07:01:14.352Z] [ERROR] Failed to bootstrap on startup!
>>>> [2017-10-13T07:01:14.352Z] [ERROR] all registries failed on bootstrap
>>>>
>>>>
>>>> I noticed it start to occur as of yesterday... not exactly sure why/how
>>>> :-/
>>>>
>>>>
>>>> --
>>>> Project lead AeroGear.org
>>>>
>>>> _______________________________________________
>>>> feedhenry-dev mailing list
>>>> feedhenry-dev at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> David Martin
>>> Red Hat Mobile
>>> Twitter: @irldavem
>>> IRC: @irldavem (feedhenry, mobile-internal)
>>>
>>
>>
>>
>> --
>> Project lead AeroGear.org
>>
>
>
>
> --
> David Martin
> Red Hat Mobile
> Twitter: @irldavem
> IRC: @irldavem (feedhenry, mobile-internal)
>



-- 
David Martin
Red Hat Mobile
Twitter: @irldavem
IRC: @irldavem (feedhenry, mobile-internal)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-dev/attachments/20171013/2fee5c0e/attachment.htm>