concourse: 4.0.0 some resources silently fail to produce input artifacts

Bug Report

I started seeing this with the github release resource, and opened https://github.com/concourse/github-release-resource/issues/75

However, I’ve now reproduced this with multiple resources. Most recently, a git resource.

Basically, a resource succeeds on a ‘check’, and shows a valid version, and the input directory gets created during the pipeline job, however it’s empty!

Somehow concourse seems to think it’s correctly downloading or downloaded or cached the resource, but whenever it runs there’s nothing in the directory.

fly check-resource does not fix it, neither does pausing and unpausing the resource, or marking the versions as unavailable - triggering a build without valid versions available, and then enabling the versions again…

The only thing I’ve found to fix it is destroying and re-creating the pipeline so the resources are completely re-created.

This is happening on a local dev stack install, where sometimes I ‘stop’ the cluster (e.g. stop the darwin worker and all the docker containers, leaving all volumes intact) and then start it back up later. When I do this, the pipelines all come back, etc, but occasionally this strange resource bug happens.

  • Concourse version: 4.0.0
  • Deployment type (BOSH/Docker/binary): Docker (web / db / linux worker) Darwin (worker)
  • Infrastructure/IaaS:
  • Browser (if applicable): Chrome
  • Did this used to work?: Yes?

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 23 (2 by maintainers)

Most upvoted comments

@vito Sorry Vito, long weekend of frustrating headbanging. Apologies.