I am doing some testing with vRO 6.0 and I seem to be having an issue with the vCAC Infrastructure Administration Plugin. Everything seem good in that I can poke around but when I attempt to use the Request a catalog item workflow I am getting this error:
java.util.ConcurrentModificationException when making this command var form = vCACCAFERequestsHelper.getRequestFormForCatalogItem(item)
Anyone seen this before and have an idea how to fix?
Thanks
Steve
Hi Steve,
This is a known issue. There is a technical preview that should fix the problem: https://communities.vmware.com/docs/DOC-28590
Also the issue will be fixed in the 6.2.1 version of the plugin.
Hope this helps.
Best Regards,
Georgi
Did you update the plugin to 6.2? If I recall right, vRO 6.0 is only compatible with the 6.2 plugin, and 5.5.2 is only compatible with 6.1. Also, on a side note, that's not the IaaS plugin... it's the CAFE (referenced just as vCloud Automation Center as how it displays in the Inventory).. Is that all good??
Yes plugin has been updated and everything "appears" good where I can poke around via the Inventory and select objects as properties so everything appears to be functioning properly expect for the request a catalog item and it craps on this command form = vCACCAFERequestsHelper.getRequestFormForCatalogItem(item) where item is the catalog item (Straight from the action). Weird huh?
Hi Steve,
This is a known issue. There is a technical preview that should fix the problem: https://communities.vmware.com/docs/DOC-28590
Also the issue will be fixed in the 6.2.1 version of the plugin.
Hope this helps.
Best Regards,
Georgi
Steve,
By chance did you upgrade a 5.5.2 vCO appliance to vRO 6.0? If so... any other gotchas?
We are going to need to follow this KB (http://kb.vmware.com/kb/2100951) while having "vRA with vRO Cluster Configuration with PostgreSQL" concerns.
We would be doing this in order to deploy the vRA 6.2 plugin because support has a hunch it might fix some of the issues we are having with the 6.1 plugin. (and we all know that usually introduces other issues... heheh... case in point, what you have going on)
Yes I followed that KB and opened the SR. The only issue I had was with the plugin that the link to the TA preview has resolved. I actually have both 5.5.2 cluster and the 6.0 cluster stood up currently while I make sure everything works the way I expect before I switch things out in the load balancer
Any chance you can do me a huge favor?
Can you look at the VCAC plugin inventory on your 5.5.2 VCO instance and see if you have ConsumerResourceOperations (actions within the Actions Folder) listed? And then the same for your 6.0 vRO with 6.2 vRA plugin?
I have been merely trying to ascertain if I have a configuration (maybe permission) issue in my current deployments, or if there is an actual bug... and maybe it is fixed in the 6.2 plugin.
Basically...
1) If you see listed Actions in both... I have a configuration/permission/something issue and upgrading may still be valid, but not specifically for fixing our issue.
2) If you don't see actions in either, it is probably an actual issue and still not fixed.
3) If you see it in the 6.2 plugin but not the 6.1 plugin... then the issue is resolved with an upgrade.
I can pull the ConsumerResourceOperations through the CLI... so I know it isn't an issue in vRA 6.2 itself.
At any rate, I think if you can check that real quick... it would help me a lot.
Here is a picture that I added into my support request so you can get the gist...
Yes I am seeing the actions listed in both versions of vCO. Which account did you configure the plugin to connect to the appliance? If you connected with administrator@vsphere.local, did you give that account entitlement rights to the blueprints and such? I configured my vCAC service account to have all the rights to the blueprints and such and then used that shared account to connect with the plugin
Using an active directory service account. I don't think I have it set up with Business Group Entitlements, however. That may be my issue. Checking.
That did it... You are brilliant, sir.
We have been adding the service account into the business group, but not setting it in the entitlements for the actions. It makes sense in retrospect, just missed it in the configuration.
LOL you should see the bald spot where I was pulling my hair out trying to figure that out. Your right make since once you have it in place but before that, well.....