Renaming Distributed Port Group results in Resolve Network Configuration errors in to do list how do i resolve this?
Could you provide a screenshot of the action Turbonomic is recommending? I can help provide a better answer with that info.
This type of configuration action can occur when a certain entity (host/vm/datastore) has been configured to consume resources from a particular network but does not have access to it. For example a VM configured to be on NetworkX but it's living on a host that can only see NetworkY. So the solution would be to configure the host to also see NetworkX or change the VM's network to be NetworkY.
Are these actions still present for you? After re-reading your question, I'm wondering if a simple "Rediscovery" will resolve this action. Admin Tab > Workflows > Target Configuration > Select Hypervisor target to rediscover > Click "Rediscover Selected"
Let me know if you're still seeing this type of action.
Retrieving data ...