)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"0520a7ec9e09f91994ea49196af4973ca0ffd687","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a0bdcea8_d2460676","updated":"2026-10-16 06:57:36.000000000","message":"Nice! Thank you!","commit_id":"d46797712c5561d1b10f4deafd327bd4654f09d4"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"aecb2595c960c7ecffed56def666b8220a797d6f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"35b78a0b_ba810936","updated":"2026-10-14 08:06:20.000000000","message":"recheck","commit_id":"d46797712c5561d1b10f4deafd327bd4654f09d4"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"ea42235d1d5e83fe399ea4a29b3c21c5cd78bc88","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8ee36dac_0a1a3be7","updated":"2026-10-13 10:06:13.000000000","message":"recheck \"Fatal glibc error: CPU does not support x86-64-v3\"","commit_id":"d46797712c5561d1b10f4deafd327bd4654f09d4"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"96f2327fa2a2f1813227c0051c6b51e243db88bb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b2c23884_46130011","in_reply_to":"89ca8a48_fa912322","updated":"2026-10-13 10:20:44.000000000","message":"I faced the same error a few days ago and recheck \"resolved\" the problem at that time. I suspect the issue is caused by sg-core using c10s as its base image. AFAIK c10s removed support for old cpu models (aka x86-64-v2) and some of our cloud provides in CI infra provides only that old cpu model. In case we face this problem consistently we likely have to consult CI team about a way to avoid using such cloud providers.","commit_id":"d46797712c5561d1b10f4deafd327bd4654f09d4"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"e13d871b6812fa2afd92d0c525cee40220a9f5a0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"89ca8a48_fa912322","in_reply_to":"8ee36dac_0a1a3be7","updated":"2026-10-13 10:17:08.000000000","message":"It seems to be related with sg-core changing image, we are investigating.","commit_id":"d46797712c5561d1b10f4deafd327bd4654f09d4"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"b6d352a1219ec5c501e3988ab2296c5482689df6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"65a4a47c_da0a9078","in_reply_to":"b2c23884_46130011","updated":"2026-10-13 10:36:55.000000000","message":"We reached the same conclusion. As there is nothing we can do to replace CI old hardware or to change the centos10 decision about deprecating it, we are going to build an \":ubi9-latest\" image to keep the CI running on the upstream infrastructure and keep it running for the time being.","commit_id":"d46797712c5561d1b10f4deafd327bd4654f09d4"}]}