Concourse fails to detect new resource version

Products

• Concourse for VMware Tanzu

Issue/Introduction

When using concourse, you may observe that a resource isn't discovering a new version of a resource. For example, you have a resource defined as follows:

- name: example-resource
  type: s3
  source:
    bucket: ((example_bucket))
    regexp: example-(.*)

And in your s3 bucket, you have two files like this:

example-1.tgz
example-2.tgz

However, concourse is only detecting the example-1.tgz

Resolution

First, ensure that concourse is pointing to the correct S3 bucket. Also ensure that the file name matches the regexp defined in your pipeline file.

If those are valid, it is likely that the resource is stored in the cache and is being pulled from there. In that case, you can run the following fly commands:

1. fly -t <target> rvs -r <pipeline>/<resource>
2. Verify that you see the old versions
3. fly -t <target> cv --resource=<pipeline>/<resource> (This will clear the versions stored by concourse)
4. fly -t <target> rvs -r <pipeline>/<resource> (To verify the old versions were removed)
5. fly -t <target> cr -r <pipeline>/<resource>

This should now pull down the newest version.