Applying VMware Aria Suite Lifecycle 8.18 Patch 5 fails with error: Packages - tree - are not available in the target repo for OS upgrade. Please provide the correct repo having the required packages.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Patching VMware Aria Lifecycle Manager (vRLCM) version 8.18 with Patch 5 fails to complete.

The update process fails at step 1 when patching the VMware Identity Manager first as stated in the installation instructions from the following KB:

CSP-102092 Patch Instructions for VMware Identity Manager 3.3.7 and VMware Aria Suite Lifecycle 8.18.0 Patch 5  https://knowledge.broadcom.com/external/article/412021 

When applying patch 5 the below error is seen:

• Error in  /var/log/vrlcm/os-package-update.log similar to below extract

Error: Packages - tree - are not available in the target repo for OS upgrade. Please provide the correct repo having the required packages.
Original list of RPMs and RPM DB are stored in /tmp/photon-upgrade-biN,  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-biN/journal.log
 Cannot continue. Aborting.

• Error in  /var/log/vrlcm/os-package-update.log similar to below extract related to json-glib,paho-c,syslog-ng  packages

Refreshing metadata for: 'VMWare Photon Linux ISO'
Metadata cache created.
 Finalise list of replacing packages
 * network-config-manager provides netmgmt
 * apache-tomcat10 provides apache-tomcat
 Finding packages in the target repo. This may take several minutes.
 Error: Packages - json-glib paho-c syslog-ng - are not available in the target repo for OS upgrade. Please provide the correct repo having the required packages.
 Original list of RPMs and RPM DB are stored in /tmp/photon-upgrade.sh-yy-mm-date-03-19-47,  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-11-22-03-19-47/journal.log
 Cannot continue. Aborting.

Environment

VMware Aria Suite Lifecycle 8.18
VMware Identity Manager 3.3.7

Cause

As part of the upgrade process, checks for packages installed are performed. This check identified a package that is not a required package which results in the seen failure. 

The Aria Lifecycle Manager patching mechanism relies on its internal package manager to upgrade all installed packages to versions compatible with the new patch level.

When a non-standard package 'tree' is encountered, the package manager cannot find a compatible update for it within the official vRLCM repositories.

This dependency resolution failure causes the entire upgrade process to abort.

Resolution

To resolve this issue, the conflicting tree package must be removed from the Aria Lifecycle Manager appliance before attempting the Patch 5 upgrade.

Procedure:

1. Take a snapshot of the vRLCM appliance before attempt to apply the patch.

2.Connect to your Aria Lifecycle Manager appliance using its IP address or FQDN.

    Log in as root.

    ssh root@<vRLCM_IP_or_FQDN>

3.Identify the tree package:

Execute the following command on the appliance to find the exact name of the installed tree package:

rpm -qa | grep tree

rpm -qa | grep json-glib

rpm -qa | grep paho-c

rpm -qa | grep syslog-ng

   

4.Remove the conflicting package: 

This action removes a non-standard package. 

          rpm -e <Full Package Name Identified>

   
   Note Replace <Full Package Name Identified> with the exact package name identified in the previous step when running command rpm -qa | grep tree

5.Initiate Patch Level 5 Update

Follow the standard patching instructions as detailed in the official Broadcom documentation:

CSP-102092 Patch Instructions for VMware Identity Manager 3.3.7 and VMware Aria Suite Lifecycle 8.18.0 Patch 5

https://knowledge.broadcom.com/external/article/412021 

After the update completes, verify the health status of the Aria Lifecycle Manager appliance and confirm that all services are running correctly.

Ensure the appliance is reporting the correct patch level (Patch 5) in the UI.