"500, OK" Banner Appears When Running Workflows
search cancel

"500, OK" Banner Appears When Running Workflows

book

Article ID: 372971

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

  • When running a workflow the user sees a Red Banner pop up at the top like so: 

 

  • This is reflected in the vRO  logs (/services-logs/prelude/vco-app/file-logs/vco-server-app.log) with an error similar to:
202X-XX-XXTXX:XX:XX:XXXZ ERROR vco [host='vco-app-XXXXXX' thread='XXXXXX' user='XXXXXX' org='XXXXXX' trace='-'] {} com.vmware.o11n.service.factory.VcoFactoryFacade - Unable to login user:XXXXXX (Ex: javax.security.auth.login.LoginException: Can not login in VMware Aria Automation with username and password)

or

2024-XX-XXTXX:XX:XX.XXXZ ERROR vco [host='vco-app-XXXXX' thread='ceip-thread-worker' user='' org='' trace=''] {} org.springframework.scheduling.support.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduled task
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'client' defined in com.vmware.o11n.telemetry.server.ServerTelemetryConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.ph.client.api.PhClient]: Factory method 'client' threw exception; nested exception is java.lang.RuntimeException: Error setting accepted issuers to client.
        at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-5.3.32.jar:5.3.32]
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.ph.client.api.PhClient]: Factory method 'client' threw exception; nested exception is java.lang.RuntimeException: Error setting accepted issuers to client.
Caused by: java.lang.RuntimeException: Error setting accepted issuers to client.

Environment

  • VMware Aria Automation Orchestrator 8.x (formerly VMware vRealize Orchestrator 8.x)

Cause

  • Issue is related to caching of internal factories, key collision of these factories and potentially the heavy use of Basic Authentication in the environment.

Resolution

  1. SSH to one of the Aria Automation appliance(s) with root user credentials.
  2.  Run the following on any node in the Aria Automation Cluster:
base64 -d <<< "aWYgZ3JlcCAtcSAnc2Vzc2lvbi1yZWdpc3RyeS1jYWNoZS54bWwnIC9vcHQvY2hhcnRzL3Zjby90ZW1wbGF0ZXMvZGVwbG95bWVudC55YW1sOyB0aGVuCiAgICBlY2hvICJBbHJlYWR5IHBhdGNoZWQiCiAgICBleGl0IDEKZmkKCmVjaG8gIlBhdGNoaW5nIGRlcGxveW1lbnQgdGVtcGxhdGUiCnZyYWNsaSBjbHVzdGVyIGV4ZWMgLS0gc2VkIC1pICJzIy4vY3JlYXRlX3NlcnZlcl9zeW1saW5rcyMuL2NyZWF0ZV9zZXJ2ZXJfc3ltbGlua3MgXCZcJiBzZWQgLWkgLXogJ3MrZXRlcm5hbD1cXFxcXCJ0cnVlXFxcXFwiK2V0ZXJuYWw9XFxcXFwiZmFsc2VcXFxcXCIgdGltZVRvTGl2ZVNlY29uZHM9XFxcXFwiNjBcXFxcXCIrMicgL3Vzci9saWIvdmNvL2FwcC1zZXJ2ZXIvY29uZi9jYWNoZXMvc2Vzc2lvbi1yZWdpc3RyeS1jYWNoZS54bWwjZyIgL29wdC9jaGFydHMvdmNvL3RlbXBsYXRlcy9kZXBsb3ltZW50LnlhbWwKCmVjaG8gIlBhdGNoaW5nIGV4aXN0aW5nIGRlcGxveW1lbnQiCmt1YmVjdGwgLW4gcHJlbHVkZSBnZXQgZGVwbG95bWVudCB2Y28tYXBwIC1vIHlhbWwgfCBzZWQgInMjLi9jcmVhdGVfc2VydmVyX3N5bWxpbmtzIy4vY3JlYXRlX3NlcnZlcl9zeW1saW5rcyBcJlwmIHNlZCAtaSAteiAncytldGVybmFsPVxcXFxcInRydWVcXFxcXCIrZXRlcm5hbD1cXFxcXCJmYWxzZVxcXFxcIiB0aW1lVG9MaXZlU2Vjb25kcz1cXFxcXCI2MFxcXFxcIisyJyAvdXNyL2xpYi92Y28vYXBwLXNlcnZlci9jb25mL2NhY2hlcy9zZXNzaW9uLXJlZ2lzdHJ5LWNhY2hlLnhtbCNnIiB8IGt1YmVjdGwgLW4gcHJlbHVkZSByZXBsYWNlIC1mIC0KCmVjaG8gIkRvbmUi" | bash -

This sets the Session Cache to expire after 1 minute (it has no expiry by default).