Upgrading TPCF Small Footprint to 10.3.x fails with "Can't change static ip addresses and instance count at the same time for job 'TCP Router'"
search cancel

Upgrading TPCF Small Footprint to 10.3.x fails with "Can't change static ip addresses and instance count at the same time for job 'TCP Router'"

book

Article ID: 432225

calendar_today

Updated On:

Products

VMware Tanzu Platform Core

Issue/Introduction

When attempting to upgrading the TPCF small footprint tile to 10.3.x, it returns the error "Can't change static ip addresses and instance count at the same time for job 'TCP Router'".

This prevents you from running the upgrade.

 

Environment

TPCF Small Footprint 10.3.x

Cause

This occurs when running TPCF Small Footprint with the TCP routing enabled.

In Small Footprint versions prior to 10.3, the TCP Router and Gorouter run on different VMs: the TCP Router runs on the tcp_router instance group and Gorouter runs on the router instance group. Starting in Small Footprint 10.3, the TCP Router runs on the router instance group, where it is colocated with Gorouter.

 

Resolution

All Small Footprint environments using static IPs for TCP Router must remove those static IPs and deploy before upgrading to 10.3.

You will need to first remove the Static IP from TPCF Small Footprint tile -> Networking -> TCP router IPs.

More details on this can be found here, under "Change: On Small Footprint only, TCP Router job is moving to the Router Instance Group"

https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/breaking-changes.html