GitHub user tdtmusic2 added a comment to the discussion: Deploying a VM in dedicated domain ends in error
Some more info here. If both the 2 hosts and their primary storages have tags (to control where vms are deployed), deployment fails no matter what I do, even if the tags are correct on the offering. If I remove the host tag and just leave the storage tag on the offering, deployment works on 1st host. On the second host it fails, however I think this is a different matter, I saw this error somewhere in the log: `Unable to add bridge br2 port vnet13: Operation not supported","wait":"0","bypassHostMaintenance":"false"}}] }` What I don't understand is why it doesn't work with host tags, seems a good way to filter the destinations. GitHub link: https://github.com/apache/cloudstack/discussions/11080#discussioncomment-13560285 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
