Upgrade to vRealize Operations Manager 8.0 stuck on step 5 of 9 in pure IPv6 Clusters
search cancel

Upgrade to vRealize Operations Manager 8.0 stuck on step 5 of 9 in pure IPv6 Clusters

book

Article ID: 319669

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • The upgrade to vRealize Operations Manager 8.0 is stuck on step 5 of 9 when the vRealize Operations Manager cluster is only configured with IPv6 addresses.


Environment

VMware vRealize Operations Manager 7.5.x
VMware vRealize Operations Manager 6.6.x
VMware vRealize Operations 8.x
VMware vRealize Operations Manager 7.0.x
VMware vRealize Operations Manager 6.7.x

Cause

This issue is caused by the hostname not getting picked up via DNS records.

Resolution

To resolve this issue, set the hostname prior to the upgrade to vRealize Operations Manager 8.0.
If required, revert back to the snapshots taken before the upgrade attempt to vRealize Operations Manager 8.0, then follow the steps below.
  1. Log into the Primary node as root via SSH or Console.
  2. Run the following command to set the hostname:
/opt/vmware/share/vami/vami_set_hostname hostname

Note: Replace hostname with the hostname configure in DNS records for this vRealize Operations Manager node.
Example: /opt/vmware/share/vami/vami_set_hostname MasterNode
  1. Repeat steps 1-3 on all other nodes, including remote collectors, in the vRealize Operations Manager cluster.
  2. Run the following command on the Primary node (and Primary Replica node if HA is enabled) to restart the gemfire-locator service:
service vmware-vcops restart gemfire-locator
  1. Follow How to take a Snapshot of vRealize Operations Manager to take a new snapshot of the vRealize Operations Manager cluster.
  2. Proceed with the upgrade to vRealize Operations Manager 8.0.


Powered by Wolken Software