Repository navigation
using host tags AND storage tags, even if they are correctly assigned, deployments fail #11083
Description
ok, when a deployment in a dedicated resource fails in general other resources will be queried to see if deployment is possible there. So the tagging problem is not specifc to the dedication (I think).
Ok, so then what would be the proper way to solve this issue? At the moment I found a working setup like this: both ssd storages, from both hosts, have the same tag, ssd, and both hdd storages have hdd. Offerings are created with storage tag. If I deploy a vm AND choose the host manually, it uses the correct storage, depending on the offering that I choose. This is ok, but I cannot find a way to have ACS choose the host automatically - if I use host tags AND storage tags, even if they are correctly assigned, all deployments fail.
Originally posted by @tdtmusic2 in #11080 (reply in thread)
Activity
tdtmusic2 commentedon Jun 25, 2025
Please note that it's about LOCAL storage. 2 hosts, each host with 2 local storages, ssd & hdd. ACS should deploy vms based on the host tags AND storage tags that are defined in the offerings (ex. I want a vm on host 1, hdd storage, or on host 2, ssd storage).
DaanHoogland commentedon Jul 7, 2025
@tdtmusic2 what versions are you running (ACS/host-OS/MS-OS etc)
tdtmusic2 commentedon Jul 7, 2025
ACS 4.20.1.0, host OS Almalinux 9.5 on all hosts and manager.
rbaweja commentedon Jul 20, 2025
i am also facing the same issue, with 4.20.0 on ubuntu, local storage... nothign works with tags either host / storage bith have issues... tried creating multiple offerings with dfferent parameters but still the error -
No destination found for a deployment for VM instance {"id":1549,"instanceName":"i-2-1549-VM","type":"User","uuid":"10d6da03-7daa-45cb-a33e-828c1bdf02b8"}
HeinzM commentedon Nov 3, 2025
I can confirm the same behavior for version 4.21.
After adding a second zone, nothing can be deployed in the 2nd zone.
"No destination found for a deployment for VM instance {"id":691,"instanceName":"i-4-691-VM","state":"Stopped","type":"User","uuid":"dbc0cce5-909c-4c8f-ba2a-556e9509ccf5"}"}
First identical zone but with different ip-addresses is working.