)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"abb94565ee232adc01b5993443495288e8fff842","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"70b7f887_c3a7232a","updated":"2022-03-12 08:39:54.000000000","message":"recheck","commit_id":"72fe42a3f1431fe615f3bdd011abda07ddb4fd58"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"cfebc857e41d351d537739539fc7bb6855d175ec","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ee21bdd1_3392eb89","updated":"2022-03-11 06:10:58.000000000","message":"recheck - hmm, this must have been something else than the race bug. let\u0027s see now again","commit_id":"72fe42a3f1431fe615f3bdd011abda07ddb4fd58"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"b91f643ace54336f0ea95c3b8f995c086999a298","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a6f40f10_3c6b134e","updated":"2022-03-10 18:10:30.000000000","message":"recheck - zuul race bug","commit_id":"72fe42a3f1431fe615f3bdd011abda07ddb4fd58"},{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"dad22efc61ee667e24fc6fd84a6ef5393e0a0e82","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"086b2023_d018ba59","in_reply_to":"27aa860d_dcc305f1","updated":"2022-03-11 13:10:42.000000000","message":"Just to update here for others, it\u0027s an issue happened on zuul side and due to which jobs are not running in stable/yoga:-\n\n\n\u003cfrickler\u003e ykarel: infra-root: it seems that zuul did not receive a reconfiguration event from gerrit for the neutron stable/yoga branch. it seems there were some connections issues with gerrit around the time when the branch was created, that may be related. I have no idea how to trigger the reconfiguration manually or how else to fix this\n\u003cfrickler\u003e https://paste.opendev.org/show/blAUy5NYueY1T0IwsdOd/\n\u003cfungi\u003e frickler: if a branch changes \"behind zuul\u0027s back\" i think it requires a full reconfigure to become aware: https://zuul-ci.org/docs/zuul/latest/operation.html#reconfiguration\n\u003cfrickler\u003e fungi: ah, it evens mentions this scenario as example, great. can I do this right now or should we wait for some off-peak time?\n\u003cfrickler\u003e the docs also aren\u0027t explicit about whether the full-reconfigure would also be done only on one scheduler or all of them\n\u003cfungi\u003e yeah, if it\u0027s not urgent we can do it at a time when a 20-minute pause will be less disruptive\n\u003cfrickler\u003e lajoskatona: ykarel: ^^ I would do this tomorrow morning then, if you agree\n\nSo the issue should clear tomorrow morning after the reconfiguration","commit_id":"72fe42a3f1431fe615f3bdd011abda07ddb4fd58"},{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"f74c48022e92d081f96e5f2f46244039f9b813c8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"27aa860d_dcc305f1","in_reply_to":"ee21bdd1_3392eb89","updated":"2022-03-11 07:51:38.000000000","message":"hmm something wrong as couldn\u0027t even run noop job https://review.opendev.org/c/openstack/neutron/+/833221, would try to reach infra, zuul logs should help in finding what\u0027s wrong.","commit_id":"72fe42a3f1431fe615f3bdd011abda07ddb4fd58"}]}