using host tags AND storage tags, even if they are correctly assigned, deployments fail

> 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 https://github.com/apache/cloudstack/discussions/11080#discussioncomment-13570015_

issue #11083 のデプロイとタグ付けに関する議論、およびリンクされた pull request #13951 と元の議論 #11080 を確認してください。手動のホスト選択がすでに行っているように、自動のホスト選択がホストタグとストレージタグの両方を尊重して正常に動作すれば、作業は完了です。

索引モデルが issue の本文から書いたものです。