GitHub user tdtmusic2 added a comment to the discussion: Deploying a VM in dedicated domain ends in error
There is clearly something weird here, let me detail the scenarios that I tested so far: host 1, 1 local storage on ssd, tag ssd1, and 1 local storage on hdd, tag hdd1 host 1, 1 local storage on ssd, tag ssd2, and 1 local storage on hdd, tag hdd2 hosts are not identical, one has a 3.2Ghz max freq and the other 2.6Ghz. I created an offer for each storage type on each host, so 4 offerings, only differences between them are the cpu frequency and storage tag. If I deploy a VM on ssd1 it works, but not on ssd2. However, if I remove the ssd2 primary storage and add it back again, deployment works on it, BUT it doesn't work on ssd1 anymore. If **both ssd storages** have the same tag, let's say ssd, then deployment works on both and vms are separeted by the cpu frequency. This would be fine, except for the scenario where you deploy via iso and need to select a disk offering - I guess it would deploy the disk randomly on one of the ssd storages and this is not good. GitHub link: https://github.com/apache/cloudstack/discussions/11080#discussioncomment-13561890 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
