Downtime for TCP Routes When Upgrading IST, TASW, and Services Tiles before TAS in TPCF
Article ID: 374487
Updated On:
Products
Issue/Introduction
Applications running on isolated_diego_cells and windows_diego_cells using TCP routes will experience downtime during upgrades with certain IST and TAS version combinations. Routes for apps using TCP Routing will not work until the TAS tile is updated to a fixed version.
Any applications making use of data services from the below tiles will experience downtime during upgrades, unless TAS is upgraded to a fixed version prior to updating the data services tiles. Applications using data services via TCP Routing will fail until the TAS tile is updated to a fixed version.
- SQL-with-MySQL-for-Tanzu-Application-Service
- Postgres for Tanzu Application Service
- GemFire for Tanzu Application Service
- Redis for VMware Tanzu Application Service
- RabbitMQ for Tanzu Application Service
Environment
You will be affected if you are using TCP Routes and Isolation Segments (IST) or Tanzu Application Service for Windows (TASW) and are currently on one of these versions of Tanzu Application Service for VMs (TAS):
- 4.0.25, 4.0.26
- 5.0.15, 5.0.16
- 6.0.5, 6.0.6
And are upgrading to one of these tile versions:
- Isolation Segments
- >= 4.0.27
- >= 5.0.17
- >= 6.0.7
- Tanzu Application Service for Windows
- >= 4.0.27
- >= 5.0.17
- >= 6.0.7
You will be affected if you are currently on one of these versions of Tanzu Application Service for VMs:
- 4.0.25, 4.0.26
- 5.0.15, 5.0.16
- 6.0.5, 6.0.6
And are upgrading to one of these tile versions:
- SQL-with-MySQL-for-Tanzu-Application-Service
- >= 3.3.1
- >= 3.2.2
- >= 3.1.5
- >= 3.0.8
- >= 2.10.18
- Postgres for Tanzu Application Service
- >= 1.1.4
- GemFire for Tanzu Application Service
- >= 2.1.1
- Redis for VMware Tanzu Application Service
- >= 3.5.1
- RabbitMQ for Tanzu Application Service
- >= 2.4.1
- >= 2.3.5
Cause
There is an incompatibility between the routing-api code in routing-release v0.301.0 and route-emitter code in diego-release >= 2.102.0.
There is an incompatibility between the routing-api code in routing-release v0.301.0 and route_registrar code in routing-release >= v0.302.0
Resolution
Upgrade TAS to at least the below versions, before upgrading any IST, TASW, or Data Service tiles:
- TAS 4.0.27+
- TAS 5.0.17+
- TAS 6.0.7+
Upgrading TAS first will ensure that your TAS tcp_router VMs are upgraded with the preventative fix prior to the affected tile VMs being updated.
Additional Information
The upgrade to a fixed version of TAS and new version of IST, TASW may be done in the same Ops Manager deployment.
Feedback
