Search the VMware Knowledge Base (KB)
View by Article ID

vRealize Operations Manager vApp install or upgrade stuck running at first boot when running ./install.sh (2150424)

  • 0 Ratings

Symptoms

  • Installing or upgrading vRealize Operations Manager vApp at first boot when running ./install.sh.
  • The vRealize Operations Manager node does not have full external network access

Cause

This issue occurs if Java timezone updater traffic is blocked and it fails to connect to internet to update the timezones during firstboot.

Resolution

This issue is resolve in vRealize Operations Manager 6.6 and later, available at VMware Downloads.
 
To work around the issue, the Java timezone updater traffic must be rejected instead of blocking in the firewall.

Use one of these options:
  • Move the vRealize Operations Manager nodes to a standard switch with no vmnics during upgrade or deployment.After upgrade or deployment the vRealize Operations Manager nodes can be migrated to a portgroup with networking.
  • Enter bogus networking configuration during vApp deployment. After upgrade or deployment f, change the IP Address of a vRealize Operations Manager 6.x Single Node Deployment or change the IP Address of a vRealize Operations Manager 6.x Multi Node Deployment to a working network configuration.
  • During upgrade or deployment configure your firewall traffic to reject and not block  from the vRealize Operations Manager nodes. After upgrade or deployment, return the firewall configuration to normal.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: