FQDN is not persistant after host reboot in vRealize Operations Manager 6.x
search cancel

FQDN is not persistant after host reboot in vRealize Operations Manager 6.x

book

Article ID: 343675

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

This article provides steps to set the hostname with FQDN in vRealize Operations Manager and keep the FQDN persistent after host reboot.

Symptoms:
 
  • Hostname is set with FQDN in vRealize Operations Manager.
  • After reboot of host, the contents of /etc/hosts file shows shortname and FQDN is not retained.


Environment

VMware vRealize Operations Manager 6.4.x
VMware vRealize Operations Manager 6.3.x
VMware vRealize Operations Manager 6.2.x

Resolution

This is a known issue affecting vRealize Operations Manager 6.x.
 
Currently, there is no resolution.
 
To work around this issue, perform these steps:
 
  1. Take cluster offline in vRealize Operations Manager as we will need to reboot host.
     
    1. Navigate to vROps_master_node_ip/admin or hostname/admin.

      Note: Replace vROPs_master_node_ip with the actual IP or hostname with actual hostname of vRealize Operations Manager master node.
       
    2. Login with admin and password.
    3. Under Cluster Status, click Take Offline and then provide a reason.

      For example:

      Reboot Host

      Note: Once Cluster Status is Offline, proceed to Step 2.
       
  2. Run this command to set hostname with FQDN:

    /opt/vmware/share/vami/vami_set_hostname FQDN_of_host

    Note: Replace FQDN_of_host with the actual FQDN
     
  3. In the /opt/vmware/bin/vcopsOvfDeployment.py file, change /bin/hostname to /bin/hostname -f.

    Note: Ensure to take a backup of the /opt/vmware/bin/vcopsOvfDeployment.py file.
     
    1. Edit the /opt/vmware/bin/vcopsOvfDeployment.py file using text editor.
    2. Update to:

      runScript('/opt/vmware/share/vami/vami_set_hostname /bin/hostname')
       
    3. Update to:

      runScript('/opt/vmware/share/vami/vami_set_hostname /bin/hostname -f')
       
    4. Save and close the file.

      Note: This is the main change which enables the FQDN to be persistent after the reboot as OS reads this file during startup.
       
  4. Reboot the host.

    Note: Post reboot, validate FQDN by opening SSH session and running the cat /etc/hosts command. FQDN should still be in place. If FQDN is still present in /etc/hosts file, repeat process on all other cluster nodes (if applicable) and then bring Cluster Online.


Additional Information

简体中文:在 vRealize Operations Manager 6.x 中重新引导主机后,FQDN 不再存在