)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":36710,"name":"Jeong Jiho","display_name":"jiho","email":"jiho.jeong@samsung.com","username":"jihoJeong"},"change_message_id":"04572065f529e0dfb8568e02fed6f83db071a3c0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"cdf06dcb_b2914f40","updated":"2026-09-14 06:51:17.000000000","message":"Gentle ping - this one has not had a review yet. The commit message ends with\na question that only the team can answer, so to make replying as cheap as\npossible, any of these three outcomes works for me:\n\n(a) land the four-line change as it is;\n(b) I respin it so that tenant criteria are not applied to pools at all,\n    which fixes the same problem from the other side and also covers pools\n    that already carry a tenant_id;\n(c) close it as wontfix because the pool write API should not be used - in\n    which case I would still like to send a small api-ref patch marking those\n    methods deprecated, since today an operator reading the docs has no way\n    to know.\n\nI have no preference beyond whichever matches the intended pool ownership\nmodel. Happy to do the work in any of the three directions.","commit_id":"5913eb4251bfd4cf7f847c412b8f92183529dda4"},{"author":{"_account_id":31664,"name":"Omer Schwartz","email":"oschwart@redhat.com","username":"oschwart"},"change_message_id":"ba592d562445ae7dce65637336c537b4b63e7dbd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1f555e49_551b3a64","updated":"2026-09-17 10:03:19.000000000","message":"The pool write API (POST /v2/pools and other Pool APIs) are deprecated for quite a while and we do not recommend anyone to use them, today designate-manage pool update is the recommended and supported way to create pools. We should not assume maintenance and review overhead with deprecated stuff.","commit_id":"5913eb4251bfd4cf7f847c412b8f92183529dda4"}]}