I've been updating our bosh installations to release 219 with vsphere stemcell 3115. When complete, bosh status shows it as version 3122. Usually the bosh status is the same as the stemcell used when updating. I've not noticed this mismatch before. Any idea why its different?

bosh status unfortunetly doesnt show bosh release version (we will be
fixing that soon). it does show build number for the bosh release. when
bosh micro deploy was used build number would always be the same as
stemcell that director is deployed on (because bosh release was not
provided separately). with bosh-init director release is shipped separately
from the stemcell hence those numbers may not match.

On Thu, Dec 10, 2015 at 4:28 PM, William C Penrod <wcpenrod(a)gmail.com>
wrote:

I've been updating our bosh installations to release 219 with vsphere
stemcell 3115. When complete, bosh status shows it as version 3122. Usually
the bosh status is the same as the stemcell used when updating. I've not
noticed this mismatch before. Any idea why its different?

That makes sense. In the past I've used the build number of the bosh
release to select the stemcell to deploy it on. What's the recommended way
to determine the stemcell that was used to test and deploy the bosh release?

On Thu, Dec 10, 2015 at 5:58 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

bosh status unfortunetly doesnt show bosh release version (we will be
fixing that soon). it does show build number for the bosh release. when
bosh micro deploy was used build number would always be the same as
stemcell that director is deployed on (because bosh release was not
provided separately). with bosh-init director release is shipped separately
from the stemcell hence those numbers may not match.

On Thu, Dec 10, 2015 at 4:28 PM, William C Penrod <wcpenrod(a)gmail.com>
wrote:

I've been updating our bosh installations to release 219 with vsphere
stemcell 3115. When complete, bosh status shows it as version 3122. Usually
the bosh status is the same as the stemcell used when updating. I've not
noticed this mismatch before. Any idea why its different?

I try to include recommended stemcell version in release notes (e.g.
http://bosh.io/releases/github.com/cloudfoundry/bosh?version=235). In
practice it's a very soft recommendation so you can use any recent stemcell
version.

On Thu, Dec 10, 2015 at 6:25 PM, William C Penrod <wcpenrod(a)gmail.com>
wrote:

That makes sense. In the past I've used the build number of the bosh
release to select the stemcell to deploy it on. What's the recommended way
to determine the stemcell that was used to test and deploy the bosh release?

On Thu, Dec 10, 2015 at 5:58 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

bosh status unfortunetly doesnt show bosh release version (we will be
fixing that soon). it does show build number for the bosh release. when
bosh micro deploy was used build number would always be the same as
stemcell that director is deployed on (because bosh release was not
provided separately). with bosh-init director release is shipped separately
from the stemcell hence those numbers may not match.

On Thu, Dec 10, 2015 at 4:28 PM, William C Penrod <wcpenrod(a)gmail.com>
wrote:

I've been updating our bosh installations to release 219 with vsphere
stemcell 3115. When complete, bosh status shows it as version 3122. Usually
the bosh status is the same as the stemcell used when updating. I've not
noticed this mismatch before. Any idea why its different?

That works. Thanks!

On Thu, Dec 10, 2015 at 7:30 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

I try to include recommended stemcell version in release notes (e.g.
http://bosh.io/releases/github.com/cloudfoundry/bosh?version=235). In
practice it's a very soft recommendation so you can use any recent stemcell
version.

On Thu, Dec 10, 2015 at 6:25 PM, William C Penrod <wcpenrod(a)gmail.com>
wrote:

That makes sense. In the past I've used the build number of the bosh
release to select the stemcell to deploy it on. What's the recommended way
to determine the stemcell that was used to test and deploy the bosh release?

On Thu, Dec 10, 2015 at 5:58 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

bosh status unfortunetly doesnt show bosh release version (we will be
fixing that soon). it does show build number for the bosh release. when
bosh micro deploy was used build number would always be the same as
stemcell that director is deployed on (because bosh release was not
provided separately). with bosh-init director release is shipped separately
from the stemcell hence those numbers may not match.

On Thu, Dec 10, 2015 at 4:28 PM, William C Penrod <wcpenrod(a)gmail.com>
wrote:

I've been updating our bosh installations to release 219 with vsphere
stemcell 3115. When complete, bosh status shows it as version 3122. Usually
the bosh status is the same as the stemcell used when updating. I've not
noticed this mismatch before. Any idea why its different?