Multiple Parents Found

fine
automate

#1

Hello all,

I had an initial MIQ environment with two appliances. I deployed three additional appliances, and created two additional zones; one to hold Azure providers, one to hold vSphere providers, and left the database/web ui appliance in the default zone.

Since doing this, I get multiple parents found whenever I attempt to deploy a VM using a catalog item, in either Azure or vSphere. I’ve run into this previously when someone had moved a template in vSphere, but that isn’t the case here. Full stack trace

Any ideas?


#2

Nevermind, that was the case here, and the zones thing was a red herring. This VMware template issue has been fixed but not yet backported, right?


#3

I am not sure about back-porting. cc @gtanzillo

You can try running tools/delete_ems_metadata_relationships.rb and then refreshing the provider to see if it resolves your issue.


#4

Oh, I didn’t know about that script, my current workaround was to delete the template in MIQ and refresh the provider, which I suppose accomplishes roughly the same thing. Thanks