)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"bbecb4a1982a5579134ff2e627a0c8319a9b7527","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"89d12b72_0ca37715","updated":"2025-03-05 17:19:47.000000000","message":"WIP because while I expect this new change to fix the zuul_return error it doesn\u0027t address the other concern I had.\n\nSpecifically infra-prod-bootstrap-bridge and infra-prod-service-bridge started at the same time. This was meant to be prevented by having infra-prod-base (parent for infra-prod-service-*) hard depend on infra-prod-bootstrap-bridge which meant that they would wait for the parent to pause or exit before starting. It almost seems like defining a dependency in a parent change isn\u0027t inherited by the child change?\n\nYou can see this happening if you look at the buildset: https://zuul.opendev.org/t/openstack/buildset/0f0ab7c1936640eebefcdc1e9bd46bc9 and the two jobs in question: https://zuul.opendev.org/t/openstack/build/ad37df93c0064983bd30c501d792be96 https://zuul.opendev.org/t/openstack/build/f85e6c92785d485c9dd50814d4a60dd0 Note the start times.","commit_id":"566cb2cccb0b7b9289b6f3d5cd25619bafaaf663"}],"playbooks/zuul/run-production-bootstrap-bridge.yaml":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"bbecb4a1982a5579134ff2e627a0c8319a9b7527","unresolved":true,"context_lines":[{"line_number":5,"context_line":"- import_playbook: ../bootstrap-bridge.yaml"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"- hosts: localhost"},{"line_number":8,"context_line":"  tasks:"},{"line_number":9,"context_line":"    - name: Wait for child jobs"},{"line_number":10,"context_line":"      zuul_return:"},{"line_number":11,"context_line":"        data:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5f551441_52ca332b","line":8,"updated":"2025-03-05 17:19:47.000000000","message":"This should be the only new code so far when compared to the original attempt.","commit_id":"566cb2cccb0b7b9289b6f3d5cd25619bafaaf663"}],"zuul.d/project.yaml":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"b6cc2dbf4fd998dd8602332f040fe4412ff79e97","unresolved":true,"context_lines":[{"line_number":340,"context_line":"        # NOTE: infra-prod-* jobs have a hierarchy below that ensure"},{"line_number":341,"context_line":"        # they can run in parallel.  We are deliberately keeping their"},{"line_number":342,"context_line":"        # dependencies here rather than job definitions to help keep"},{"line_number":343,"context_line":"        # these relationships clear. The one exception to this is the"},{"line_number":344,"context_line":"        # base infra-prod-playbook job depends on infra-prod-bootstrap-bridge."},{"line_number":345,"context_line":"        # We make this exception because it is vital that bootstrap-bridge"},{"line_number":346,"context_line":"        # run before everything else always."},{"line_number":347,"context_line":""},{"line_number":348,"context_line":"        # This installs the ansible on bridge that all the infra-prod"},{"line_number":349,"context_line":"        # jobs will run with.  Note the jobs use this ansible to then"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"ea484aa7_b9ae1171","line":346,"range":{"start_line":343,"start_character":37,"end_line":346,"end_character":44},"updated":"2025-03-05 18:18:59.000000000","message":"This comment block is no longer accurate. But we can clean that up later if we want.","commit_id":"f002f29130d5249f200c93d493beaddc65d3bcdc"}]}