Connecting vRealize Orchestrator Plugin for Horizon to Horizon Cluster behind Load balancer fails
search cancel

Connecting vRealize Orchestrator Plugin for Horizon to Horizon Cluster behind Load balancer fails

book

Article ID: 345127

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • Connecting vRealize Orchestrator Plugin for Horizon to Horizon Cluster behind Load balancer fails.
  • If Horizon cluster is behind a Load balance and IT admin executes "Add View Pod In Configuration" workflow in vRealize Orchestrator Plugin for Horizon, the workflow fails with the error similar to:

    ERROR {:8a1cxxxxxxxxxxxxxxxxxxxxxxxx040f} [SCRIPTING_LOG] [Add View Pod In Configuration (10/30/18 07:05:49)] Error in (Workflow:Add View Pod In Configuration / Ping connection servers (item7)#6) java.net.ConnectException: Connection timed out (Connection timed out)
    2018-10-30 07:09:07.775-0400 ERROR {:8a1cxxxxxxxxxxxxxxxxxxxxxxxx040f} [SCRIPTING_LOG] Workflow execution stack:
    ***
    item: 'Add View Pod In Configuration/item7', state: 'failed', business state: 'null', exception: 'java.net.ConnectException: Connection timed out (Connection timed out) (Workflow:Add View Pod In Configuration / Ping connection servers (item7)#6)'
    workflow: 'Add View Pod In Configuration' (5a22xxxx-xxxx-xxxx-xxxx-xxxxxxxx4195) 
    |  'attribute': name=viewPodConfiguration type=ConfigurationElement value=dunes://service.dunes.ch/ConfigurationElement?id='779dxxxx-xxxx-xxxx-xxxx-xxxxxxxx5128'&dunesName='ConfigurationElement'
    |  'attribute': name=continueUpdate type=boolean value=true
    |  'attribute': name=isTrustedSSLCertificate type=boolean value=true
    |  'attribute': name=connectionServers type=Array/string value=#{#string#https://FullQualifiedDomainName:443#;#string#https://FullQualifiedDomainName:443#;#string#https://FullQualifiedDomainName:443#;#string#https://FullQualifiedDomainName:443#}#
    |  'attribute': name=csIndex type=number value=4.0
    |  'attribute': name=ignoreWarnings type=boolean value=false
    |  'attribute': name=importCertificateErrorCode type=string value=
    |  'attribute': name=untrustedServers type=Array/string value=__NULL__
    |  'input': name=oneCSHost type=string value=HostName
    |  'input': name=oneCSDomain type=string value=DomainName
    |  'input': name=username type=string value=UserName
    |  'input': name=password type=SecureString value=__NULL__
    |  'input': name=podAlias type=string value=Enterprise
    |  'no outputs'


Resolution

This is a known issue affecting VMware vRealize Orchestrator Plugin for Horizon 1.x.

Currently, there is no resolution.

Workaround:
To work around this issue, move the vRealize Orchestrator which installs the vRealize Orchestrator Plugin for Horizon behind the same Load Balancer as Horizon Cluster.