Skip to content

Instantly share code, notes, and snippets.

@supertopher

supertopher/upgraaaade.md

Last active July 13, 2016 23:45
Show Gist options
  • Save supertopher/985e865b7618eb24fce2ffe75fb85aef to your computer and use it in GitHub Desktop.
Save supertopher/985e865b7618eb24fce2ffe75fb85aef to your computer and use it in GitHub Desktop.
Download ZIP
Upgrading concourse to version 1.4.0 / RunC
Raw
upgraaaade.md

Upgrading to Concourse verison 1.4.0

  • At this moment the SF cloud ops team believes that upgrading to the latest version of concourse has some external networking issues.

  • We are unsure if these issues are due to runC, 1.4.0, or some yet undiscovered problem.

  • The upgrade also failed for us while upgrading the database, and reverting back to 1.2.0 was unsuccessful. We think at this moment we are stuck on 1.4.0 unless we tear down the whole deployment

  • With that said we suggest staying away from the latest verion of concourse until we can dig into the problem a bit more over here.

I will update this document / send an email when we discover more about this issue.

Notes on the actual change in your pipelines and manifests for when you want to upgrade to 1.4.0

Relevent manifest guide from the readme

Your concourse deployment manifests will need to change the following lines

name: garden-linux
version: latest

to say

name: garden-runc
version: latest

Additionally any pipelines that are deploying this change will move stemcells to garden runc. Thus

garden-linux-*.tgz

will change to

garden-runc-*.tgz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment