vsphere plugin returns null values until service is restarted or vCenter instance is updated

Products

• VMware vCenter Server

Issue/Introduction

• Aria Automation Orchestrator vSphere plugin returns null values until the orchestrator service is restarted or vCenter instance is updated.
• The var/log/vmware/vpxd/vpxd.log log in vcenter contains an invalid login error which cites an expired token as the cause:
  
  

  2024-09-29T19:25:31.543Z error vpxd[] [Originator@ sub=Default opID=<OPID>] [VpxLRO] -- ERROR lro--- <ID> -- SessionManager -- vim.SessionManager.loginByToken: :vim.fault.InvalidLogin
  --> Result:
  --> (vim.fault.InvalidLogin) {
  -->    faultCause = (vmodl.MethodFault) null, 
  -->    faultMessage = <unset>
  -->    msg = ""
  --> }
  --> Args:
  --> 
  --> Arg locale:
  --> "en"
  2024-09-29T19:25:31.548Z info vpxd[] [Originator@ sub=vpxLro opID=<OPID>] [VpxLRO] -- BEGIN lro- -- SessionManager -- vim.SessionManager.loginByToken -- <ID> 
  2024-09-29T19:25:31.550Z error vpxd[] [Originator@ sub=MoSessionMgr opID=<OPID>] [SessionManagerMo::LoginByToken] Couldn't find the SAML token due to N9SsoClient14ParseExceptionE(The token has expired at: 2024-09-28T08:49:53.37Z)

Environment

Aria Automation Orchestrator 8.x

Cause

The issue here is caused by the fact that the Orchestrator server sometimes provides expired tokens to the plugins, vSphere plugin in this example.

Resolution

The issue is resolved in the Aria Automation Orchestrator 8.18.1 release.



To workaround the issue on version 8.16 you can run the below script:


1. As a best practice pre-caution before making any changes first snapshot the Aria Automation Orchestrator appliance 


2. SSH to appliance as root user and run below script:

Please note that this will restart the orchestrator pod.

base64 -d <<< "aWYgZ3JlcCAtcSAnc2Vzc2lvbi1yZWdpc3RyeS1jYWNoZS54bWwnIC9vcHQvY2hhcnRzL3Zjby90ZW1wbGF0ZXMvZGVwbG95bWVudC55YW1sOyB0aGVuCiAgICBlY2hvICJBbHJlYWR5IHBhdGNoZWQiCiAgICBleGl0IDEKZmkKCmVjaG8gIlBhdGNoaW5nIGRlcGxveW1lbnQgdGVtcGxhdGUiCnZyYWNsaSBjbHVzdGVyIGV4ZWMgLS0gc2VkIC1pICJzIy4vY3JlYXRlX3NlcnZlcl9zeW1saW5rcyMuL2NyZWF0ZV9zZXJ2ZXJfc3ltbGlua3MgXCZcJiBzZWQgLWkgLXogJ3MrZXRlcm5hbD1cXFxcXCJ0cnVlXFxcXFwiK2V0ZXJuYWw9XFxcXFwiZmFsc2VcXFxcXCIgdGltZVRvTGl2ZVNlY29uZHM9XFxcXFwiNjBcXFxcXCIrMicgL3Vzci9saWIvdmNvL2FwcC1zZXJ2ZXIvY29uZi9jYWNoZXMvc2Vzc2lvbi1yZWdpc3RyeS1jYWNoZS54bWwjZyIgL29wdC9jaGFydHMvdmNvL3RlbXBsYXRlcy9kZXBsb3ltZW50LnlhbWwKCmVjaG8gIlBhdGNoaW5nIGV4aXN0aW5nIGRlcGxveW1lbnQiCmt1YmVjdGwgLW4gcHJlbHVkZSBnZXQgZGVwbG95bWVudCB2Y28tYXBwIC1vIHlhbWwgfCBzZWQgInMjLi9jcmVhdGVfc2VydmVyX3N5bWxpbmtzIy4vY3JlYXRlX3NlcnZlcl9zeW1saW5rcyBcJlwmIHNlZCAtaSAteiAncytldGVybmFsPVxcXFxcInRydWVcXFxcXCIrZXRlcm5hbD1cXFxcXCJmYWxzZVxcXFxcIiB0aW1lVG9MaXZlU2Vjb25kcz1cXFxcXCI2MFxcXFxcIisyJyAvdXNyL2xpYi92Y28vYXBwLXNlcnZlci9jb25mL2NhY2hlcy9zZXNzaW9uLXJlZ2lzdHJ5LWNhY2hlLnhtbCNnIiB8IGt1YmVjdGwgLW4gcHJlbHVkZSByZXBsYWNlIC1mIC0KCmVjaG8gIkRvbmUi" | bash -

Additional Information

The same issue is also seen in the vRA plugin and in Multi-Node Plugin, where a generic 403 http error is thrown without an explanation.