)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":25402,"name":"Francesco Pantano","email":"fpantano@redhat.com","username":"fmount"},"change_message_id":"c957f12fda611f44bd29118baadf0d5914236e1b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"0f6a6383_41faab1d","updated":"2026-11-12 16:35:00.000000000","message":"Looks like the custom nodeset confirmed that landing on a different nodepool that provides -v3 solves the deployment issue. \nWe might need to revert the custom zuul nodeset definition and define something globally that might help to keep the current sizing.","commit_id":"797d321c90e6c8d175e9a1e935f068bbd54b5f98"},{"author":{"_account_id":25402,"name":"Francesco Pantano","email":"fpantano@redhat.com","username":"fmount"},"change_message_id":"3c668752cf449a4bb36a624cb8bd02464726c574","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"7cf2691e_9e8a74f1","updated":"2026-11-12 13:21:44.000000000","message":"Umbrella (v21) needs x86-64-v3: \u0027ceph --version\u0027 aborts\nwith \"Fatal glibc error: CPU does not support x86-64-v3\" [1].\nSo I\u0027m pinning the jobs to temporarily run on the 16GB labels (not offered by\nrax-base) via local nodesets in .zuul.yaml, purely to validate the bump on\nv3-capable hardware.\nOnce we validate it we can revert it and discuss about providing a v3-capable 8GB label nodepool [2].\n\n[1] https://docs.ceph.com/en/latest/start/os-recommendations/#umbrella-container-base-image\n[2] https://opendev.org/opendev/zuul-providers/src/branch/master/zuul.d/providers.yaml","commit_id":"797d321c90e6c8d175e9a1e935f068bbd54b5f98"}]}