all:
  children:
    zuul_unreachable:
      hosts: {}
  hosts:
    ubuntu-noble:
      ansible_connection: ssh
      ansible_host: 162.253.55.20
      ansible_port: 22
      ansible_python_interpreter: auto
      ansible_user: zuul
      nodepool:
        az: yul2
        cloud: public
        external_id: 0667e88a-b9e0-4921-b050-9ca90c12c05c
        host_id: c4600005a1f84ec9cc26b70f8fc016fbda1ce53427a51810c81ebddd
        interface_ip: 162.253.55.20
        label: ubuntu-noble
        node_properties: {}
        private_ipv4: 162.253.55.20
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.20
        public_ipv6: 2604:e100:1:0:f816:3eff:fe0c:f7c6
        region: ca-ymq-1
        slot: null
      tox_environment:
        NOSE_HTML_OUT_FILE: nose_results.html
        NOSE_WITH_HTML_OUTPUT: 1
        NOSE_WITH_XUNIT: 1
      tox_envlist: unit
      zuul_node:
        az: yul2
        cloud: public
        external_id: 0667e88a-b9e0-4921-b050-9ca90c12c05c
        host_id: c4600005a1f84ec9cc26b70f8fc016fbda1ce53427a51810c81ebddd
        interface_ip: 162.253.55.20
        label: ubuntu-noble
        node_properties: {}
        private_ipv4: 162.253.55.20
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.20
        public_ipv6: 2604:e100:1:0:f816:3eff:fe0c:f7c6
        region: ca-ymq-1
        slot: null
        uuid: null
  vars:
    tox_environment:
      NOSE_HTML_OUT_FILE: nose_results.html
      NOSE_WITH_HTML_OUTPUT: 1
      NOSE_WITH_XUNIT: 1
    tox_envlist: unit
    zuul:
      _inheritance_path:
      - '<Job base explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: vexxhost/zuul-config/zuul.d/jobs.yaml@main#1>'
      - '<Job unittests explicit: None implied: {MatchAny:{ImpliedBranchMatcher:master}}
        source: zuul/zuul-jobs/zuul.d/general-jobs.yaml@master#9>'
      - '<Job tox explicit: None implied: {MatchAny:{ImpliedBranchMatcher:master}}
        source: zuul/zuul-jobs/zuul.d/python-jobs.yaml@master#1>'
      - '<Job magnum-cluster-api-tox explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: vexxhost/magnum-cluster-api/zuul.d/jobs.yaml@main#1>'
      - '<Job magnum-cluster-api-tox-unit explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: vexxhost/magnum-cluster-api/zuul.d/jobs.yaml@main#7>'
      - '<Job magnum-cluster-api-tox-unit explicit: None implied: None source: vexxhost/magnum-cluster-api/zuul.d/project.yaml@main#1>'
      ansible_version: '9'
      attempts: 1
      branch: main
      build: 3dc5fe455cbd4e809f2438d7ede2e59c
      build_refs:
      - branch: main
        change: '889'
        change_message: "feat: verify kubelet serving certificates, approved by cluster-api-csr-approver\n\nCloses
          #365.\n\nToday every kubelet in a Magnum cluster serves its API (`logs`,
          `exec`, `port-forward`, metrics) with a self-signed certificate, and kube-apiserver
          connects without verifying it. With the new `kubelet_serving_cert_verification_enabled=true`
          label, each kubelet gets a serving certificate signed by the cluster CA,
          and kube-apiserver rejects any kubelet it can't verify. The legacy Heat
          driver always worked this way: it issued kubelet certificates itself and
          set `--kubelet-certificate-authority` unconditionally.\n\nKubernetes never
          approves kubelet serving CSRs on its own, so something has to check that
          the requested names belong to the node. This PR uses [cluster-api-csr-approver](https://github.com/vexxhost/cluster-api-csr-approver)
          (v0.1.0). It runs next to Cluster API in the management cluster and approves
          a CSR only when every IP and DNS name in it matches the addresses CAPO reports
          on that node's `Machine`. Earlier revisions installed postfinance/kubelet-csr-approver
          inside each workload cluster and accepted any IP in `fixed_subnet_cidr`.
          That approach rejected floating IPs, existing networks and extra interfaces,
          and let any node request a certificate for another node's IP. Atmosphere
          installs and enables the approver by default.\n\n## Behavior\n\n**Node configuration.**
          A kubeadm strategic patch at `/etc/kubernetes/patches/kubeletconfiguration0+strategic.json`
          sets `serverTLSBootstrap: true`. It is applied through `patches.directory`
          on `init` and `join`, on control plane and worker nodes, before the kubelet
          starts. kube-apiserver gets `--kubelet-certificate-authority=/etc/kubernetes/pki/ca.crt`.
          The feature is driven by the `enableKubeletServingCertificateVerification`
          ClusterClass variable. Like every other variable it is required: ClusterClasses
          are versioned, and clusters only move to a new one on create or upgrade,
          when the driver sends every variable.\n\nOnce kube-apiserver verifies kubelets,
          a new control plane node only becomes ready after its serving certificate
          is approved, so the approver must be installed before clusters use the label.
          The docs say so; the driver doesn't check for it.\n\n**Removed:** the vendored
          `kubelet-csr-approver` chart and patch, the Rust `ClusterAddon` and its
          addon Secret entry, the `fixed_subnet_cidr` label plumbing in Rust, the
          helm `--skip-tests` support, and the Helm 3.10.3 \u2192 3.12.0 bump that
          only existed for it.\n\n## CI\n\n`devstack/plugin.sh` (Zuul hydrophone jobs)
          and `hack/setup-capo.sh` (functional job and `hack/stack.sh`) register the
          approver as a clusterctl add-on provider. They install it with `--addon
          csr-approver:${CSR_APPROVER_VERSION}` (default `v0.1.0`) in the same `clusterctl
          init` and wait for `capi-csr-approver-system/capi-csr-approver-controller-manager`
          to roll out. The hydrophone clusters don't set the label, so the approver
          has nothing to approve there.\n\n## Docs\n\nThe new [admin guide](docs/admin/kubelet-serving-certificates.md)
          covers what Magnum does: the requirement, what the label changes, troubleshooting
          and limitations. Installation, configuration and observability link to the
          approver's README rather than copying it. The label entry in `labels.md`
          is updated.\n\n## Testing\n\n- `cargo test --workspace` passes, including
          the feature's tests for the patches with the label on and off and for the
          ClusterClass variable.\n- `pytest magnum_cluster_api/tests/unit/`: 218 passed.
          The 8 `test_update_nodegroup*` failures also happen on `main` and are unrelated.\n-
          clusterctl v1.13.2 (the CI version) resolves `csr-approver:v0.1.0` from
          the generated config with and without `GOPROXY=off`.\n- All 8 Zuul hydrophone
          jobs install the approver with clusterctl and pass; the job logs show it
          rolling out and running without errors. No CI cluster sets the label yet,
          so approval itself is covered by the approver's own CAPD and CAPO e2e suites.\n-
          pre-commit passes.\n\n## Deployment notes\n\nRequires Cluster API v1.11
          or later in the management cluster, the minimum the approver supports.\n"
        change_url: https://github.com/vexxhost/magnum-cluster-api/pull/889
        commit_id: 97816bc59c9a5789a53667d0c717308acaacb47a
        patchset: 97816bc59c9a5789a53667d0c717308acaacb47a
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/magnum-cluster-api
          name: vexxhost/magnum-cluster-api
          short_name: magnum-cluster-api
          src_dir: src/github.com/vexxhost/magnum-cluster-api
        src_dir: src/github.com/vexxhost/magnum-cluster-api
        topic: null
      buildset: 5c9bb71664744054a4938cf010f2af22
      buildset_refs:
      - branch: main
        change: '889'
        change_message: "feat: verify kubelet serving certificates, approved by cluster-api-csr-approver\n\nCloses
          #365.\n\nToday every kubelet in a Magnum cluster serves its API (`logs`,
          `exec`, `port-forward`, metrics) with a self-signed certificate, and kube-apiserver
          connects without verifying it. With the new `kubelet_serving_cert_verification_enabled=true`
          label, each kubelet gets a serving certificate signed by the cluster CA,
          and kube-apiserver rejects any kubelet it can't verify. The legacy Heat
          driver always worked this way: it issued kubelet certificates itself and
          set `--kubelet-certificate-authority` unconditionally.\n\nKubernetes never
          approves kubelet serving CSRs on its own, so something has to check that
          the requested names belong to the node. This PR uses [cluster-api-csr-approver](https://github.com/vexxhost/cluster-api-csr-approver)
          (v0.1.0). It runs next to Cluster API in the management cluster and approves
          a CSR only when every IP and DNS name in it matches the addresses CAPO reports
          on that node's `Machine`. Earlier revisions installed postfinance/kubelet-csr-approver
          inside each workload cluster and accepted any IP in `fixed_subnet_cidr`.
          That approach rejected floating IPs, existing networks and extra interfaces,
          and let any node request a certificate for another node's IP. Atmosphere
          installs and enables the approver by default.\n\n## Behavior\n\n**Node configuration.**
          A kubeadm strategic patch at `/etc/kubernetes/patches/kubeletconfiguration0+strategic.json`
          sets `serverTLSBootstrap: true`. It is applied through `patches.directory`
          on `init` and `join`, on control plane and worker nodes, before the kubelet
          starts. kube-apiserver gets `--kubelet-certificate-authority=/etc/kubernetes/pki/ca.crt`.
          The feature is driven by the `enableKubeletServingCertificateVerification`
          ClusterClass variable. Like every other variable it is required: ClusterClasses
          are versioned, and clusters only move to a new one on create or upgrade,
          when the driver sends every variable.\n\nOnce kube-apiserver verifies kubelets,
          a new control plane node only becomes ready after its serving certificate
          is approved, so the approver must be installed before clusters use the label.
          The docs say so; the driver doesn't check for it.\n\n**Removed:** the vendored
          `kubelet-csr-approver` chart and patch, the Rust `ClusterAddon` and its
          addon Secret entry, the `fixed_subnet_cidr` label plumbing in Rust, the
          helm `--skip-tests` support, and the Helm 3.10.3 \u2192 3.12.0 bump that
          only existed for it.\n\n## CI\n\n`devstack/plugin.sh` (Zuul hydrophone jobs)
          and `hack/setup-capo.sh` (functional job and `hack/stack.sh`) register the
          approver as a clusterctl add-on provider. They install it with `--addon
          csr-approver:${CSR_APPROVER_VERSION}` (default `v0.1.0`) in the same `clusterctl
          init` and wait for `capi-csr-approver-system/capi-csr-approver-controller-manager`
          to roll out. The hydrophone clusters don't set the label, so the approver
          has nothing to approve there.\n\n## Docs\n\nThe new [admin guide](docs/admin/kubelet-serving-certificates.md)
          covers what Magnum does: the requirement, what the label changes, troubleshooting
          and limitations. Installation, configuration and observability link to the
          approver's README rather than copying it. The label entry in `labels.md`
          is updated.\n\n## Testing\n\n- `cargo test --workspace` passes, including
          the feature's tests for the patches with the label on and off and for the
          ClusterClass variable.\n- `pytest magnum_cluster_api/tests/unit/`: 218 passed.
          The 8 `test_update_nodegroup*` failures also happen on `main` and are unrelated.\n-
          clusterctl v1.13.2 (the CI version) resolves `csr-approver:v0.1.0` from
          the generated config with and without `GOPROXY=off`.\n- All 8 Zuul hydrophone
          jobs install the approver with clusterctl and pass; the job logs show it
          rolling out and running without errors. No CI cluster sets the label yet,
          so approval itself is covered by the approver's own CAPD and CAPO e2e suites.\n-
          pre-commit passes.\n\n## Deployment notes\n\nRequires Cluster API v1.11
          or later in the management cluster, the minimum the approver supports.\n"
        change_url: https://github.com/vexxhost/magnum-cluster-api/pull/889
        commit_id: 97816bc59c9a5789a53667d0c717308acaacb47a
        patchset: 97816bc59c9a5789a53667d0c717308acaacb47a
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/magnum-cluster-api
          name: vexxhost/magnum-cluster-api
          short_name: magnum-cluster-api
          src_dir: src/github.com/vexxhost/magnum-cluster-api
        src_dir: src/github.com/vexxhost/magnum-cluster-api
        topic: null
      change: '889'
      change_message: "feat: verify kubelet serving certificates, approved by cluster-api-csr-approver\n\nCloses
        #365.\n\nToday every kubelet in a Magnum cluster serves its API (`logs`, `exec`,
        `port-forward`, metrics) with a self-signed certificate, and kube-apiserver
        connects without verifying it. With the new `kubelet_serving_cert_verification_enabled=true`
        label, each kubelet gets a serving certificate signed by the cluster CA, and
        kube-apiserver rejects any kubelet it can't verify. The legacy Heat driver
        always worked this way: it issued kubelet certificates itself and set `--kubelet-certificate-authority`
        unconditionally.\n\nKubernetes never approves kubelet serving CSRs on its
        own, so something has to check that the requested names belong to the node.
        This PR uses [cluster-api-csr-approver](https://github.com/vexxhost/cluster-api-csr-approver)
        (v0.1.0). It runs next to Cluster API in the management cluster and approves
        a CSR only when every IP and DNS name in it matches the addresses CAPO reports
        on that node's `Machine`. Earlier revisions installed postfinance/kubelet-csr-approver
        inside each workload cluster and accepted any IP in `fixed_subnet_cidr`. That
        approach rejected floating IPs, existing networks and extra interfaces, and
        let any node request a certificate for another node's IP. Atmosphere installs
        and enables the approver by default.\n\n## Behavior\n\n**Node configuration.**
        A kubeadm strategic patch at `/etc/kubernetes/patches/kubeletconfiguration0+strategic.json`
        sets `serverTLSBootstrap: true`. It is applied through `patches.directory`
        on `init` and `join`, on control plane and worker nodes, before the kubelet
        starts. kube-apiserver gets `--kubelet-certificate-authority=/etc/kubernetes/pki/ca.crt`.
        The feature is driven by the `enableKubeletServingCertificateVerification`
        ClusterClass variable. Like every other variable it is required: ClusterClasses
        are versioned, and clusters only move to a new one on create or upgrade, when
        the driver sends every variable.\n\nOnce kube-apiserver verifies kubelets,
        a new control plane node only becomes ready after its serving certificate
        is approved, so the approver must be installed before clusters use the label.
        The docs say so; the driver doesn't check for it.\n\n**Removed:** the vendored
        `kubelet-csr-approver` chart and patch, the Rust `ClusterAddon` and its addon
        Secret entry, the `fixed_subnet_cidr` label plumbing in Rust, the helm `--skip-tests`
        support, and the Helm 3.10.3 \u2192 3.12.0 bump that only existed for it.\n\n##
        CI\n\n`devstack/plugin.sh` (Zuul hydrophone jobs) and `hack/setup-capo.sh`
        (functional job and `hack/stack.sh`) register the approver as a clusterctl
        add-on provider. They install it with `--addon csr-approver:${CSR_APPROVER_VERSION}`
        (default `v0.1.0`) in the same `clusterctl init` and wait for `capi-csr-approver-system/capi-csr-approver-controller-manager`
        to roll out. The hydrophone clusters don't set the label, so the approver
        has nothing to approve there.\n\n## Docs\n\nThe new [admin guide](docs/admin/kubelet-serving-certificates.md)
        covers what Magnum does: the requirement, what the label changes, troubleshooting
        and limitations. Installation, configuration and observability link to the
        approver's README rather than copying it. The label entry in `labels.md` is
        updated.\n\n## Testing\n\n- `cargo test --workspace` passes, including the
        feature's tests for the patches with the label on and off and for the ClusterClass
        variable.\n- `pytest magnum_cluster_api/tests/unit/`: 218 passed. The 8 `test_update_nodegroup*`
        failures also happen on `main` and are unrelated.\n- clusterctl v1.13.2 (the
        CI version) resolves `csr-approver:v0.1.0` from the generated config with
        and without `GOPROXY=off`.\n- All 8 Zuul hydrophone jobs install the approver
        with clusterctl and pass; the job logs show it rolling out and running without
        errors. No CI cluster sets the label yet, so approval itself is covered by
        the approver's own CAPD and CAPO e2e suites.\n- pre-commit passes.\n\n## Deployment
        notes\n\nRequires Cluster API v1.11 or later in the management cluster, the
        minimum the approver supports.\n"
      change_url: https://github.com/vexxhost/magnum-cluster-api/pull/889
      child_jobs: []
      commit_id: 97816bc59c9a5789a53667d0c717308acaacb47a
      event_id: 54be68c0-d3a7-11f1-8469-6b7b47f95a76
      executor:
        hostname: 2d72f0692154
        inventory_file: /var/lib/zuul/builds/3dc5fe455cbd4e809f2438d7ede2e59c/ansible/inventory.yaml
        log_root: /var/lib/zuul/builds/3dc5fe455cbd4e809f2438d7ede2e59c/work/logs
        result_data_file: /var/lib/zuul/builds/3dc5fe455cbd4e809f2438d7ede2e59c/work/results.json
        src_root: /var/lib/zuul/builds/3dc5fe455cbd4e809f2438d7ede2e59c/work/src
        work_root: /var/lib/zuul/builds/3dc5fe455cbd4e809f2438d7ede2e59c/work
      include_vars: []
      items:
      - branch: main
        change: '889'
        change_message: "feat: verify kubelet serving certificates, approved by cluster-api-csr-approver\n\nCloses
          #365.\n\nToday every kubelet in a Magnum cluster serves its API (`logs`,
          `exec`, `port-forward`, metrics) with a self-signed certificate, and kube-apiserver
          connects without verifying it. With the new `kubelet_serving_cert_verification_enabled=true`
          label, each kubelet gets a serving certificate signed by the cluster CA,
          and kube-apiserver rejects any kubelet it can't verify. The legacy Heat
          driver always worked this way: it issued kubelet certificates itself and
          set `--kubelet-certificate-authority` unconditionally.\n\nKubernetes never
          approves kubelet serving CSRs on its own, so something has to check that
          the requested names belong to the node. This PR uses [cluster-api-csr-approver](https://github.com/vexxhost/cluster-api-csr-approver)
          (v0.1.0). It runs next to Cluster API in the management cluster and approves
          a CSR only when every IP and DNS name in it matches the addresses CAPO reports
          on that node's `Machine`. Earlier revisions installed postfinance/kubelet-csr-approver
          inside each workload cluster and accepted any IP in `fixed_subnet_cidr`.
          That approach rejected floating IPs, existing networks and extra interfaces,
          and let any node request a certificate for another node's IP. Atmosphere
          installs and enables the approver by default.\n\n## Behavior\n\n**Node configuration.**
          A kubeadm strategic patch at `/etc/kubernetes/patches/kubeletconfiguration0+strategic.json`
          sets `serverTLSBootstrap: true`. It is applied through `patches.directory`
          on `init` and `join`, on control plane and worker nodes, before the kubelet
          starts. kube-apiserver gets `--kubelet-certificate-authority=/etc/kubernetes/pki/ca.crt`.
          The feature is driven by the `enableKubeletServingCertificateVerification`
          ClusterClass variable. Like every other variable it is required: ClusterClasses
          are versioned, and clusters only move to a new one on create or upgrade,
          when the driver sends every variable.\n\nOnce kube-apiserver verifies kubelets,
          a new control plane node only becomes ready after its serving certificate
          is approved, so the approver must be installed before clusters use the label.
          The docs say so; the driver doesn't check for it.\n\n**Removed:** the vendored
          `kubelet-csr-approver` chart and patch, the Rust `ClusterAddon` and its
          addon Secret entry, the `fixed_subnet_cidr` label plumbing in Rust, the
          helm `--skip-tests` support, and the Helm 3.10.3 \u2192 3.12.0 bump that
          only existed for it.\n\n## CI\n\n`devstack/plugin.sh` (Zuul hydrophone jobs)
          and `hack/setup-capo.sh` (functional job and `hack/stack.sh`) register the
          approver as a clusterctl add-on provider. They install it with `--addon
          csr-approver:${CSR_APPROVER_VERSION}` (default `v0.1.0`) in the same `clusterctl
          init` and wait for `capi-csr-approver-system/capi-csr-approver-controller-manager`
          to roll out. The hydrophone clusters don't set the label, so the approver
          has nothing to approve there.\n\n## Docs\n\nThe new [admin guide](docs/admin/kubelet-serving-certificates.md)
          covers what Magnum does: the requirement, what the label changes, troubleshooting
          and limitations. Installation, configuration and observability link to the
          approver's README rather than copying it. The label entry in `labels.md`
          is updated.\n\n## Testing\n\n- `cargo test --workspace` passes, including
          the feature's tests for the patches with the label on and off and for the
          ClusterClass variable.\n- `pytest magnum_cluster_api/tests/unit/`: 218 passed.
          The 8 `test_update_nodegroup*` failures also happen on `main` and are unrelated.\n-
          clusterctl v1.13.2 (the CI version) resolves `csr-approver:v0.1.0` from
          the generated config with and without `GOPROXY=off`.\n- All 8 Zuul hydrophone
          jobs install the approver with clusterctl and pass; the job logs show it
          rolling out and running without errors. No CI cluster sets the label yet,
          so approval itself is covered by the approver's own CAPD and CAPO e2e suites.\n-
          pre-commit passes.\n\n## Deployment notes\n\nRequires Cluster API v1.11
          or later in the management cluster, the minimum the approver supports.\n"
        change_url: https://github.com/vexxhost/magnum-cluster-api/pull/889
        commit_id: 97816bc59c9a5789a53667d0c717308acaacb47a
        patchset: 97816bc59c9a5789a53667d0c717308acaacb47a
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/magnum-cluster-api
          name: vexxhost/magnum-cluster-api
          short_name: magnum-cluster-api
          src_dir: src/github.com/vexxhost/magnum-cluster-api
        topic: null
      job: magnum-cluster-api-tox-unit
      jobtags: []
      max_attempts: 3
      message: ZmVhdDogdmVyaWZ5IGt1YmVsZXQgc2VydmluZyBjZXJ0aWZpY2F0ZXMsIGFwcHJvdmVkIGJ5IGNsdXN0ZXItYXBpLWNzci1hcHByb3ZlcgoKQ2xvc2VzICMzNjUuCgpUb2RheSBldmVyeSBrdWJlbGV0IGluIGEgTWFnbnVtIGNsdXN0ZXIgc2VydmVzIGl0cyBBUEkgKGBsb2dzYCwgYGV4ZWNgLCBgcG9ydC1mb3J3YXJkYCwgbWV0cmljcykgd2l0aCBhIHNlbGYtc2lnbmVkIGNlcnRpZmljYXRlLCBhbmQga3ViZS1hcGlzZXJ2ZXIgY29ubmVjdHMgd2l0aG91dCB2ZXJpZnlpbmcgaXQuIFdpdGggdGhlIG5ldyBga3ViZWxldF9zZXJ2aW5nX2NlcnRfdmVyaWZpY2F0aW9uX2VuYWJsZWQ9dHJ1ZWAgbGFiZWwsIGVhY2gga3ViZWxldCBnZXRzIGEgc2VydmluZyBjZXJ0aWZpY2F0ZSBzaWduZWQgYnkgdGhlIGNsdXN0ZXIgQ0EsIGFuZCBrdWJlLWFwaXNlcnZlciByZWplY3RzIGFueSBrdWJlbGV0IGl0IGNhbid0IHZlcmlmeS4gVGhlIGxlZ2FjeSBIZWF0IGRyaXZlciBhbHdheXMgd29ya2VkIHRoaXMgd2F5OiBpdCBpc3N1ZWQga3ViZWxldCBjZXJ0aWZpY2F0ZXMgaXRzZWxmIGFuZCBzZXQgYC0ta3ViZWxldC1jZXJ0aWZpY2F0ZS1hdXRob3JpdHlgIHVuY29uZGl0aW9uYWxseS4KCkt1YmVybmV0ZXMgbmV2ZXIgYXBwcm92ZXMga3ViZWxldCBzZXJ2aW5nIENTUnMgb24gaXRzIG93biwgc28gc29tZXRoaW5nIGhhcyB0byBjaGVjayB0aGF0IHRoZSByZXF1ZXN0ZWQgbmFtZXMgYmVsb25nIHRvIHRoZSBub2RlLiBUaGlzIFBSIHVzZXMgW2NsdXN0ZXItYXBpLWNzci1hcHByb3Zlcl0oaHR0cHM6Ly9naXRodWIuY29tL3ZleHhob3N0L2NsdXN0ZXItYXBpLWNzci1hcHByb3ZlcikgKHYwLjEuMCkuIEl0IHJ1bnMgbmV4dCB0byBDbHVzdGVyIEFQSSBpbiB0aGUgbWFuYWdlbWVudCBjbHVzdGVyIGFuZCBhcHByb3ZlcyBhIENTUiBvbmx5IHdoZW4gZXZlcnkgSVAgYW5kIEROUyBuYW1lIGluIGl0IG1hdGNoZXMgdGhlIGFkZHJlc3NlcyBDQVBPIHJlcG9ydHMgb24gdGhhdCBub2RlJ3MgYE1hY2hpbmVgLiBFYXJsaWVyIHJldmlzaW9ucyBpbnN0YWxsZWQgcG9zdGZpbmFuY2Uva3ViZWxldC1jc3ItYXBwcm92ZXIgaW5zaWRlIGVhY2ggd29ya2xvYWQgY2x1c3RlciBhbmQgYWNjZXB0ZWQgYW55IElQIGluIGBmaXhlZF9zdWJuZXRfY2lkcmAuIFRoYXQgYXBwcm9hY2ggcmVqZWN0ZWQgZmxvYXRpbmcgSVBzLCBleGlzdGluZyBuZXR3b3JrcyBhbmQgZXh0cmEgaW50ZXJmYWNlcywgYW5kIGxldCBhbnkgbm9kZSByZXF1ZXN0IGEgY2VydGlmaWNhdGUgZm9yIGFub3RoZXIgbm9kZSdzIElQLiBBdG1vc3BoZXJlIGluc3RhbGxzIGFuZCBlbmFibGVzIHRoZSBhcHByb3ZlciBieSBkZWZhdWx0LgoKIyMgQmVoYXZpb3IKCioqTm9kZSBjb25maWd1cmF0aW9uLioqIEEga3ViZWFkbSBzdHJhdGVnaWMgcGF0Y2ggYXQgYC9ldGMva3ViZXJuZXRlcy9wYXRjaGVzL2t1YmVsZXRjb25maWd1cmF0aW9uMCtzdHJhdGVnaWMuanNvbmAgc2V0cyBgc2VydmVyVExTQm9vdHN0cmFwOiB0cnVlYC4gSXQgaXMgYXBwbGllZCB0aHJvdWdoIGBwYXRjaGVzLmRpcmVjdG9yeWAgb24gYGluaXRgIGFuZCBgam9pbmAsIG9uIGNvbnRyb2wgcGxhbmUgYW5kIHdvcmtlciBub2RlcywgYmVmb3JlIHRoZSBrdWJlbGV0IHN0YXJ0cy4ga3ViZS1hcGlzZXJ2ZXIgZ2V0cyBgLS1rdWJlbGV0LWNlcnRpZmljYXRlLWF1dGhvcml0eT0vZXRjL2t1YmVybmV0ZXMvcGtpL2NhLmNydGAuIFRoZSBmZWF0dXJlIGlzIGRyaXZlbiBieSB0aGUgYGVuYWJsZUt1YmVsZXRTZXJ2aW5nQ2VydGlmaWNhdGVWZXJpZmljYXRpb25gIENsdXN0ZXJDbGFzcyB2YXJpYWJsZS4gTGlrZSBldmVyeSBvdGhlciB2YXJpYWJsZSBpdCBpcyByZXF1aXJlZDogQ2x1c3RlckNsYXNzZXMgYXJlIHZlcnNpb25lZCwgYW5kIGNsdXN0ZXJzIG9ubHkgbW92ZSB0byBhIG5ldyBvbmUgb24gY3JlYXRlIG9yIHVwZ3JhZGUsIHdoZW4gdGhlIGRyaXZlciBzZW5kcyBldmVyeSB2YXJpYWJsZS4KCk9uY2Uga3ViZS1hcGlzZXJ2ZXIgdmVyaWZpZXMga3ViZWxldHMsIGEgbmV3IGNvbnRyb2wgcGxhbmUgbm9kZSBvbmx5IGJlY29tZXMgcmVhZHkgYWZ0ZXIgaXRzIHNlcnZpbmcgY2VydGlmaWNhdGUgaXMgYXBwcm92ZWQsIHNvIHRoZSBhcHByb3ZlciBtdXN0IGJlIGluc3RhbGxlZCBiZWZvcmUgY2x1c3RlcnMgdXNlIHRoZSBsYWJlbC4gVGhlIGRvY3Mgc2F5IHNvOyB0aGUgZHJpdmVyIGRvZXNuJ3QgY2hlY2sgZm9yIGl0LgoKKipSZW1vdmVkOioqIHRoZSB2ZW5kb3JlZCBga3ViZWxldC1jc3ItYXBwcm92ZXJgIGNoYXJ0IGFuZCBwYXRjaCwgdGhlIFJ1c3QgYENsdXN0ZXJBZGRvbmAgYW5kIGl0cyBhZGRvbiBTZWNyZXQgZW50cnksIHRoZSBgZml4ZWRfc3VibmV0X2NpZHJgIGxhYmVsIHBsdW1iaW5nIGluIFJ1c3QsIHRoZSBoZWxtIGAtLXNraXAtdGVzdHNgIHN1cHBvcnQsIGFuZCB0aGUgSGVsbSAzLjEwLjMg4oaSIDMuMTIuMCBidW1wIHRoYXQgb25seSBleGlzdGVkIGZvciBpdC4KCiMjIENJCgpgZGV2c3RhY2svcGx1Z2luLnNoYCAoWnV1bCBoeWRyb3Bob25lIGpvYnMpIGFuZCBgaGFjay9zZXR1cC1jYXBvLnNoYCAoZnVuY3Rpb25hbCBqb2IgYW5kIGBoYWNrL3N0YWNrLnNoYCkgcmVnaXN0ZXIgdGhlIGFwcHJvdmVyIGFzIGEgY2x1c3RlcmN0bCBhZGQtb24gcHJvdmlkZXIuIFRoZXkgaW5zdGFsbCBpdCB3aXRoIGAtLWFkZG9uIGNzci1hcHByb3Zlcjoke0NTUl9BUFBST1ZFUl9WRVJTSU9OfWAgKGRlZmF1bHQgYHYwLjEuMGApIGluIHRoZSBzYW1lIGBjbHVzdGVyY3RsIGluaXRgIGFuZCB3YWl0IGZvciBgY2FwaS1jc3ItYXBwcm92ZXItc3lzdGVtL2NhcGktY3NyLWFwcHJvdmVyLWNvbnRyb2xsZXItbWFuYWdlcmAgdG8gcm9sbCBvdXQuIFRoZSBoeWRyb3Bob25lIGNsdXN0ZXJzIGRvbid0IHNldCB0aGUgbGFiZWwsIHNvIHRoZSBhcHByb3ZlciBoYXMgbm90aGluZyB0byBhcHByb3ZlIHRoZXJlLgoKIyMgRG9jcwoKVGhlIG5ldyBbYWRtaW4gZ3VpZGVdKGRvY3MvYWRtaW4va3ViZWxldC1zZXJ2aW5nLWNlcnRpZmljYXRlcy5tZCkgY292ZXJzIHdoYXQgTWFnbnVtIGRvZXM6IHRoZSByZXF1aXJlbWVudCwgd2hhdCB0aGUgbGFiZWwgY2hhbmdlcywgdHJvdWJsZXNob290aW5nIGFuZCBsaW1pdGF0aW9ucy4gSW5zdGFsbGF0aW9uLCBjb25maWd1cmF0aW9uIGFuZCBvYnNlcnZhYmlsaXR5IGxpbmsgdG8gdGhlIGFwcHJvdmVyJ3MgUkVBRE1FIHJhdGhlciB0aGFuIGNvcHlpbmcgaXQuIFRoZSBsYWJlbCBlbnRyeSBpbiBgbGFiZWxzLm1kYCBpcyB1cGRhdGVkLgoKIyMgVGVzdGluZwoKLSBgY2FyZ28gdGVzdCAtLXdvcmtzcGFjZWAgcGFzc2VzLCBpbmNsdWRpbmcgdGhlIGZlYXR1cmUncyB0ZXN0cyBmb3IgdGhlIHBhdGNoZXMgd2l0aCB0aGUgbGFiZWwgb24gYW5kIG9mZiBhbmQgZm9yIHRoZSBDbHVzdGVyQ2xhc3MgdmFyaWFibGUuCi0gYHB5dGVzdCBtYWdudW1fY2x1c3Rlcl9hcGkvdGVzdHMvdW5pdC9gOiAyMTggcGFzc2VkLiBUaGUgOCBgdGVzdF91cGRhdGVfbm9kZWdyb3VwKmAgZmFpbHVyZXMgYWxzbyBoYXBwZW4gb24gYG1haW5gIGFuZCBhcmUgdW5yZWxhdGVkLgotIGNsdXN0ZXJjdGwgdjEuMTMuMiAodGhlIENJIHZlcnNpb24pIHJlc29sdmVzIGBjc3ItYXBwcm92ZXI6djAuMS4wYCBmcm9tIHRoZSBnZW5lcmF0ZWQgY29uZmlnIHdpdGggYW5kIHdpdGhvdXQgYEdPUFJPWFk9b2ZmYC4KLSBBbGwgOCBadXVsIGh5ZHJvcGhvbmUgam9icyBpbnN0YWxsIHRoZSBhcHByb3ZlciB3aXRoIGNsdXN0ZXJjdGwgYW5kIHBhc3M7IHRoZSBqb2IgbG9ncyBzaG93IGl0IHJvbGxpbmcgb3V0IGFuZCBydW5uaW5nIHdpdGhvdXQgZXJyb3JzLiBObyBDSSBjbHVzdGVyIHNldHMgdGhlIGxhYmVsIHlldCwgc28gYXBwcm92YWwgaXRzZWxmIGlzIGNvdmVyZWQgYnkgdGhlIGFwcHJvdmVyJ3Mgb3duIENBUEQgYW5kIENBUE8gZTJlIHN1aXRlcy4KLSBwcmUtY29tbWl0IHBhc3Nlcy4KCiMjIERlcGxveW1lbnQgbm90ZXMKClJlcXVpcmVzIENsdXN0ZXIgQVBJIHYxLjExIG9yIGxhdGVyIGluIHRoZSBtYW5hZ2VtZW50IGNsdXN0ZXIsIHRoZSBtaW5pbXVtIHRoZSBhcHByb3ZlciBzdXBwb3J0cy4K
      patchset: 97816bc59c9a5789a53667d0c717308acaacb47a
      pipeline: check
      playbook_context:
        playbook_projects:
          trusted/project_0/github.com/vexxhost/zuul-config:
            canonical_name: github.com/vexxhost/zuul-config
            checkout: main
            commit: 298983cd1253e6833abdb49d87d912527e0e6597
          trusted/project_1/opendev.org/zuul/zuul-jobs:
            canonical_name: opendev.org/zuul/zuul-jobs
            checkout: master
            commit: f440b84a5acad7dc4611f363d8aca14806971959
          trusted/project_2/github.com/vexxhost/zuul-jobs:
            canonical_name: github.com/vexxhost/zuul-jobs
            checkout: main
            commit: 4fd48825891421af0774bdd500fee36e111d80a6
          untrusted/project_0/opendev.org/zuul/zuul-jobs:
            canonical_name: opendev.org/zuul/zuul-jobs
            checkout: master
            commit: f440b84a5acad7dc4611f363d8aca14806971959
          untrusted/project_1/github.com/vexxhost/zuul-config:
            canonical_name: github.com/vexxhost/zuul-config
            checkout: main
            commit: 298983cd1253e6833abdb49d87d912527e0e6597
          untrusted/project_2/github.com/vexxhost/zuul-jobs:
            canonical_name: github.com/vexxhost/zuul-jobs
            checkout: main
            commit: 4fd48825891421af0774bdd500fee36e111d80a6
          untrusted/project_3/github.com/vexxhost/magnum-cluster-api:
            canonical_name: github.com/vexxhost/magnum-cluster-api
            checkout: main
            commit: 0586418a25df102be7afa0662b6b49204e83cfee
        playbooks:
        - path: untrusted/project_0/opendev.org/zuul/zuul-jobs/playbooks/tox/run.yaml
          roles:
          - checkout: master
            checkout_description: playbook branch
            link_name: ansible/playbook_0/role_1/zuul-jobs
            link_target: untrusted/project_0/opendev.org/zuul/zuul-jobs
            role_path: ansible/playbook_0/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/playbook_0/role_2/zuul-jobs
            link_target: untrusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/playbook_0/role_2/zuul-jobs/roles
        post_playbooks:
        - path: untrusted/project_0/opendev.org/zuul/zuul-jobs/playbooks/tox/post.yaml
          roles:
          - checkout: master
            checkout_description: playbook branch
            link_name: ansible/post_playbook_0/role_1/zuul-jobs
            link_target: untrusted/project_0/opendev.org/zuul/zuul-jobs
            role_path: ansible/post_playbook_0/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/post_playbook_0/role_2/zuul-jobs
            link_target: untrusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/post_playbook_0/role_2/zuul-jobs/roles
        - path: untrusted/project_0/opendev.org/zuul/zuul-jobs/playbooks/unittests/post.yaml
          roles:
          - checkout: master
            checkout_description: playbook branch
            link_name: ansible/post_playbook_1/role_1/zuul-jobs
            link_target: untrusted/project_0/opendev.org/zuul/zuul-jobs
            role_path: ansible/post_playbook_1/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/post_playbook_1/role_2/zuul-jobs
            link_target: untrusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/post_playbook_1/role_2/zuul-jobs/roles
        - path: trusted/project_0/github.com/vexxhost/zuul-config/playbooks/base/post.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/post_playbook_2/role_1/zuul-jobs
            link_target: trusted/project_1/opendev.org/zuul/zuul-jobs
            role_path: ansible/post_playbook_2/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/post_playbook_2/role_2/zuul-jobs
            link_target: trusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/post_playbook_2/role_2/zuul-jobs/roles
        - path: trusted/project_0/github.com/vexxhost/zuul-config/playbooks/base/post-logs.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/post_playbook_3/role_1/zuul-jobs
            link_target: trusted/project_1/opendev.org/zuul/zuul-jobs
            role_path: ansible/post_playbook_3/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/post_playbook_3/role_2/zuul-jobs
            link_target: trusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/post_playbook_3/role_2/zuul-jobs/roles
        pre_playbooks:
        - path: trusted/project_0/github.com/vexxhost/zuul-config/playbooks/base/pre.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/pre_playbook_0/role_1/zuul-jobs
            link_target: trusted/project_1/opendev.org/zuul/zuul-jobs
            role_path: ansible/pre_playbook_0/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/pre_playbook_0/role_2/zuul-jobs
            link_target: trusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/pre_playbook_0/role_2/zuul-jobs/roles
        - path: untrusted/project_0/opendev.org/zuul/zuul-jobs/playbooks/unittests/pre.yaml
          roles:
          - checkout: master
            checkout_description: playbook branch
            link_name: ansible/pre_playbook_1/role_1/zuul-jobs
            link_target: untrusted/project_0/opendev.org/zuul/zuul-jobs
            role_path: ansible/pre_playbook_1/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/pre_playbook_1/role_2/zuul-jobs
            link_target: untrusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/pre_playbook_1/role_2/zuul-jobs/roles
        - path: untrusted/project_0/opendev.org/zuul/zuul-jobs/playbooks/tox/pre.yaml
          roles:
          - checkout: master
            checkout_description: playbook branch
            link_name: ansible/pre_playbook_2/role_1/zuul-jobs
            link_target: untrusted/project_0/opendev.org/zuul/zuul-jobs
            role_path: ansible/pre_playbook_2/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/pre_playbook_2/role_2/zuul-jobs
            link_target: untrusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/pre_playbook_2/role_2/zuul-jobs/roles
        - path: untrusted/project_3/github.com/vexxhost/magnum-cluster-api/zuul.d/playbooks/tox/pre.yml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/pre_playbook_3/role_2/zuul-jobs
            link_target: untrusted/project_0/opendev.org/zuul/zuul-jobs
            role_path: ansible/pre_playbook_3/role_2/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/pre_playbook_3/role_3/zuul-jobs
            link_target: untrusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/pre_playbook_3/role_3/zuul-jobs/roles
        - path: untrusted/project_3/github.com/vexxhost/magnum-cluster-api/zuul.d/playbooks/unit/pre.yml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/pre_playbook_4/role_2/zuul-jobs
            link_target: untrusted/project_0/opendev.org/zuul/zuul-jobs
            role_path: ansible/pre_playbook_4/role_2/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/pre_playbook_4/role_3/zuul-jobs
            link_target: untrusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/pre_playbook_4/role_3/zuul-jobs/roles
      post_review: false
      post_timeout: null
      pre_timeout: null
      project:
        canonical_hostname: github.com
        canonical_name: github.com/vexxhost/magnum-cluster-api
        name: vexxhost/magnum-cluster-api
        short_name: magnum-cluster-api
        src_dir: src/github.com/vexxhost/magnum-cluster-api
      projects:
        github.com/vexxhost/magnum-cluster-api:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/magnum-cluster-api
          checkout: main
          checkout_description: zuul branch
          commit: 0586418a25df102be7afa0662b6b49204e83cfee
          name: vexxhost/magnum-cluster-api
          required: false
          short_name: magnum-cluster-api
          src_dir: src/github.com/vexxhost/magnum-cluster-api
      ref: refs/pull/889/head
      resources: {}
      tenant: oss
      timeout: 1800
      topic: null
      voting: true
