)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":36710,"name":"Jeong Jiho","display_name":"jiho","email":"jiho.jeong@samsung.com","username":"jihoJeong"},"change_message_id":"ebd5452d1bd80d569d0b9ec1d0be1b1f1e497551","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"359f43d8_5dfa55e3","updated":"2026-11-10 07:25:31.000000000","message":"Thanks for picking this up, and for the clear explanation on the bug.\n\nAs the reporter, this matches what I ran into: the attribute filter drops\nthe requested pool because pools never define a pool_id attribute, and\nthe zone quietly ends up on the default pool. Having the warning in both\npool-scheduler.rst and the devstack README is the right call, since the\ndevstack example is where people copy the combination from, and pointing\nreaders to the single-mechanism configurations in multiple-pools.rst gives\nthem a working alternative rather than just a \"don\u0027t\".\n\nWe have since found a different way to handle our use case on our side,\nso the other half of the bug is no longer an issue for us - happy to see\nthis close it. Thanks again!","commit_id":"6d63efb9ba7a182912256393ee6d622d9b391ba2"}]}