When a cluster gets upgraded from 8.16 to 8.18. The primary node upgrades successfully, but the remaining nodes fail to upgrade. When attempting to upgrade the second node (which is in maintenance mode), the upgrade immediately reports “failed.”
Aria Operations for Logs 8.x
If the upgrade on a primary node or middle worker node is interrupted, the upgrade for the rest of the cluster will hang, and will need to be continued manually via the command line.
To upgrade VMware Aria Operations for Logs to the preferred version via the command line, please complete the following steps.
Note: If you are upgrading the cluster from scratch, start with the Primary node and then the subsequent worker nodes.
/usr/lib/loginsight/application/sbin/loginsight-pak-upgrade.py /tmp/pak_file/usr/lib/loginsight/application/sbin/loginsight-pak-upgrade.py /tmp/VMware-vRealize-Log-Insight-8.12.0-21618456.pak
See the Related Information section for steps to re-apply the certificate to ensure the internode communication certificate gets updated.
After completing the manual upgrade steps in the Resolution section, ensure the cluster gets the updated internode communication certificate by re-applying the certificate.
Follow Install a custom certificate if you are using a custom certificate for VMware Aria Operations for Logs.
If you are using the default certificate, follow Revert to the default certificate.
Impact/Risks:
Starting with VMware Aria Operations for Logs 8.12, the upgrade process updates the internode communication certificate. However, the certificate update only happens if the rolling upgrade is successful and won’t be triggered in case of a manual upgrade. To ensure the cluster gets the updated internode communication certificate, see the Related Information section for instructions on re-applying the certificate after completing the Resolution steps in this article.