Upgrade to Aria Operation for Network version 6.11 fails, due to package discrepancy where deployment versions originating below 3.9 versions

Products

• VMware Aria Operations for Networks
• VMware Aria Suite

Issue/Introduction

Purpose of this Broadcom Knowledge base Article is to provide workaround for the upgrade failure issue and to unblock the upgrade failed deployments.

Symptoms:
Below error entries can be seen in centralized-upgrade.log on platform appliance and launcher latest.log on collector appliance.

Failed to fetch file:/var/cache/apt-cacher-ng/svc.ni.vmware.com/repo/ubuntu20/pool/main/v/v4l-utils/libv4l-0_1.18.0-2build1_amd64.deb File not found - /var/cache/apt-cacher-ng/svc.ni.vmware.com/repo/ubuntu20/pool/main/v/v4l-utils/libv4l-0_1.18.0-2build1_amd64.deb

Failed to fetch file:/var/cache/apt-cacher-ng/svc.ni.vmware.com/repo/ubuntu20/pool/main/v/v4l-utils/libv4lconvert0_1.18.0-2build1_amd64.deb  File not found - /var/cache/apt-cacher-ng/svc.ni.vmware.com/repo/ubuntu20/pool/main/v/v4l-utils/libv4lconvert0_1.18.0-2build1_amd64.deb

Environment

VMware vRealize Network Insight 6.6.0
VMware vRealize Network Insight 6.7.0
VMware vRealize Network Insight 6.3.x
VMware Aria Operations for Networks 6.11.0
VMware Aria Operations for Networks 6.10.0
VMware vRealize Network Insight 6.2.x
VMware vRealize Network Insight 6.4.0
VMware vRealize Network Insight 6.8.0
VMware vRealize Network Insight 6.5.1

Cause

Upgrade to Aria Operation for Network 6.11 fails due to package discrepancy.

Resolution

This issue is fixed in upcoming Aria Operation for Network  (vRNI) version 6.12.0

Workaround:

The below workaround has to be applied BEFORE the upgrade failure to 6.11.
Therefore, revert to snapshots/backups to prior the upgrade failures to apply the workarounds.
Also, the workaround has to be applied on all platforms and collectors.


1. Validate the version history shows earlier than version 3.9
 SSH to each Aria Operation for Network (vRNI) appliance as "consoleuser".
Run "show-version history" CLI. If you see versions below v3.9 then continue with rest of workaround steps.

Above is needed to scope which all vRNI appliance Nodes are in question where workaround needs to be applied.

2. Check  if below directory exists in the appliances(s):
  sudo ls -ld /var/cache/apt-cacher-ng/
 
3. If above command's output says no such file or directory, then create the directory using command below:
  sudo mkdir -p /var/cache/apt-cacher-ng/ 
If no error, then proceed to step 3.

4. Download vrni-packages.tar file, See attachment section on this KB.

 Validate the file on of the given below checksum:

 MD5: 6781B5EFC126A2413ED47E9CCD343805
 SHA1-SUM: E2F749A717B42C9D8F741CB1AFFECD8E3AB4DA29
 SHA-256: 2592D6E70F25F1FC811D068A68237FCD0A8A53B5C0EB4FAA62D585E12B690B83

 Commands to check checksum values as below:
 md5sum vrni-packages.tar
 sha1sum vrni-packages
 sha256sum vrni-packages
 
Output of above command should match the checksum value as per above mentioned.

5. Extract packages using below command:
   sudo tar -xvf /tmp/vrni-packages.tar -C /var/cache/apt-cacher-ng/

6. Update permissions, using below commands:
  sudo find /var/cache/apt-cacher-ng/ -type d ! -perm 2755 -exec chmod 2755 {} \;
 sudo find /var/cache/apt-cacher-ng/ -type f ! -perm 644 -exec chmod 644 {} \; 

7. Now proceed with upgrade to Aria Operation for Network (vRNI) 6.11.

Note:Please raise a support ticket to engage VMware GSS support, if you are not comfortable in running/executing  above steps.

Additional Information

Refer to VMware Aria Operations for Networks Release Notes:
https://docs.vmware.com/en/VMware-Aria-Operations-for-Networks/services/rn/vmware-aria-operations-for-networks-release-notes/index.html

Impact/Risks:
This is applicable to Aria Operation for Networks (vRNI) where deployment versions originating below 3.9 versions