all:
  children:
    zuul_unreachable:
      hosts: {}
  hosts:
    debian-bookworm:
      ansible_connection: ssh
      ansible_host: 2a13:1a81:8000:3124:f816:3eff:feff:8259
      ansible_port: 22
      ansible_python_interpreter: auto
      ansible_user: zuul
      nodepool:
        az: nova
        cloud: regiocloud-a-ci
        external_id: a0c7ed2c-9c3b-4911-b067-471affd2d16c
        host_id: 82101243836454d7401d5893feae9e2c5df7cc291646d8a99b33b53b
        interface_ip: 2a13:1a81:8000:3124:f816:3eff:feff:8259
        label: debian-bookworm
        node_properties: {}
        private_ipv4: 10.128.7.169
        private_ipv6: null
        provider: regiocloud-a
        public_ipv4: 81.163.193.162
        public_ipv6: 2a13:1a81:8000:3124:f816:3eff:feff:8259
        region: null
        slot: null
  vars:
    zuul:
      _inheritance_path:
      - '<Job base explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: osism/zuul-config/zuul.d/jobs.yaml@main#2>'
      - '<Job yamllint explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: osism/zuul-jobs/.zuul.yaml@main#59>'
      - '<Job yamllint explicit: None implied: None source: osism/release/.zuul.yaml@main#14>'
      ansible_version: '9'
      attempts: 1
      branch: main
      build: e9f11a01c67e4e17b4b7644f21228218
      build_refs:
      - branch: main
        change: '2632'
        change_message: "latest: cap ansible-core below 2.19\n\n## Problem\n\nThe
          `current` and `next` testbed lanes have TIMED_OUT at the full 4.5 h Zuul\ntimeout
          every night since 2026-07-25. kolla-ansible's `common` role fails with\n`ansible_facts`
          empty and `os_family` undefined, so `kolla_toolbox` is never\ndeployed and
          the non-aborting celery chain polls until Zuul kills the build.\n\nCause:
          `latest/base.yml` moved `ansible_core_version` to 2.19.11. ansible-core\n2.19
          namespaces fact-cache entries with an `s1_` key prefix, so\n`osism-ansible:latest`
          writes into a keyspace `kolla-ansible:2025.1` (2.18.18)\nand `ceph-ansible:reef`
          (2.16.19) cannot read \u2014 and they share one Redis fact\ncache. kolla
          has no fallback, because OSISM splits kolla's `site.yml` and the\nsplitter
          drops the `gather-facts.yml` import while forcing `gather_facts: false`.\n\n`base.yml`
          cannot cross 2.19 while it shares a cache with containers that cannot\nfollow:
          kolla-ansible 2025.1 requires `ansible-core>=2.17,<2.19`, and\nceph-ansible
          caps `<2.17` on every branch including `main`. Independently,\n`cloud.common`
          5.0.0 declares `requires_ansible >=2.15.0,<2.19`, so the 2.19 pin\nalso
          sits outside the declared support range of a collection this file pins.\n\n##
          Change\n\n- `latest/base.yml`: `ansible_core_version` 2.19.11 -> 2.18.18.
          All 22\n  collections pinned in this file were checked against Galaxy `requires_ansible`\n
          \ \u2014 none needs `>=2.19`, so 2.18.18 satisfies every one.\n- `latest/base.yml`:
          `ansible_version` 12.2.0 -> 11.10.0. Cosmetic only; the\n  field is not
          installed for any live build. Reverted so the pair is not\n  misleading.\n-
          `.github/renovate.json`: disable major and minor `ansible` / `ansible-core`\n
          \ updates for `latest/base.yml`. Blocking minor is the point \u2014 for
          ansible-core,\n  2.18 -> 2.19 is itself a minor bump. The per-release files
          already carry this\n  policy; `base.yml` was the only ansible pin left floating.
          Appended last so the\n  existing `groupName: \"ansible\"` rule keeps applying
          for patch updates.\n\n## Verification\n\nReaches CI at the next nightly
          `osism-ansible:latest` rebuild, then the\nfollowing midnight run. Note a
          green run confirms the trigger, not the\nmechanism \u2014 the mechanism
          is already confirmed separately, by reading the 2.19\n`PluginInterposer`
          source and by reproducing the failure outside the testbed\nwith two ansible-core
          venvs against a local Redis.\n\n## Lifting the cap\n\nNot before kolla-ansible
          can gather its own facts. Splitting the shared fact\ncache first would make
          things worse rather than better: kolla would get an empty\ncache and still
          no gather step, failing every host instead of only those the\nceph-ansible
          OSD play happens to rescue.\n\n## Related\n\nFull analysis, including the
          reproduction and the cost of holding the cap:\n\n- osism/issues#1420\n\nBlocked
          while this cap holds, since `ansible` 14 requires `ansible-core~=2.21.2`:\n\n-
          osism/release#2623\n\n\U0001F916 Generated with [Claude Code](https://claude.com/claude-code)\n"
        change_url: https://github.com/osism/release/pull/2632
        commit_id: f3ee996d0b36eab208d02265eec2d1b0a16ab7a5
        patchset: f3ee996d0b36eab208d02265eec2d1b0a16ab7a5
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/release
          name: osism/release
          short_name: release
        src_dir: src/github.com/osism/release
        topic: null
      buildset: 585fa34354f1401596ab68b3b95e029d
      buildset_refs:
      - branch: main
        change: '2632'
        change_message: "latest: cap ansible-core below 2.19\n\n## Problem\n\nThe
          `current` and `next` testbed lanes have TIMED_OUT at the full 4.5 h Zuul\ntimeout
          every night since 2026-07-25. kolla-ansible's `common` role fails with\n`ansible_facts`
          empty and `os_family` undefined, so `kolla_toolbox` is never\ndeployed and
          the non-aborting celery chain polls until Zuul kills the build.\n\nCause:
          `latest/base.yml` moved `ansible_core_version` to 2.19.11. ansible-core\n2.19
          namespaces fact-cache entries with an `s1_` key prefix, so\n`osism-ansible:latest`
          writes into a keyspace `kolla-ansible:2025.1` (2.18.18)\nand `ceph-ansible:reef`
          (2.16.19) cannot read \u2014 and they share one Redis fact\ncache. kolla
          has no fallback, because OSISM splits kolla's `site.yml` and the\nsplitter
          drops the `gather-facts.yml` import while forcing `gather_facts: false`.\n\n`base.yml`
          cannot cross 2.19 while it shares a cache with containers that cannot\nfollow:
          kolla-ansible 2025.1 requires `ansible-core>=2.17,<2.19`, and\nceph-ansible
          caps `<2.17` on every branch including `main`. Independently,\n`cloud.common`
          5.0.0 declares `requires_ansible >=2.15.0,<2.19`, so the 2.19 pin\nalso
          sits outside the declared support range of a collection this file pins.\n\n##
          Change\n\n- `latest/base.yml`: `ansible_core_version` 2.19.11 -> 2.18.18.
          All 22\n  collections pinned in this file were checked against Galaxy `requires_ansible`\n
          \ \u2014 none needs `>=2.19`, so 2.18.18 satisfies every one.\n- `latest/base.yml`:
          `ansible_version` 12.2.0 -> 11.10.0. Cosmetic only; the\n  field is not
          installed for any live build. Reverted so the pair is not\n  misleading.\n-
          `.github/renovate.json`: disable major and minor `ansible` / `ansible-core`\n
          \ updates for `latest/base.yml`. Blocking minor is the point \u2014 for
          ansible-core,\n  2.18 -> 2.19 is itself a minor bump. The per-release files
          already carry this\n  policy; `base.yml` was the only ansible pin left floating.
          Appended last so the\n  existing `groupName: \"ansible\"` rule keeps applying
          for patch updates.\n\n## Verification\n\nReaches CI at the next nightly
          `osism-ansible:latest` rebuild, then the\nfollowing midnight run. Note a
          green run confirms the trigger, not the\nmechanism \u2014 the mechanism
          is already confirmed separately, by reading the 2.19\n`PluginInterposer`
          source and by reproducing the failure outside the testbed\nwith two ansible-core
          venvs against a local Redis.\n\n## Lifting the cap\n\nNot before kolla-ansible
          can gather its own facts. Splitting the shared fact\ncache first would make
          things worse rather than better: kolla would get an empty\ncache and still
          no gather step, failing every host instead of only those the\nceph-ansible
          OSD play happens to rescue.\n\n## Related\n\nFull analysis, including the
          reproduction and the cost of holding the cap:\n\n- osism/issues#1420\n\nBlocked
          while this cap holds, since `ansible` 14 requires `ansible-core~=2.21.2`:\n\n-
          osism/release#2623\n\n\U0001F916 Generated with [Claude Code](https://claude.com/claude-code)\n"
        change_url: https://github.com/osism/release/pull/2632
        commit_id: f3ee996d0b36eab208d02265eec2d1b0a16ab7a5
        patchset: f3ee996d0b36eab208d02265eec2d1b0a16ab7a5
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/release
          name: osism/release
          short_name: release
        src_dir: src/github.com/osism/release
        topic: null
      change: '2632'
      change_message: "latest: cap ansible-core below 2.19\n\n## Problem\n\nThe `current`
        and `next` testbed lanes have TIMED_OUT at the full 4.5 h Zuul\ntimeout every
        night since 2026-07-25. kolla-ansible's `common` role fails with\n`ansible_facts`
        empty and `os_family` undefined, so `kolla_toolbox` is never\ndeployed and
        the non-aborting celery chain polls until Zuul kills the build.\n\nCause:
        `latest/base.yml` moved `ansible_core_version` to 2.19.11. ansible-core\n2.19
        namespaces fact-cache entries with an `s1_` key prefix, so\n`osism-ansible:latest`
        writes into a keyspace `kolla-ansible:2025.1` (2.18.18)\nand `ceph-ansible:reef`
        (2.16.19) cannot read \u2014 and they share one Redis fact\ncache. kolla has
        no fallback, because OSISM splits kolla's `site.yml` and the\nsplitter drops
        the `gather-facts.yml` import while forcing `gather_facts: false`.\n\n`base.yml`
        cannot cross 2.19 while it shares a cache with containers that cannot\nfollow:
        kolla-ansible 2025.1 requires `ansible-core>=2.17,<2.19`, and\nceph-ansible
        caps `<2.17` on every branch including `main`. Independently,\n`cloud.common`
        5.0.0 declares `requires_ansible >=2.15.0,<2.19`, so the 2.19 pin\nalso sits
        outside the declared support range of a collection this file pins.\n\n## Change\n\n-
        `latest/base.yml`: `ansible_core_version` 2.19.11 -> 2.18.18. All 22\n  collections
        pinned in this file were checked against Galaxy `requires_ansible`\n  \u2014
        none needs `>=2.19`, so 2.18.18 satisfies every one.\n- `latest/base.yml`:
        `ansible_version` 12.2.0 -> 11.10.0. Cosmetic only; the\n  field is not installed
        for any live build. Reverted so the pair is not\n  misleading.\n- `.github/renovate.json`:
        disable major and minor `ansible` / `ansible-core`\n  updates for `latest/base.yml`.
        Blocking minor is the point \u2014 for ansible-core,\n  2.18 -> 2.19 is itself
        a minor bump. The per-release files already carry this\n  policy; `base.yml`
        was the only ansible pin left floating. Appended last so the\n  existing `groupName:
        \"ansible\"` rule keeps applying for patch updates.\n\n## Verification\n\nReaches
        CI at the next nightly `osism-ansible:latest` rebuild, then the\nfollowing
        midnight run. Note a green run confirms the trigger, not the\nmechanism \u2014
        the mechanism is already confirmed separately, by reading the 2.19\n`PluginInterposer`
        source and by reproducing the failure outside the testbed\nwith two ansible-core
        venvs against a local Redis.\n\n## Lifting the cap\n\nNot before kolla-ansible
        can gather its own facts. Splitting the shared fact\ncache first would make
        things worse rather than better: kolla would get an empty\ncache and still
        no gather step, failing every host instead of only those the\nceph-ansible
        OSD play happens to rescue.\n\n## Related\n\nFull analysis, including the
        reproduction and the cost of holding the cap:\n\n- osism/issues#1420\n\nBlocked
        while this cap holds, since `ansible` 14 requires `ansible-core~=2.21.2`:\n\n-
        osism/release#2623\n\n\U0001F916 Generated with [Claude Code](https://claude.com/claude-code)\n"
      change_url: https://github.com/osism/release/pull/2632
      child_jobs: []
      commit_id: f3ee996d0b36eab208d02265eec2d1b0a16ab7a5
      event_id: 097a89a0-8a48-11f1-8c1b-5ccae61fd9c7
      executor:
        hostname: 521e9411259a
        inventory_file: /var/lib/zuul/builds/e9f11a01c67e4e17b4b7644f21228218/ansible/inventory.yaml
        log_root: /var/lib/zuul/builds/e9f11a01c67e4e17b4b7644f21228218/work/logs
        result_data_file: /var/lib/zuul/builds/e9f11a01c67e4e17b4b7644f21228218/work/results.json
        src_root: /var/lib/zuul/builds/e9f11a01c67e4e17b4b7644f21228218/work/src
        work_root: /var/lib/zuul/builds/e9f11a01c67e4e17b4b7644f21228218/work
      include_vars: []
      items:
      - branch: main
        change: '2632'
        change_message: "latest: cap ansible-core below 2.19\n\n## Problem\n\nThe
          `current` and `next` testbed lanes have TIMED_OUT at the full 4.5 h Zuul\ntimeout
          every night since 2026-07-25. kolla-ansible's `common` role fails with\n`ansible_facts`
          empty and `os_family` undefined, so `kolla_toolbox` is never\ndeployed and
          the non-aborting celery chain polls until Zuul kills the build.\n\nCause:
          `latest/base.yml` moved `ansible_core_version` to 2.19.11. ansible-core\n2.19
          namespaces fact-cache entries with an `s1_` key prefix, so\n`osism-ansible:latest`
          writes into a keyspace `kolla-ansible:2025.1` (2.18.18)\nand `ceph-ansible:reef`
          (2.16.19) cannot read \u2014 and they share one Redis fact\ncache. kolla
          has no fallback, because OSISM splits kolla's `site.yml` and the\nsplitter
          drops the `gather-facts.yml` import while forcing `gather_facts: false`.\n\n`base.yml`
          cannot cross 2.19 while it shares a cache with containers that cannot\nfollow:
          kolla-ansible 2025.1 requires `ansible-core>=2.17,<2.19`, and\nceph-ansible
          caps `<2.17` on every branch including `main`. Independently,\n`cloud.common`
          5.0.0 declares `requires_ansible >=2.15.0,<2.19`, so the 2.19 pin\nalso
          sits outside the declared support range of a collection this file pins.\n\n##
          Change\n\n- `latest/base.yml`: `ansible_core_version` 2.19.11 -> 2.18.18.
          All 22\n  collections pinned in this file were checked against Galaxy `requires_ansible`\n
          \ \u2014 none needs `>=2.19`, so 2.18.18 satisfies every one.\n- `latest/base.yml`:
          `ansible_version` 12.2.0 -> 11.10.0. Cosmetic only; the\n  field is not
          installed for any live build. Reverted so the pair is not\n  misleading.\n-
          `.github/renovate.json`: disable major and minor `ansible` / `ansible-core`\n
          \ updates for `latest/base.yml`. Blocking minor is the point \u2014 for
          ansible-core,\n  2.18 -> 2.19 is itself a minor bump. The per-release files
          already carry this\n  policy; `base.yml` was the only ansible pin left floating.
          Appended last so the\n  existing `groupName: \"ansible\"` rule keeps applying
          for patch updates.\n\n## Verification\n\nReaches CI at the next nightly
          `osism-ansible:latest` rebuild, then the\nfollowing midnight run. Note a
          green run confirms the trigger, not the\nmechanism \u2014 the mechanism
          is already confirmed separately, by reading the 2.19\n`PluginInterposer`
          source and by reproducing the failure outside the testbed\nwith two ansible-core
          venvs against a local Redis.\n\n## Lifting the cap\n\nNot before kolla-ansible
          can gather its own facts. Splitting the shared fact\ncache first would make
          things worse rather than better: kolla would get an empty\ncache and still
          no gather step, failing every host instead of only those the\nceph-ansible
          OSD play happens to rescue.\n\n## Related\n\nFull analysis, including the
          reproduction and the cost of holding the cap:\n\n- osism/issues#1420\n\nBlocked
          while this cap holds, since `ansible` 14 requires `ansible-core~=2.21.2`:\n\n-
          osism/release#2623\n\n\U0001F916 Generated with [Claude Code](https://claude.com/claude-code)\n"
        change_url: https://github.com/osism/release/pull/2632
        commit_id: f3ee996d0b36eab208d02265eec2d1b0a16ab7a5
        patchset: f3ee996d0b36eab208d02265eec2d1b0a16ab7a5
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/release
          name: osism/release
          short_name: release
          src_dir: src/github.com/osism/release
        topic: null
      job: yamllint
      jobtags: []
      max_attempts: 3
      message: bGF0ZXN0OiBjYXAgYW5zaWJsZS1jb3JlIGJlbG93IDIuMTkKCiMjIFByb2JsZW0KClRoZSBgY3VycmVudGAgYW5kIGBuZXh0YCB0ZXN0YmVkIGxhbmVzIGhhdmUgVElNRURfT1VUIGF0IHRoZSBmdWxsIDQuNSBoIFp1dWwKdGltZW91dCBldmVyeSBuaWdodCBzaW5jZSAyMDI2LTA3LTI1LiBrb2xsYS1hbnNpYmxlJ3MgYGNvbW1vbmAgcm9sZSBmYWlscyB3aXRoCmBhbnNpYmxlX2ZhY3RzYCBlbXB0eSBhbmQgYG9zX2ZhbWlseWAgdW5kZWZpbmVkLCBzbyBga29sbGFfdG9vbGJveGAgaXMgbmV2ZXIKZGVwbG95ZWQgYW5kIHRoZSBub24tYWJvcnRpbmcgY2VsZXJ5IGNoYWluIHBvbGxzIHVudGlsIFp1dWwga2lsbHMgdGhlIGJ1aWxkLgoKQ2F1c2U6IGBsYXRlc3QvYmFzZS55bWxgIG1vdmVkIGBhbnNpYmxlX2NvcmVfdmVyc2lvbmAgdG8gMi4xOS4xMS4gYW5zaWJsZS1jb3JlCjIuMTkgbmFtZXNwYWNlcyBmYWN0LWNhY2hlIGVudHJpZXMgd2l0aCBhbiBgczFfYCBrZXkgcHJlZml4LCBzbwpgb3Npc20tYW5zaWJsZTpsYXRlc3RgIHdyaXRlcyBpbnRvIGEga2V5c3BhY2UgYGtvbGxhLWFuc2libGU6MjAyNS4xYCAoMi4xOC4xOCkKYW5kIGBjZXBoLWFuc2libGU6cmVlZmAgKDIuMTYuMTkpIGNhbm5vdCByZWFkIOKAlCBhbmQgdGhleSBzaGFyZSBvbmUgUmVkaXMgZmFjdApjYWNoZS4ga29sbGEgaGFzIG5vIGZhbGxiYWNrLCBiZWNhdXNlIE9TSVNNIHNwbGl0cyBrb2xsYSdzIGBzaXRlLnltbGAgYW5kIHRoZQpzcGxpdHRlciBkcm9wcyB0aGUgYGdhdGhlci1mYWN0cy55bWxgIGltcG9ydCB3aGlsZSBmb3JjaW5nIGBnYXRoZXJfZmFjdHM6IGZhbHNlYC4KCmBiYXNlLnltbGAgY2Fubm90IGNyb3NzIDIuMTkgd2hpbGUgaXQgc2hhcmVzIGEgY2FjaGUgd2l0aCBjb250YWluZXJzIHRoYXQgY2Fubm90CmZvbGxvdzoga29sbGEtYW5zaWJsZSAyMDI1LjEgcmVxdWlyZXMgYGFuc2libGUtY29yZT49Mi4xNyw8Mi4xOWAsIGFuZApjZXBoLWFuc2libGUgY2FwcyBgPDIuMTdgIG9uIGV2ZXJ5IGJyYW5jaCBpbmNsdWRpbmcgYG1haW5gLiBJbmRlcGVuZGVudGx5LApgY2xvdWQuY29tbW9uYCA1LjAuMCBkZWNsYXJlcyBgcmVxdWlyZXNfYW5zaWJsZSA+PTIuMTUuMCw8Mi4xOWAsIHNvIHRoZSAyLjE5IHBpbgphbHNvIHNpdHMgb3V0c2lkZSB0aGUgZGVjbGFyZWQgc3VwcG9ydCByYW5nZSBvZiBhIGNvbGxlY3Rpb24gdGhpcyBmaWxlIHBpbnMuCgojIyBDaGFuZ2UKCi0gYGxhdGVzdC9iYXNlLnltbGA6IGBhbnNpYmxlX2NvcmVfdmVyc2lvbmAgMi4xOS4xMSAtPiAyLjE4LjE4LiBBbGwgMjIKICBjb2xsZWN0aW9ucyBwaW5uZWQgaW4gdGhpcyBmaWxlIHdlcmUgY2hlY2tlZCBhZ2FpbnN0IEdhbGF4eSBgcmVxdWlyZXNfYW5zaWJsZWAKICDigJQgbm9uZSBuZWVkcyBgPj0yLjE5YCwgc28gMi4xOC4xOCBzYXRpc2ZpZXMgZXZlcnkgb25lLgotIGBsYXRlc3QvYmFzZS55bWxgOiBgYW5zaWJsZV92ZXJzaW9uYCAxMi4yLjAgLT4gMTEuMTAuMC4gQ29zbWV0aWMgb25seTsgdGhlCiAgZmllbGQgaXMgbm90IGluc3RhbGxlZCBmb3IgYW55IGxpdmUgYnVpbGQuIFJldmVydGVkIHNvIHRoZSBwYWlyIGlzIG5vdAogIG1pc2xlYWRpbmcuCi0gYC5naXRodWIvcmVub3ZhdGUuanNvbmA6IGRpc2FibGUgbWFqb3IgYW5kIG1pbm9yIGBhbnNpYmxlYCAvIGBhbnNpYmxlLWNvcmVgCiAgdXBkYXRlcyBmb3IgYGxhdGVzdC9iYXNlLnltbGAuIEJsb2NraW5nIG1pbm9yIGlzIHRoZSBwb2ludCDigJQgZm9yIGFuc2libGUtY29yZSwKICAyLjE4IC0+IDIuMTkgaXMgaXRzZWxmIGEgbWlub3IgYnVtcC4gVGhlIHBlci1yZWxlYXNlIGZpbGVzIGFscmVhZHkgY2FycnkgdGhpcwogIHBvbGljeTsgYGJhc2UueW1sYCB3YXMgdGhlIG9ubHkgYW5zaWJsZSBwaW4gbGVmdCBmbG9hdGluZy4gQXBwZW5kZWQgbGFzdCBzbyB0aGUKICBleGlzdGluZyBgZ3JvdXBOYW1lOiAiYW5zaWJsZSJgIHJ1bGUga2VlcHMgYXBwbHlpbmcgZm9yIHBhdGNoIHVwZGF0ZXMuCgojIyBWZXJpZmljYXRpb24KClJlYWNoZXMgQ0kgYXQgdGhlIG5leHQgbmlnaHRseSBgb3Npc20tYW5zaWJsZTpsYXRlc3RgIHJlYnVpbGQsIHRoZW4gdGhlCmZvbGxvd2luZyBtaWRuaWdodCBydW4uIE5vdGUgYSBncmVlbiBydW4gY29uZmlybXMgdGhlIHRyaWdnZXIsIG5vdCB0aGUKbWVjaGFuaXNtIOKAlCB0aGUgbWVjaGFuaXNtIGlzIGFscmVhZHkgY29uZmlybWVkIHNlcGFyYXRlbHksIGJ5IHJlYWRpbmcgdGhlIDIuMTkKYFBsdWdpbkludGVycG9zZXJgIHNvdXJjZSBhbmQgYnkgcmVwcm9kdWNpbmcgdGhlIGZhaWx1cmUgb3V0c2lkZSB0aGUgdGVzdGJlZAp3aXRoIHR3byBhbnNpYmxlLWNvcmUgdmVudnMgYWdhaW5zdCBhIGxvY2FsIFJlZGlzLgoKIyMgTGlmdGluZyB0aGUgY2FwCgpOb3QgYmVmb3JlIGtvbGxhLWFuc2libGUgY2FuIGdhdGhlciBpdHMgb3duIGZhY3RzLiBTcGxpdHRpbmcgdGhlIHNoYXJlZCBmYWN0CmNhY2hlIGZpcnN0IHdvdWxkIG1ha2UgdGhpbmdzIHdvcnNlIHJhdGhlciB0aGFuIGJldHRlcjoga29sbGEgd291bGQgZ2V0IGFuIGVtcHR5CmNhY2hlIGFuZCBzdGlsbCBubyBnYXRoZXIgc3RlcCwgZmFpbGluZyBldmVyeSBob3N0IGluc3RlYWQgb2Ygb25seSB0aG9zZSB0aGUKY2VwaC1hbnNpYmxlIE9TRCBwbGF5IGhhcHBlbnMgdG8gcmVzY3VlLgoKIyMgUmVsYXRlZAoKRnVsbCBhbmFseXNpcywgaW5jbHVkaW5nIHRoZSByZXByb2R1Y3Rpb24gYW5kIHRoZSBjb3N0IG9mIGhvbGRpbmcgdGhlIGNhcDoKCi0gb3Npc20vaXNzdWVzIzE0MjAKCkJsb2NrZWQgd2hpbGUgdGhpcyBjYXAgaG9sZHMsIHNpbmNlIGBhbnNpYmxlYCAxNCByZXF1aXJlcyBgYW5zaWJsZS1jb3Jlfj0yLjIxLjJgOgoKLSBvc2lzbS9yZWxlYXNlIzI2MjMKCvCfpJYgR2VuZXJhdGVkIHdpdGggW0NsYXVkZSBDb2RlXShodHRwczovL2NsYXVkZS5jb20vY2xhdWRlLWNvZGUpCg==
      patchset: f3ee996d0b36eab208d02265eec2d1b0a16ab7a5
      pipeline: check
      playbook_context:
        playbook_projects:
          trusted/project_0/github.com/osism/zuul-config:
            canonical_name: github.com/osism/zuul-config
            checkout: main
            commit: 71b711c422c10c242a8f785dc6d41ed9d12e9cd3
          trusted/project_1/github.com/osism/openinfra-zuul-jobs:
            canonical_name: github.com/osism/openinfra-zuul-jobs
            checkout: master
            commit: 242732586e2cba04d04867d3e302888c766bc231
          trusted/project_2/github.com/osism/zuul-jobs:
            canonical_name: github.com/osism/zuul-jobs
            checkout: main
            commit: dcb06ea8a3ad422cc9d98b376216617b2daa6a02
          untrusted/project_0/github.com/osism/zuul-jobs:
            canonical_name: github.com/osism/zuul-jobs
            checkout: main
            commit: dcb06ea8a3ad422cc9d98b376216617b2daa6a02
          untrusted/project_1/github.com/osism/zuul-config:
            canonical_name: github.com/osism/zuul-config
            checkout: main
            commit: 71b711c422c10c242a8f785dc6d41ed9d12e9cd3
          untrusted/project_2/github.com/osism/openinfra-zuul-jobs:
            canonical_name: github.com/osism/openinfra-zuul-jobs
            checkout: master
            commit: 242732586e2cba04d04867d3e302888c766bc231
        playbooks:
        - path: untrusted/project_0/github.com/osism/zuul-jobs/playbooks/yamllint/run.yaml
          roles:
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/playbook_0/role_0/zuul-config
            link_target: untrusted/project_1/github.com/osism/zuul-config
            role_path: ansible/playbook_0/role_0/zuul-config/roles
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/playbook_0/role_1/openinfra-zuul-jobs
            link_target: untrusted/project_2/github.com/osism/openinfra-zuul-jobs
            role_path: ansible/playbook_0/role_1/openinfra-zuul-jobs/roles
          - checkout: main
            checkout_description: playbook branch
            link_name: ansible/playbook_0/role_2/zuul-jobs
            link_target: untrusted/project_0/github.com/osism/zuul-jobs
            role_path: ansible/playbook_0/role_2/zuul-jobs/roles
      post_review: false
      post_timeout: 1800
      pre_timeout: null
      project:
        canonical_hostname: github.com
        canonical_name: github.com/osism/release
        name: osism/release
        short_name: release
        src_dir: src/github.com/osism/release
      projects:
        github.com/osism/release:
          canonical_hostname: github.com
          canonical_name: github.com/osism/release
          checkout: main
          checkout_description: zuul branch
          commit: da10366284863d9e3889d116f7c0e8f0c869b63f
          name: osism/release
          required: false
          short_name: release
          src_dir: src/github.com/osism/release
      ref: refs/pull/2632/head
      resources: {}
      tenant: osism
      timeout: 1800
      topic: null
      voting: true
