TAS Apply Change Failing after Upgrade Using Stemcell 621.216
search cancel

TAS Apply Change Failing after Upgrade Using Stemcell 621.216

book

Article ID: 298284

calendar_today

Updated On:

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

Randomly some Diego cells are left unresponsive after upgrading the foundation from 2.10.X to 2.11.X and using the latest Linux stemcell 621.216.

Environment

Product Version: 2.11

Resolution

At this time, we recommend customers not use the latest stemcell 621.216 which has been removed from https://network.pivotal.io. The root cause as to why Diego Cells are left unresponsive is under investigation. It is safe to upgrade your TAS tile 2.10.X to 2.11.X, but do not use this stemcell. If you already upgraded TAS, we recommend reverting the stemcell change only following this KB.

Operations Manager (Ops Manager) UI always uses the latest Stemcell uploaded. If you accidentally upload a Stemcell that is newer than the one you intend to use there is a workaround to revert the change.

  1. Upload the previous stemcell you were using, in the Ops Manager VM in /var/tempest/stemcells bosh upload-stemcell /var/tempest/stemcells/bosh-stemcell-xyz

  2. Back up the installation.yml and actual-installation.yml file. cp /var/tempest/workspaces/default/installation.yml ~/installation-orig.yml

  3. Follow this KB to decrypt the installation.yml file and actual-installation.yml.

  4. Edit both files and replace the current stemcell with the previous stemcell version you uploaded step 1. See Snippet below for an example.

  5. Following KB to encrypt installation.yml and actual-installation.yml file

  6. Return to Ops manager GUI and confirm in the Stemcell Library the previous stemcell version is selected.

Snippet from installation.yml

    version: '621.216'

    file: bosh-stemcell-621.216-xxx

replace with

    version: '621.211'

    file: bosh-stemcell-621.211-xxx