Quantcast
Channel: VMware Communities : All Content - vRealize Automation Tools
Viewing all articles
Browse latest Browse all 9859

Potential Bug Found: HTTP 400 Errors for Dynamically Generated Dropdowns in Property Definitions when Multi-Tenancy is in Place - Workaround Included

$
0
0

Hi all,

 

I've stumbled on an issue creating dynamically generated dropdowns for use in property definitions when the following conditions are in place:

 

1. You have a multi-tenant environment.

2. Each tenant is pointing to a DIFFERENT vRO instance. For example, you have a DEV tenant which points to your DEV vRO while your vsphere.local points to your Production VRO.

3. You are trying to configure a dynamically generated dropdown that is NOT on vsphere.local.

4. I'm using vRA version 7.1.

 

As I created the property definition and bound the values to the external vRO action that returns an array of strings, I received a generic "An error has occurred banner" on the GUI and the new dynamic property was not added. I was able to pick the vRO action from the list of items that are native to the configured vRO for my DEV tenant. It isn't until I clicked "Submit" that I received the warning banner. I was also unable to find the stack trace for this failure in the log section of the vRA GUI. In order to capture what is going on, I had to look at the catalina.out file in /storage/log/vmware/vcac. Here I saw the following at the top of an error stack trace shortly after clicking the "Submit" button:

 

com.vmware.vcac.platform.service.rest.resolver.ApplicationExceptionHandler.handleHttpStatusCodeException:673 - 404 not found

 

The workaround: I had to change the vRO configuration on the vsphere.local tenant to match the configuration on the DEV tenant. Before hand I tried to import the action from DEV's vRO instance into vsphere.local's, but I'm assuming the change in action GUIDs between the two still caused the same error to occur. Now I am able to get the dropdown working in the DEV tenant at the expense of having my vsphere.local pointing to something I do not want it to.

 

Maybe this is something that can be fixed in 7.2?


Viewing all articles
Browse latest Browse all 9859

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>