Stemcell Library page incorrectly displays Deployed stemcell version

Products

• Operations Manager

Issue/Introduction

Customer might initiate a deployment to upgrade the stemcell for various tiles using Apply Change. However, the Apply Changes fails before reaching certain tiles.  For these tiles, it is expected to show the previously used stemcell version as deployed.​​ However, the Stemcell Library page may incorrectly display the desired (new) stemcell version as Deployed.

​

In contrast, the Review Pending Changes page correctly reflects the upcoming update with the message: “Update stemcell from <actual-version> to <desired-version>.”

The incorrect stemcell version is shown as deployed at the following Ops Manager API endpoints as well: 

• /api/v0/stemcell_associations → shows stemcells linked to tiles
• /api/v0/stemcell_assignments → shows stemcells currently in use by products

The BOSH CLI shows the correct, expected deployed stemcell:

• Run bosh vms --vitals → lists VMs and the stemcell ID each one uses

The Deployment Manifest also shows the expected stemcell:

• Use bosh manifest → shows the exact stemcell version defined for the deployment

Environment

Operations manager

Cause

Ops Manager saves the deployment state right after updating runtime configs for all tiles.  This persists the stemcell update before any tile updates begin. This means that even if a deployment fails before reaching a specific tile, the updated stemcell settings remain saved.

Resolution

To mitigate, proceed with the Apply Changes with the desired stemcell on the tile. The stemcell will then be used, and the state will converge.