# Unable to cache after migrating from stack v5.11.0 to v6.22.1 **URL:** \ **Category:** Elastic CI Stack for AWS\ **Created:** [July 15, 2024, 2:05pm UTC](https://forum.buildkite.community/t/unable-to-cache-after-migrating-from-stack-v5-11-0-to-v6-22-1/3793 "2024-07-15T14:05:37Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![gaur](https://avatars.discourse-cdn.com/v4/letter/g/d2c977/32.png) [@gaur](https://forum.buildkite.community/u/gaur)\ **Post date:** [July 15, 2024, 2:05pm UTC](https://forum.buildkite.community/t/unable-to-cache-after-migrating-from-stack-v5-11-0-to-v6-22-1/3793/1 "2024-07-15T14:05:37Z")
Hi, I am a newbie and I have been fighting a cascade of issues in our pipeline that uses Buildkite Elastic CI Stack for AWS. Our pipeline is a bit old and it uses stack version v5.11.0 and a bunch of old plugins. [An issue](https://github.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/390) with one of those plugins made me upgrade it to v6.22.1. The stack got successfully deployed using the aws CLI. So that’s great! Now I am migrating a pipeline that was running jobs on the old stack ( **unclustered** agents) to a new one (clustered). Unfortunately there are gaps in Buildkite’s documentation on how to set this up correctly, so here’s what I tried: 1. add new cluster 2. defined 2 queues, `default`, `16cores-1agent` (as named in stack parameter `BuildkiteQueue`) - I picked **self-hosted** infrastructure there 3. switch the pipeline from unclustered area to this cluster 4. try building a branch that is known to build on the old stack I get this strange error, and I don’t know where it is coming from, and why?: ![image](https://us1.discourse-cdn.com/flex016/uploads/buildkite1/original/2X/3/3022867fd49fc2fe25c86bd5ca38a252db5f864b.png) Have I configured something wrong? Does plugin `nienbo/cache-buildkite-plugin` requires some special parameter/configuration? Here’s a snippet from the pipeline upload YAML: ```yaml cache: &cache id: my_app backend: s3 key: "v1-cache-{{ id }}-{{ git.commit }}" restore-keys: - "v1-cache-{{ id }}-{{ git.commit }}" s3: bucket: my-test-bucket paths: - . steps: - label: ":buildkite: meta-data" command: .buildkite/scripts/set_version_meta_data.sh my_app - wait - label: ":cpp: build my_app" command: .buildkite/scripts/build_my_app.sh plugins: - chronotc/metadata-env#v1.0.0: keys: - my-app-release-version=MY_APP_RELEASE_VERSION - docker-login#v2.1.0: - docker#v5.3.0: image: "docker-registry.something.com/images/ubuntu-22.04:0.2.0" environment: - MY_APP_RELEASE_VERSION - nienbo/cache#v2.4.16: *cache - artifacts#v1.8.0: upload: "build/my_app/my_app-*" agents: queue: "16cores-1agent" ``` I have studied the plugin’s documentation and all logs on CloudWatch. Nothing hints as to what could be the cause. Can anyone tell me what could be the issue? ---
**Author:** ![athreya](https://avatars.discourse-cdn.com/v4/letter/a/958977/32.png) [@athreya](https://forum.buildkite.community/u/athreya)\ **Post date:** [July 15, 2024, 2:18pm UTC](https://forum.buildkite.community/t/unable-to-cache-after-migrating-from-stack-v5-11-0-to-v6-22-1/3793/2 "2024-07-15T14:18:14Z")
Hey Gaur 👋 Welcome to buildkite community: ) That’s an intresting one! Would you be able to send over the build details to [support@buildkite.com](mailto:support@buildkite.com), so we can have a look into this further?. Also, here’s a document that might help you with the migration process [Manage clusters | Buildkite Documentation](https://buildkite.com/docs/clusters/manage-clusters#move-unclustered-agents-to-a-cluster) Cheers! Athreya ---
**Author:** ![gaur](https://avatars.discourse-cdn.com/v4/letter/g/d2c977/32.png) [@gaur](https://forum.buildkite.community/u/gaur)\ **Post date:** [July 15, 2024, 7:15pm UTC](https://forum.buildkite.community/t/unable-to-cache-after-migrating-from-stack-v5-11-0-to-v6-22-1/3793/3 "2024-07-15T19:15:42Z")
Thank you, Athreya! I just now sent the build details to [support@buildkite.com](mailto:support@buildkite.com). ---
**Author:** ![athreya](https://avatars.discourse-cdn.com/v4/letter/a/958977/32.png) [@athreya](https://forum.buildkite.community/u/athreya)\ **Post date:** [July 15, 2024, 7:30pm UTC](https://forum.buildkite.community/t/unable-to-cache-after-migrating-from-stack-v5-11-0-to-v6-22-1/3793/4 "2024-07-15T19:30:03Z")
Cheers For sharing those details Gaur! We are currently looking into it and will revert back on the email with our findings : ) Regards Athreya ---
**Author:** ![paula](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/paula/32/954_2.png) [@paula](https://forum.buildkite.community/u/paula)\ **Post date:** [July 16, 2024, 1:15am UTC](https://forum.buildkite.community/t/unable-to-cache-after-migrating-from-stack-v5-11-0-to-v6-22-1/3793/5 "2024-07-16T01:15:35Z")
To round out this post with the answer we worked out via email: The problem is the stack upgrade brought with it an agent version upgrade that supports hosted agents. Hosted agents also support cache volumes. This made the YAML `cache` key reserved on the new agent version and cause the pipeline parsing failure. To fix this, simply renaming the top level key from `cache` to `cache_plugin` fixes the issue. Eg. ```diff - cache: &cache + cache_plugin: &cache id: icfse backend: s3 key: "v1-cache-{{ id }}-{{ git.commit }}" restore-keys: - "v1-cache-{{ id }}-{{ git.commit }}" s3: bucket: my-test-bucket paths: - . ``` ---
**Author:** ![gaur](https://avatars.discourse-cdn.com/v4/letter/g/d2c977/32.png) [@gaur](https://forum.buildkite.community/u/gaur)\ **Post date:** [July 16, 2024, 5:43am UTC](https://forum.buildkite.community/t/unable-to-cache-after-migrating-from-stack-v5-11-0-to-v6-22-1/3793/6 "2024-07-16T05:43:50Z")
Thank you, Jarryd and Athreya! It worked like a charm! 👍 🙂 I didn’t suspect it at all. Have a great day!