Maybe my google foo is broken, but I couldn’t see any mention of this in VMware’s KB library. I’m trying to find out if it’s also an issue in vRA 6.2 too.
Edit 14/05/2015: I’m reliably informed that this is fixed in 6.2.
So, what’s the problem?
Well, I was demonstrating how it was possible to change the description of a VM in vCAC via the “Edit” resource action and how it would also result in the vCenter VM being updated.
So, with the description added, I hit Submit. The description is added to the Virtual Machine in vCAC and also vCenter. I then went to to demonstrate a custom action that executes a vRO workflow and was surprised when it failed and complained about the identity of the network being used.
A brief bit of head-scratching later, and I discovered that vCAC believed the VM to have no network interface:
The VM’s properties confirmed, that as far as vCAC was concerned, this VM was not connected to any network! However, looking at vCenter, the story was very different:
For anyone familiar with vCAC, the solution is easy. And, in fact, vCAC will fix the issue itself in under 24 hours. Forcing vCAC to refresh the vCenter inventory clears up the discrepancy:
Clearly an odd “feature” of the vCAC portal and I probably wouldn’t even have noticed it but for using the same VM for a particular resource action that needed the VM’s network properties.