Airgap Upgrade (agctl upgrade) from TCA 3.2 to 3.4 Fails with "apache-tomcat needs any of following packages" Error
search cancel

Airgap Upgrade (agctl upgrade) from TCA 3.2 to 3.4 Fails with "apache-tomcat needs any of following packages" Error

book

Article ID: 420317

calendar_today

Updated On:

Products

VMware Telco Cloud Automation

Issue/Introduction

When performing an Airgap upgrade using the agctl upgrade command to transition from Airgap 3.2 to 3.4, the process fails with an error indicating a dependency mismatch related to the Apache Tomcat package.

The following error is observed in the upgrade script output:

2025-xx-xxTxx-xx-xx+0000 ERROR: Following installed packages do not have their corresponding replacing packages available in the target repo.
 - apache-tomcat needs any of following packages in target repo - apache-tomcat10 apache-tomcat9
Original list of RPMs and RPM DB are stored in /tmp/photon-upgrade.sh-2025-xx-xx-xx-xx-xx, please provide contents of that folder along with system journal logs for analysis; these logs can be captured using command-
# /usr/bin/journalctl -xa > /tmp/photon-upgrade.sh-2025-xx-xx-xx-xx-xx/journal.log
Cannot continue. Aborting.

Environment

3.4

Cause

The upgrade process involves a CAP4 to CAP5 transition, which attempts to reinstall all packages from the previous system. The failure is caused by an RPM dependency mismatch for the apache-tomcat package.

Systems that were originally installed as Airgap 3.0.0 and subsequently upgraded to 3.2 have legacy packages like apache-tomcat that are no longer included in the base Airgap 3.1.0+ OVA or the 3.4 upgrade bundle. The photon-upgrade.sh script detects the presence of the older apache-tomcat package but cannot find a direct replacement (apache-tomcat10 or apache-tomcat9) in the target repository, thus aborting the upgrade.

Resolution

The permanent fix is planned for upcoming patch releases (TCA 3.3.0.1 and future 3.4 patches).

Additional Information

This issue is an artifact of upgrades from very early Airgap versions (3.0.0) where these packages were default installations. The issue is targeted to be fixed in future patch releases (3.3.0.1 and subsequent 3.4 patches) by modifying the upgrade script to correctly check and remove these packages before initiating the OS upgrade.