Need help with storage tags.

[SviridoffA]

I have two storage repositories: one for the production workload and a second one created for testing. To prevent virtual machines from being created on the test storage, I tagged both repositories. Consequently, I added the storage tags of the primary repository to all existing VM offerings. When I decided to delete test storage, I discovered that virtual routers had appeared on it. I put the storage into maintenance mode, and currently there are no routers left on it. Afterwards, I tagged all service offerings with the label of the primary storage. The tag applied successfully everywhere, even on those offerings where virtual machines were already running. It applied to all except one: System Offering For Software Router. All virtual routers are now located on the main storage. Nevertheless, I am still receiving an error:

🐱 > update serviceoffering id=9975fbf7-f8e1-4485-9ec9-5a4735e9e2dc storagetags=vmdata
🙈 Error: (HTTP 431, error code 4350) There are active volumes using the disk offering {"name":"System Offering For Software Router","uuid":"97e673db-e77b-4d1a-8d09-b50ce2c1c534"}, and the pool {"name":"hdd","uuid":"56fb2ebd-0dae-471c-8de0-3750e9f9747f"} doesn't have the new tags. The following volumes are using the mentioned disk offering [{"name":"ROOT-549","uuid":"902cf6da-5d50-4077-8bb9-3f2ea22cefae"},{"name":"ROOT-694","uuid":"77e71fb1-e40f-4741-b4df-dd4a06b90f99"},{"name":"ROOT-657","uuid":"37724ce8-350d-49ef-b9db-88a0f1ff9abc"},{"name":"ROOT-848","uuid":"2be54fc0-7a4b-4b4f-92c0-84a93c060f33"},{"name":"ROOT-1074","uuid":"22adf582-2a17-4294-81bc-4b745954f44b"},{"name":"ROOT-1133","uuid":"b63adb2b-6514-47e4-b384-469fc959701d"},{"name":"ROOT-1206","uuid":"944d8003-2246-45ff-bf68-b5929ff80843"},{"name":"ROOT-1208","uuid":"630cd105-9050-442f-a066-c8a3e9e2952d"},{"name":"ROOT-1209","uuid":"abcf79b0-3b8a-4711-ae2d-108cd21e5783"},{"name":"ROOT-1210","uuid":"b0452ff9-291a-4223-821b-b55199c5a3ba"},{"name":"ROOT-1212","uuid":"b5dfa5d2-949d-4e2e-83de-30b1f8a98037"},{"name":"ROOT-1219","uuid":"774e0409-097e-4e0a-b769-1030d51885fb"},{"name":"ROOT-1220","uuid":"92038e01-228f-43d4-a9f0-7417859327b4"},{"name":"ROOT-1224","uuid":"a94f3030-a579-4800-92de-74070da12ea5"},{"name":"ROOT-1225","uuid":"8584f207-473a-4127-a837-f62b603b4244"},{"name":"ROOT-1241","uuid":"de80d199-9008-4c81-90a6-442a3a28c420"},{"name":"ROOT-1242","uuid":"fbac35e9-241a-4b08-b7c0-691bbbc6c8e0"}]. Please first add the new tags to the mentioned storage pools before adding them to the disk offering.

And it won't let me delete this storage either; it says there are volumes associated with it. I tried to recreate these routers, but the newly created routers also run into this problem. Could someone please suggest a way to avoid this issue?

I'm using ACS 4.20.2 and Linstor as primary storages.

[SviridoffA]

Okay, I re-read the error message one more time and decided to temporarily add the vmdata tag to the test storage, and then successfully added the tag to the system offering, after which I deleted it from the test storage, but CloudStack still doesn't let me delete the storage.

[SviridoffA]

Thanks everyone for help, problem has been solved😁😁😁. The problem was that I had one router remaining in the database whose network was in the allocated state (it was marked as being located on the test storage, but since the router hadn't been created yet, I didn't see it). I simply started this router and CloudStack placed it on the main storage. After that, I successfully deleted test storage.