search

cloudfoundry / bosh-deployment-resource

Apache License 2.0
12 stars 26 forks source link

Upgrading a major stemcell while using compiled-releases fails #26

Closed utricularian closed 3 years ago

utricularian commented 7 years ago

I have a preexisting, deployed bosh deployment that uses compiled-releases against a stemcell. I want to deploy a major stemcell bump, using newer compiled-releases (which have been compiled against my new stemcell). The deploy fails claiming my release references packages without source code and are not compiled against stemcell.

A new feature was added to the Bosh2 CLI to accommodate this if compiled-releases is built correctly (CLI release, example compiled-releases).

I am using a simple put in my concourse task.

My current workarounds are to either a) delete the entire deployment and run a cleanup, b) manually upload each release binary, or c) refactor my CI to use the bosh CLI to handle deployments. Since this is just for test stuff I can delete the entire deployment, but if someone were to use this to deploy a production site they'll be stuck.

bosh-admin-bot commented 3 years ago

This issue was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.

bosh-admin-bot commented 3 years ago

This issue was closed because it has been labeled Stale for 7 days without subsequent activity. Feel free to re-open this issue at any time by commenting below.