VCF Operations Fleet Management loses its networking configuration on reboot or during upgrade to 9.0.1

Products

• VCF Operations

Issue/Introduction

• Upgraded VCF Operations Fleet Management to 9.0.1 subsequently VCF Operations Fleet Management loses its networking configuration after reboot during the upgrade process
• Migration of host occurs due to HA failover causing the networking configuration to be lost for VCF Operations Fleet Management
• Networking is set correctly in the vApp properties of the appliance, you can use the following documentation as a guide to review the vApp properties Configure vApp Properties 

Environment

VCF Operations 9.0.1

Cause

Before reboot the network was STATIC. The VCF Operations Fleet Management attempts to get a DHCP IP after reboot. The system was then restored manually as STATIC.  All of these changes resulted in the loss networking configuration in VCF Operations Fleet Management.

Resolution

1. Take snapshot of VCF Operations Fleet Management. You can use the following as a guide Take Snapshots of a Virtual Machine 
2. Open web/remote console to VCF Operations Fleet Management appliance and sign in as root
3. Add the IP Address of VCF Operations Fleet Manager   

   nmctl set-static dev eth0 a ###.###.###.###/24 gw ###.###.###.###

   Note: please replacing the ###'s with the ip address of fleet manager and gateway

4.  Add DNS Servers:   

   nmctl set-dns dev eth0 dns ###.###.###.###

   Note replacing the ###'s with the ip address of the DNS server (If adding multiple DNS servers please use comma to separate the DNS IP addresses in the command) 

5. Reboot VCF Operations Fleet Manager 

Additional Information

Note: After resolving the network configuration issue and restoring Fleet Management connectivity, VCF Fleet Management version 9.0.1 may fail to come online due to the PostgreSQL service reporting the below error

 

vmware_vrlcm.log

 

Caused by: org.hibernate.exception.JDBCConnectionException: Unable to open JDBC Connection for DDL execution

        at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:112)

Caused by: org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

        at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:319)

 

journalctl -xeu vpostgres.service 

 

<Hostname> postgres[20638]: pg_ctl: could not open PID file "/var/vmware/vpostgres/current/pgdata/postmaster.pid": Permission denied

<Hostname> systemd[1]: vpostgres.service: Control process exited, code=exited, status=1/FAILURE

 

Follow this article#412351 for Resolution