It is a package inside of github.com/cloudfoundry/bosh-utils Here is where the binary is built: https://main.bosh-ci.cf-app.com/teams/main/pipelines/bosh-utils

Hi Ponraj, Although it is likely to be the same instance, there is no guarantee that the same instance will be always chosen as the canary. There are many reasons BOSH director would choose a differen

The Tips section of the page you linked to has instructions on how to ssh into the director vm. --Tyler wrote:

Arpit, More recent versions of the stemcell remove the vcap user's root privileges. To gain root access, you can use [cloudfoundry/os-conf-release/jobs/user_add]( https://github.com/cloudfoundry/os-co

You may want to lobby Dmitriy to add the '--no-track' feature to the v2 cli. He is the product owner and prioritizes our backlog. As a workaround, you can run `$ bosh -e my-env -d my-dep deploy my-dep

There is no --no-track option, but you can ctl-c and the task will continue. 'bosh task 123' will reattach to the output. --Tyler

A copy of the old package is kept around so that reverting to the previous version requires less downtime. This minimizes downtime in the case of a failed deploy. This is an intended feature. Currentl