I have a property defined with external value (vRO action). When selecting an IaaS catalog item with this property included the following error appears at the top of the browser:
Unable to refresh request form from the server Invalid argument
If I re-configure the property definition back to static ...
apples:apples
oranges:oranges
bananas:bananas
... then it works fine. I have seen differing solutions that either return a value of type string/array or Properties. Regardless of what my vRO action returns I get the same error indicated in the title:
var myReturnValue = [ 'apples' , 'oranges' , 'bananas' ]
return myReturnValue
.... or ....
var myReturnValue = { 'apple':'apple' , 'oranges':'oranges , 'bananas':'bananas' }
return myReturnValue
.... or ....
var myReturnValue = new Properties()
myReturnValue.put ( 'apples' , 'apples' )
myReturnValue.put ( 'oranges' , 'oranges' )
myReturnValue.put ( 'bananas' , 'bananas' )
return myReturnValue
The action logs the value of myReturnValue as well as the object type and object class name just to confirm I have the right type. When I compare my code to other code in the environment or code provided by VMware (all of the referenced actions in Configuration Details for the vRealize Orchestrator Action Custom Property Definitions) I don't see any real difference.
This is the response I got from GSS:
Based on the log messages in catalina.out, the cause of the error "Unable to refresh request form from server" during request time, is due to the value of maximum lease days for component blueprint being less than that of the top level blueprint. Please see below:
./catalina.out.18-38826-2018-11-30 15:01:56,378 vcac: [component="cafe:shell" priority="ERROR" thread="tomcat-http--5" tenant="<name of tenant>" context="v9gvU8ZC" parent="" token="v9gvU8ZC"] composition-service:requestForm.logToApacheCommons:59 - <d7e8c483> Error: {"errors":[{"code":900124,"source":null,"message":"Values for [_leaseDays] are less restrictive than original values.","systemMessage":"Values for [_leaseDays] are less restrictive than original values.","moreInfoUrl":null}]}
./catalina.out.18-38827-2018-11-30 15:01:56,378 vcac: [component="cafe:shell" priority="ERROR" thread="tomcat-http--5" tenant="<name of tenant>" context="v9gvU8ZC" parent="" token="v9gvU8ZC"] composition-service:requestForm.logToApacheCommons:59 - <d7e8c483> Error: {"errors":[{"code":900124,"source":null,"message":"Values for [_leaseDays] are less restrictive than original values.","systemMessage":"Values for [_leaseDays] are less restrictive than original values.","moreInfoUrl":null}]}
./catalina.out.18:38828:2018-11-30 15:01:56,379 vcac: [component="cafe:shell" priority="ERROR" thread="tomcat-http--5" tenant="<name of tenant>" context="v9gvU8ZC" parent="" token="v9gvU8ZC"] composition-service:requestForm.logToApacheCommons:59 - <d7e8c483> Unable to refresh request form from the server
./catalina.out.18-38829-Values for [_leaseDays] are less restrictive than original values.
./catalina.out.18-38830-Error: {"errors":[{"code":900124,"source":null,"message":"Values for [_leaseDays] are less restrictive than original values.","systemMessage":"Values for [_leaseDays] are less restrictive than original values.","moreInfoUrl":null}]}
As this was for a temporary throw-away blueprint I didn't bother making the necessary changes and testing. I wish this detail was bubbled up to the UI. It would make troubleshooting so much easier.
Couple of questions...
Are you using vRA Custom Forms?
Your custom property, is set set as a string using a DropDown?
If it does not reveal too much can you post a screenshot of the property?
Steve
sbeaver:
Are you using vRA Custom Forms?
No, I'm using standard IaaS form which means I'm limited by property definitions.
Your custom property, is set set as a string using a DropDown?
Yes.
If it does not reveal too much can you post a screenshot of the property?
I suspect though that the vRO action maybe more useful:
I have had some "grief" in the past with property group returning the value as expected and to be totally honest I have not spend that much time on it if I was able to achieve the results using another method. With that said.... Have you tried using that action in the presentation layer of the vRO workflow to see if you get the expected results? I think you will find that method work a little more consistently with a little less grief.
Also I believe the log file you are looking for is the scripting log
This is the response I got from GSS:
Based on the log messages in catalina.out, the cause of the error "Unable to refresh request form from server" during request time, is due to the value of maximum lease days for component blueprint being less than that of the top level blueprint. Please see below:
./catalina.out.18-38826-2018-11-30 15:01:56,378 vcac: [component="cafe:shell" priority="ERROR" thread="tomcat-http--5" tenant="<name of tenant>" context="v9gvU8ZC" parent="" token="v9gvU8ZC"] composition-service:requestForm.logToApacheCommons:59 - <d7e8c483> Error: {"errors":[{"code":900124,"source":null,"message":"Values for [_leaseDays] are less restrictive than original values.","systemMessage":"Values for [_leaseDays] are less restrictive than original values.","moreInfoUrl":null}]}
./catalina.out.18-38827-2018-11-30 15:01:56,378 vcac: [component="cafe:shell" priority="ERROR" thread="tomcat-http--5" tenant="<name of tenant>" context="v9gvU8ZC" parent="" token="v9gvU8ZC"] composition-service:requestForm.logToApacheCommons:59 - <d7e8c483> Error: {"errors":[{"code":900124,"source":null,"message":"Values for [_leaseDays] are less restrictive than original values.","systemMessage":"Values for [_leaseDays] are less restrictive than original values.","moreInfoUrl":null}]}
./catalina.out.18:38828:2018-11-30 15:01:56,379 vcac: [component="cafe:shell" priority="ERROR" thread="tomcat-http--5" tenant="<name of tenant>" context="v9gvU8ZC" parent="" token="v9gvU8ZC"] composition-service:requestForm.logToApacheCommons:59 - <d7e8c483> Unable to refresh request form from the server
./catalina.out.18-38829-Values for [_leaseDays] are less restrictive than original values.
./catalina.out.18-38830-Error: {"errors":[{"code":900124,"source":null,"message":"Values for [_leaseDays] are less restrictive than original values.","systemMessage":"Values for [_leaseDays] are less restrictive than original values.","moreInfoUrl":null}]}
As this was for a temporary throw-away blueprint I didn't bother making the necessary changes and testing. I wish this detail was bubbled up to the UI. It would make troubleshooting so much easier.