vRA 8 - Bug with tagged resource pools

[bdamian]

I've found a new bug in vRealize Automation 8.0.1.

I've tagged a Resource Pool called "vra8produccion" on a Cloud Zone with "env:prod", then I've deployed an instance selecting env:prod and the VM was created on a wrong Resource Pool.

Screenshot with tagged RP

Screenshot from vCenter

I don't understand why vRA put the VM in the wrong RP.

Any ideas?

[stevedrummond]

What does the provisioning diagram look like? It will show what decisions were made on the placement of the VM.

[bdamian]

It shows me this:

I will delete the deployment and try again.

[bdamian]

The provisioning diagram show the correct information, but it deploy the VMs in the incorrect Resource Pool. I hope this kind of things will be fixed soon enough.

[stevedrummond]

Sounds like a bug. You will definitely need to raise a SR if you have any hope it will be fixed.

[bdamian]

Is there any easy way to raise a SR? I've always put it here...