vRealize Automation 7.x is configured with shortname instead of FQDN
search cancel

vRealize Automation 7.x is configured with shortname instead of FQDN

book

Article ID: 325925

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:

  • Embedded Horizon vIDM Connectors do not show up or generate errors as seen below:

    ERROR (SimpleAsyncTaskExecutor-1) [;;] com.vmware.horizon.connector.admin.ObjectPushEngine - Exception in REST call. Error code: 400 : Error body: {"errors":[{"code":"form.invalid.host","message":"Host is not valid. It has to be a valid fully qualified domain name (FQDN) or an IPv4 address.","parameters":null}]}
     
  • Logging in to the vRA portal, under Administration > Connectors, you see connector(s) hostname showing only shortname instead of FQDN.

Environment

VMware vRealize Automation 7.x

Cause

This issue occurs because Horizon Identity Provider ldP connectors are not compatible with short name.

Resolution

To resolve the issue:
 
  1. Change the Primary Appliance Host Name following the below procedure.

     
    1. In DNS, create an additional record with the new primary host name.

      Note: Do not remove the existing DNS record with the old host name yet.
    2. Wait for DNS replication and zone distribution to occur.
    3. Log in as root on the primary vRealize Automation appliance management interface https://vrealize-automation-appliance-FQDN:5480
    4. Click Network > Address.
    5. In the Hostname text box, enter the new primary host name, and click Save Settings.
    6. From a console session as root on the primary vRealize Automation appliance, run the script:

      /usr/lib/vcac/tools/change-hostname/change-hostname_master.sh new-primary-hostname old-primary-hostname
       
    7. Run the script one time for each directory in the current environment. There might be multiple directories per tenant.

      For example, if you have two directories, run the script twice, one after the other.
    8. Run this script from a console session:
       
      sed -i "s/old-primary-hostname/new-primary-hostname/g" "/etc/haproxy/conf.d/10-psql.cfg" "/etc/haproxy/conf.d/20-vcac.cfg"
      echo new-primary-hostname > /usr/local/horizon/conf/flags/sysconfig.hostname
       
    9. Restart the primary vRealize Automation appliance.
    10. Log in as root on each replica vRealize Automation appliance management interface https://vrealize-automation-appliance-FQDN:5480
    11. Click vRA Settings > Cluster.
    12. Use Join Cluster to re-join each replica node to the cluster.
    13. Verify that all authentication connectors are working correctly.
    14. In DNS, remove the existing DNS record with the old primary host name.

       
  2. Change a Replica vRealize Automation Appliance Host Name following the below procedure:
     
    1. In DNS, create an additional record with the new replica host name.

      Note: Do not remove the existing DNS record with the old host name yet.
    2. Wait for DNS replication and zone distribution to occur.
    3. Log in as root on the replica vRealize Automation appliance management interface https://vrealize-automation-appliance-FQDN:5480
    4. Click Network > Address.
    5. In the Hostname text box, enter the new primary host name, and click Save Settings.
    6. From a console session as root on the replica vRealize Automation appliance, run the script:

      /usr/lib/vcac/tools/change-hostname/change-hostname_replica.sh new-replica-hostname old-replica-hostname
       
    7. From a console session as root on the primary vRealize Automation appliance, run the script:
       
      /usr/lib/vcac/tools/change-hostname/change-hostname_master.sh new-replica-hostname old-replica-hostname
       
      sed -i "s/old-replica-hostname/new-replica-hostname/g" "/etc/haproxy/conf.d/10-psql.cfg" "/etc/haproxy/conf.d/20-vcac.cfg"
      echo primary-hostname > /usr/local/horizon/conf/flags/sysconfig.hostname
       
    8. From a console session as root on each replica vRealize Automation appliance, run the commands:
       
      sed -i "s/old-replica-hostname/new-replica-hostname/g" "/etc/haproxy/conf.d/10-psql.cfg" "/etc/haproxy/conf.d/20-vcac.cfg" "/usr/local/horizon/conf/flags/sysconfig.hostname"
      echo new-replica-hostname > /usr/local/horizon/conf/flags/sysconfig.hostname
    9. Log in as root on the replica vRealize Automation appliance management interface, https://vrealize-automation-appliance-FQDN:5480
    10. Click vRA Settings > Cluster.
    11. Use Join Cluster to re-join the replica node to the cluster.
    12. Verify that all authentication connectors are working correctly.
    13. In DNS, remove the existing DNS record with the old replica host name.
 
After following above steps, if you do not see all connectors listed (in case of vRealize Automation configured in High Availability mode), refer to the KB to rejoin the vRA cluster:
 
Once you see Identity Provider connectors, change the IdP Hostname under Identity Providers to load Bblancer 'VIP' FQDN (in the case of HA configured vRA appliances).



Powered by Wolken Software