Resource doesn't show orange on pipeline view when check fails

[cjcjameson]

We observe a failed check in a docker-image-resource in the resource view, but we don't see the resource go "orange" in the pipeline view.

This may be an issue with this docker-image-resource, or could be a more general Concourse failure. I was unable to do an assessment if I could reproduce a similar error with another resource type.

[concourse-bot]

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

• [ ] #115553885 Resource doesn't show orange on pipeline view when check fails

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

[zaksoup]

I've seen this on the git resource as well. Probably not specific to docker-images-resource.

[vito]

It's when the resource only appears as an output of a job. Probably an easy fix.

[rubenv]

Just ran into this exact issue with a private registry.

Pushes work fine, but I have the feeling that checks don't use username / password correctly.

From the registry logs:

192.168.219.125 - - [31/Jul/2018:15:27:39 +0000] "GET /v2/f1bot/manifests/latest HTTP/1.1" 401 148 "" "Go-http-client/1.1"
time="2018-07-31T15:28:39Z" level=warning msg="error authorizing context: basic authentication challenge for realm \"Rocketeer Docker\": invalid authorization credential" go.version=go1.7.6 http.request.host="registry.rocketeer.be:443" http.request.id=32b147f3-0b09-46a8-95a2-31d74b02fa6c http.request.method=GET http.request.remoteaddr=94.130.52.174 http.request.uri="/v2/" http.request.useragent="Go-http-client/1.1" instance.id=892748dc-3f22-4262-a9e9-1163c6ea5b21 version=v2.6.2 
192.168.219.125 - - [31/Jul/2018:15:28:39 +0000] "GET /v2/ HTTP/1.1" 401 87 "" "Go-http-client/1.1"
time="2018-07-31T15:28:39Z" level=error msg="error authenticating user \"ruben\\n\": authentication failure" go.version=go1.7.6 http.request.host="registry.rocketeer.be:443" http.request.id=51b6839b-c78a-4543-be9f-761277c1e7d0 http.request.method=GET http.request.remoteaddr=94.130.52.174 http.request.uri="/v2/f1bot/manifests/latest" http.request.useragent="Go-http-client/1.1" instance.id=892748dc-3f22-4262-a9e9-1163c6ea5b21 vars.name=f1bot vars.reference=latest version=v2.6.2 

Is there any other way to help debug this?

[xtremerui]

Is this still happening? If yes please provide minimized steps to reproduce it. Thx!