cloudfoundry/bosh-deployment

BBR ops-file uses old stemcell

Closed this issue · 3 comments

As part of the bump to ubuntu-xenial-456 for the compiled releases it appears that the backup-and-restore-sdk release defined in the bbr.yml was not bumped as well, causing the following failure when deploying:

Can't use release 'backup-and-restore-sdk/1.15.1'. It references packages without source code and are not compiled against stemcell 'bosh-google-kvm-ubuntu-xenial-go_agent/456.1':
 - 'azure-blobstore-backup-restorer/38048238704527ce36165164010a61667e32124d'
 - 'database-backup-restorer/3693f965b546b9e6fca622fb1166f504cfce3fdb'
 - 'database-backup-restorer-boost/c3aee061423c7de8e1bbe50db88f82379c54edf3'
 - 'database-backup-restorer-mariadb/fb964c7d07a5cc5b0487d9f94c01d777c169e17f'
 - 'database-backup-restorer-mysql-5.5/949e6844e3a0da60c20ea9fb4f5fb2181fd2e3ad'
 - 'database-backup-restorer-mysql-5.6/361ffd33a416f92bfc06aa6f5f59d966a6aaa370'
 - 'database-backup-restorer-mysql-5.7/ac5d90d4308139c1b4c4b4d93a3ccb89ef291d00'
 - 'database-backup-restorer-postgres-10/d7f19747af1c25c7896c6cd678bdd0d11230f61a'
 - 'database-backup-restorer-postgres-11/dafb0f69cae5f2cdc6d77cbefb7f783028bd45a5'
 - 'database-backup-restorer-postgres-9.4/a67d1cd0da02f6092142ba75cb06a204768e698c'
 - 'database-backup-restorer-postgres-9.6/c29df70e36862c03bfb9e5a27b360b452e95d473'
 - 'gcs-blobstore-backup-restorer/4ad6a700839d007849d30c31bf717246d8f82681'
 - 'golang-1-linux/0fb4dcd069c8e997914e544ce1b76f6643b54e806669bec264cb7a9b4c7bfee4'
 - 's3-blobstore-backup-restorer/6e8aa067cd878eb944066be534b3e5803811ebe9'

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/167426027

The labels on this github issue will be updated when the story is started.

Hey @aclevername ,

It seems that the error you're seeing was a mismatch between the package's version and the deployed stemcell version, we had a few issues bumping some release versions. We've properly recompiled all of the releases against the new stemcell line now, and this issue should no longer appear.

Thanks!

Thanks for the quick turnaround @belinda-liu!