Some VM's did not upgrade to new stemcell during Apply Changes
search cancel

Some VM's did not upgrade to new stemcell during Apply Changes

book

Article ID: 393295

calendar_today

Updated On:

Products

VMware Tanzu Application Service

Issue/Introduction

User upgrades VM's in environment to new stemcell. The Apply Changes completes successfully but some of the VM's in the deployment are still showing old stemcell.

Cause

This issue can occur if VM's were previously marked as 'bosh ignored' by the platform operators. These ignored instances were not 'unignored' before attempting to apply the new stemcell.

Resolution

To confirm the issue, run the below command and check if any of the instances in question are marked as 'ignored'.

bosh -d  <service-instance-deployment> instances --details

A.) If yes, then:

  1. 'bosh unignore' the VM's identified as 'ignored' from above step.
    bosh -d <service-instance-deployment> unignore vm
  2. Apply Changes again.

 

B.) If no, the user will need to troubleshoot further and/or open a ticket with TANZU Support by Broadcom.

Additional Information

Important Note Regarding mysql VM's:

If TAS core mysql VM's are identified as ignored instances by using the steps on this KB article, then it is recommended to check the health of the cluster before proceeding with the Resolution by running the mysql-diag command from the mysql_monitor VM.  ONLY proceed with the Resolution above if all VM's in the cluster are 'healthy' and 'synced' (example picture).  If the cluster is not healthy, then will need further troubleshooting first. Open a ticket with TANZU Support by Broadcom for assistance.