During a platform upgrade cycle, after successfully upgrading Tanzu Application Service (TAS) to version 10.4.0, subsequent attempts to stage and deploy the accompanying Isolation Segment tile fail. The staging and migration engine halts abruptly with a fatal JavaScript runtime error during the configuration validation phase, preventing the operator from applying pending changes.
Platform Management: Tanzu Operations Manager 3.3.0
Control Plane Product: Elastic Application Runtime (TAS) upgraded from 10.2.9 to 10.4.0
Data Plane Product: Isolation Segment tile attempting an upgrade from 10.2.9 to 10.4.0
Foundation Trajectory: Upgraded continuously over time starting from version 10.2.7
A known platform defect in the migration engine causes Operations Manager to lose its file-based record of previously executed migrations within the /var/tempest/workspaces/default/product_data_migrations/ directory. This metadata loss results in misalignment of the state of the product tile.
When the Isolation Segment 10.4.0 tile is staged, the upgrade framework reads the missing tracking ledger and incorrectly treats the existing deployment as a brand-new installation. It then attempts to force-execute historical, legacy JavaScript delta scripts sequentially from the beginning of the product line (dating back to 2017/2018), such as 201708150940_ssl_cipher_for_router.js. These scripts attempt to validate deprecated properties that were completely removed from the 10.3.x and 10.4.x architectures. The modern node --check validation engine encounters an unresolvable reference and crashes with a TypeError: Cannot read property 'value' of undefined error.
Because the underlying persistent migration ledger for the tile has been corrupted within the configuration blob, the upgrade process must be corrected by purging the local workspace directory cache and cleanly reinstalling the tile configuration.
Please create a Tanzu Support ticket for assistance.