Upgrade is stuck on the collector(s) with error Node version mismatch for VMware Aria Operations for Networks
book
Article ID: 369666
calendar_today
Updated On:
Products
VCF Operations for Networks
Issue/Introduction
VMware Aria Operations Networks upgrade will stuck on the collector(s) and not progressed further even after waiting for a couple of hours.
Platform Node(s) upgrade on GUI shows completed but for collector(s) nodes it shows error "Node version mismatch" , refer to screenshot below:
The launcher latest.log will shows the .gnupg file permission errors.
Take an SSH to the collector using the user called support on the affected collector.
Type ub to switch to ubuntu mode.
Navigate to /var/log/arkin/launcher
Verify the below errors in the latest.log
2024-05-16T02:50:04.044Z ERROR launcher.upgrade.ServiceBundleDownloader launcher-upgrade-exec-2 verifySignedBundle:320 Failed to verify signed bundle /tmp/upgrade_infra-base-1706185032-addabb2e7d2565b384720214900724249518527092754391826.tgz.bundle. Output: gpg: WARNING: unsafe ownership on homedir '/home/ubuntu/.gnupg'
gpg: failed to create temporary file '/home/ubuntu/.gnupg/._lk0x0000557cc47b8780.vrni-proxy-release.12278': Permission denied
gpg: can't allocate lock for '/home/ubuntu/.gnupg/pubring.kbx': Permission denied
gpg: keyblock resource '/home/ubuntu/.gnupg/pubring.kbx': Permission denied
gpg: public key is 31077AF7C3Fxxxxx
gpg: encrypted with RSA key, ID 31077AF7C3Fxxxxx
gpg: decryption failed: No secret key
Environment
Aria Operations for Networks 6.12.0 Aria Operations for Networks 6.12.1
Cause
VMware Aria Operations for Networks upgrade collector(s) will stuck due to the permission issue on gnupg file on the appliance(s).
Resolution
To workaround this, perform below:
1. SSH to each collector and login as the support user and then switch to ubuntu user by typing the below command:
ub
2. Execute below mentioned command on each of the Collectors to correct the permissions of the .gnupg file.
sudo chown -R ubuntu:ubuntu /home/ubuntu/.gnupg
3. Post execution of the above solution the upgrade resumed further and gets completed, Screenshot for upgrade completion and Node version mismatch error fixed as below: