all:
  children:
    zuul_unreachable:
      hosts: {}
  hosts:
    debian-bookworm:
      ansible_connection: ssh
      ansible_host: 2a13:1a81:8000:3124:f816:3eff:fedc:f23
      ansible_port: 22
      ansible_python_interpreter: auto
      ansible_user: zuul
      nodepool:
        az: nova
        cloud: regiocloud-a-ci
        external_id: 29ee56b7-7bdc-4a79-9ea4-d579467e6081
        host_id: 82101243836454d7401d5893feae9e2c5df7cc291646d8a99b33b53b
        interface_ip: 2a13:1a81:8000:3124:f816:3eff:fedc:f23
        label: debian-bookworm
        node_properties: {}
        private_ipv4: 10.128.7.28
        private_ipv6: null
        provider: regiocloud-a
        public_ipv4: 81.163.193.0
        public_ipv6: 2a13:1a81:8000:3124:f816:3eff:fedc:f23
        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 ansible-collection-ensure-readme explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: osism/zuul-jobs/.zuul.yaml@main#2>'
      - '<Job ansible-collection-ensure-readme explicit: None implied: None source:
        osism/ansible-collection-services/.zuul.yaml@main#498>'
      ansible_version: '9'
      attempts: 1
      branch: main
      build: a7847fee1c094fb69830c88e98387761
      build_refs:
      - branch: main
        change: '2109'
        change_message: "netbox: recreate containers after pulling new images\n\n##
          Problem\n\nThe `Pull container images` task in `roles/netbox/tasks/service.yml`
          pulls new images but has no `notify`/`register`. A recreate (`docker compose
          up -d`, via the `Restart netbox service` handler chain) is only triggered
          when the rendered `docker-compose.yml` changes or the systemd unit changes.\n\nOn
          a rolling-tag update (e.g. `latest` \u2192 `latest`) the compose file text
          is identical and the service is already active, so neither trigger fires
          \u2014 the freshly pulled image is downloaded but the running container
          keeps the old image (which has lost its `:latest` tag) until the next compose/unit
          change or a manual `systemctl restart netbox.service`.\n\n## Fix\n\nNotify
          the existing `Restart netbox service` handler from the pull task:\n\n```yaml\n-
          name: Pull container images\n  community.docker.docker_compose_v2_pull:\n
          \   project_src: \"{{ netbox_docker_compose_directory }}\"\n  when: netbox_pre_pull
          | bool\n  retries: 3\n  delay: 30\n  notify: Restart netbox service\n```\n\nThe
          notify only fires when the pull actually reports `changed`; the handler
          chain ends in `service: state: restarted` \u2192 systemd `ExecStart=docker
          compose up --remove-orphans` \u2192 containers recreated with the new images.
          The handler keeps respecting `netbox_service_allow_restart`, and the duplicate
          notify from `Copy docker-compose.yml` still collapses into a single restart.\n\nThis
          mirrors the manager-role fix in #2106 (root cause #2105).\n\nCloses #2107"
        change_url: https://github.com/osism/ansible-collection-services/pull/2109
        commit_id: 61d4d1bdf61d7fb55ebd19dba43e179c33391054
        patchset: 61d4d1bdf61d7fb55ebd19dba43e179c33391054
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-services
          name: osism/ansible-collection-services
          short_name: ansible-collection-services
        src_dir: src/github.com/osism/ansible-collection-services
        topic: null
      buildset: 7dad57dcbd6b47239e968e3d30bf8019
      buildset_refs:
      - branch: main
        change: '2109'
        change_message: "netbox: recreate containers after pulling new images\n\n##
          Problem\n\nThe `Pull container images` task in `roles/netbox/tasks/service.yml`
          pulls new images but has no `notify`/`register`. A recreate (`docker compose
          up -d`, via the `Restart netbox service` handler chain) is only triggered
          when the rendered `docker-compose.yml` changes or the systemd unit changes.\n\nOn
          a rolling-tag update (e.g. `latest` \u2192 `latest`) the compose file text
          is identical and the service is already active, so neither trigger fires
          \u2014 the freshly pulled image is downloaded but the running container
          keeps the old image (which has lost its `:latest` tag) until the next compose/unit
          change or a manual `systemctl restart netbox.service`.\n\n## Fix\n\nNotify
          the existing `Restart netbox service` handler from the pull task:\n\n```yaml\n-
          name: Pull container images\n  community.docker.docker_compose_v2_pull:\n
          \   project_src: \"{{ netbox_docker_compose_directory }}\"\n  when: netbox_pre_pull
          | bool\n  retries: 3\n  delay: 30\n  notify: Restart netbox service\n```\n\nThe
          notify only fires when the pull actually reports `changed`; the handler
          chain ends in `service: state: restarted` \u2192 systemd `ExecStart=docker
          compose up --remove-orphans` \u2192 containers recreated with the new images.
          The handler keeps respecting `netbox_service_allow_restart`, and the duplicate
          notify from `Copy docker-compose.yml` still collapses into a single restart.\n\nThis
          mirrors the manager-role fix in #2106 (root cause #2105).\n\nCloses #2107"
        change_url: https://github.com/osism/ansible-collection-services/pull/2109
        commit_id: 61d4d1bdf61d7fb55ebd19dba43e179c33391054
        patchset: 61d4d1bdf61d7fb55ebd19dba43e179c33391054
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-services
          name: osism/ansible-collection-services
          short_name: ansible-collection-services
        src_dir: src/github.com/osism/ansible-collection-services
        topic: null
      change: '2109'
      change_message: "netbox: recreate containers after pulling new images\n\n##
        Problem\n\nThe `Pull container images` task in `roles/netbox/tasks/service.yml`
        pulls new images but has no `notify`/`register`. A recreate (`docker compose
        up -d`, via the `Restart netbox service` handler chain) is only triggered
        when the rendered `docker-compose.yml` changes or the systemd unit changes.\n\nOn
        a rolling-tag update (e.g. `latest` \u2192 `latest`) the compose file text
        is identical and the service is already active, so neither trigger fires \u2014
        the freshly pulled image is downloaded but the running container keeps the
        old image (which has lost its `:latest` tag) until the next compose/unit change
        or a manual `systemctl restart netbox.service`.\n\n## Fix\n\nNotify the existing
        `Restart netbox service` handler from the pull task:\n\n```yaml\n- name: Pull
        container images\n  community.docker.docker_compose_v2_pull:\n    project_src:
        \"{{ netbox_docker_compose_directory }}\"\n  when: netbox_pre_pull | bool\n
        \ retries: 3\n  delay: 30\n  notify: Restart netbox service\n```\n\nThe notify
        only fires when the pull actually reports `changed`; the handler chain ends
        in `service: state: restarted` \u2192 systemd `ExecStart=docker compose up
        --remove-orphans` \u2192 containers recreated with the new images. The handler
        keeps respecting `netbox_service_allow_restart`, and the duplicate notify
        from `Copy docker-compose.yml` still collapses into a single restart.\n\nThis
        mirrors the manager-role fix in #2106 (root cause #2105).\n\nCloses #2107"
      change_url: https://github.com/osism/ansible-collection-services/pull/2109
      child_jobs: []
      commit_id: 61d4d1bdf61d7fb55ebd19dba43e179c33391054
      event_id: df5d6490-6a25-11f1-8bf2-b7ff7698e487
      executor:
        hostname: 521e9411259a
        inventory_file: /var/lib/zuul/builds/a7847fee1c094fb69830c88e98387761/ansible/inventory.yaml
        log_root: /var/lib/zuul/builds/a7847fee1c094fb69830c88e98387761/work/logs
        result_data_file: /var/lib/zuul/builds/a7847fee1c094fb69830c88e98387761/work/results.json
        src_root: /var/lib/zuul/builds/a7847fee1c094fb69830c88e98387761/work/src
        work_root: /var/lib/zuul/builds/a7847fee1c094fb69830c88e98387761/work
      include_vars: []
      items:
      - branch: main
        change: '2109'
        change_message: "netbox: recreate containers after pulling new images\n\n##
          Problem\n\nThe `Pull container images` task in `roles/netbox/tasks/service.yml`
          pulls new images but has no `notify`/`register`. A recreate (`docker compose
          up -d`, via the `Restart netbox service` handler chain) is only triggered
          when the rendered `docker-compose.yml` changes or the systemd unit changes.\n\nOn
          a rolling-tag update (e.g. `latest` \u2192 `latest`) the compose file text
          is identical and the service is already active, so neither trigger fires
          \u2014 the freshly pulled image is downloaded but the running container
          keeps the old image (which has lost its `:latest` tag) until the next compose/unit
          change or a manual `systemctl restart netbox.service`.\n\n## Fix\n\nNotify
          the existing `Restart netbox service` handler from the pull task:\n\n```yaml\n-
          name: Pull container images\n  community.docker.docker_compose_v2_pull:\n
          \   project_src: \"{{ netbox_docker_compose_directory }}\"\n  when: netbox_pre_pull
          | bool\n  retries: 3\n  delay: 30\n  notify: Restart netbox service\n```\n\nThe
          notify only fires when the pull actually reports `changed`; the handler
          chain ends in `service: state: restarted` \u2192 systemd `ExecStart=docker
          compose up --remove-orphans` \u2192 containers recreated with the new images.
          The handler keeps respecting `netbox_service_allow_restart`, and the duplicate
          notify from `Copy docker-compose.yml` still collapses into a single restart.\n\nThis
          mirrors the manager-role fix in #2106 (root cause #2105).\n\nCloses #2107"
        change_url: https://github.com/osism/ansible-collection-services/pull/2109
        commit_id: 61d4d1bdf61d7fb55ebd19dba43e179c33391054
        patchset: 61d4d1bdf61d7fb55ebd19dba43e179c33391054
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-services
          name: osism/ansible-collection-services
          short_name: ansible-collection-services
          src_dir: src/github.com/osism/ansible-collection-services
        topic: null
      job: ansible-collection-ensure-readme
      jobtags: []
      max_attempts: 3
      message: bmV0Ym94OiByZWNyZWF0ZSBjb250YWluZXJzIGFmdGVyIHB1bGxpbmcgbmV3IGltYWdlcwoKIyMgUHJvYmxlbQoKVGhlIGBQdWxsIGNvbnRhaW5lciBpbWFnZXNgIHRhc2sgaW4gYHJvbGVzL25ldGJveC90YXNrcy9zZXJ2aWNlLnltbGAgcHVsbHMgbmV3IGltYWdlcyBidXQgaGFzIG5vIGBub3RpZnlgL2ByZWdpc3RlcmAuIEEgcmVjcmVhdGUgKGBkb2NrZXIgY29tcG9zZSB1cCAtZGAsIHZpYSB0aGUgYFJlc3RhcnQgbmV0Ym94IHNlcnZpY2VgIGhhbmRsZXIgY2hhaW4pIGlzIG9ubHkgdHJpZ2dlcmVkIHdoZW4gdGhlIHJlbmRlcmVkIGBkb2NrZXItY29tcG9zZS55bWxgIGNoYW5nZXMgb3IgdGhlIHN5c3RlbWQgdW5pdCBjaGFuZ2VzLgoKT24gYSByb2xsaW5nLXRhZyB1cGRhdGUgKGUuZy4gYGxhdGVzdGAg4oaSIGBsYXRlc3RgKSB0aGUgY29tcG9zZSBmaWxlIHRleHQgaXMgaWRlbnRpY2FsIGFuZCB0aGUgc2VydmljZSBpcyBhbHJlYWR5IGFjdGl2ZSwgc28gbmVpdGhlciB0cmlnZ2VyIGZpcmVzIOKAlCB0aGUgZnJlc2hseSBwdWxsZWQgaW1hZ2UgaXMgZG93bmxvYWRlZCBidXQgdGhlIHJ1bm5pbmcgY29udGFpbmVyIGtlZXBzIHRoZSBvbGQgaW1hZ2UgKHdoaWNoIGhhcyBsb3N0IGl0cyBgOmxhdGVzdGAgdGFnKSB1bnRpbCB0aGUgbmV4dCBjb21wb3NlL3VuaXQgY2hhbmdlIG9yIGEgbWFudWFsIGBzeXN0ZW1jdGwgcmVzdGFydCBuZXRib3guc2VydmljZWAuCgojIyBGaXgKCk5vdGlmeSB0aGUgZXhpc3RpbmcgYFJlc3RhcnQgbmV0Ym94IHNlcnZpY2VgIGhhbmRsZXIgZnJvbSB0aGUgcHVsbCB0YXNrOgoKYGBgeWFtbAotIG5hbWU6IFB1bGwgY29udGFpbmVyIGltYWdlcwogIGNvbW11bml0eS5kb2NrZXIuZG9ja2VyX2NvbXBvc2VfdjJfcHVsbDoKICAgIHByb2plY3Rfc3JjOiAie3sgbmV0Ym94X2RvY2tlcl9jb21wb3NlX2RpcmVjdG9yeSB9fSIKICB3aGVuOiBuZXRib3hfcHJlX3B1bGwgfCBib29sCiAgcmV0cmllczogMwogIGRlbGF5OiAzMAogIG5vdGlmeTogUmVzdGFydCBuZXRib3ggc2VydmljZQpgYGAKClRoZSBub3RpZnkgb25seSBmaXJlcyB3aGVuIHRoZSBwdWxsIGFjdHVhbGx5IHJlcG9ydHMgYGNoYW5nZWRgOyB0aGUgaGFuZGxlciBjaGFpbiBlbmRzIGluIGBzZXJ2aWNlOiBzdGF0ZTogcmVzdGFydGVkYCDihpIgc3lzdGVtZCBgRXhlY1N0YXJ0PWRvY2tlciBjb21wb3NlIHVwIC0tcmVtb3ZlLW9ycGhhbnNgIOKGkiBjb250YWluZXJzIHJlY3JlYXRlZCB3aXRoIHRoZSBuZXcgaW1hZ2VzLiBUaGUgaGFuZGxlciBrZWVwcyByZXNwZWN0aW5nIGBuZXRib3hfc2VydmljZV9hbGxvd19yZXN0YXJ0YCwgYW5kIHRoZSBkdXBsaWNhdGUgbm90aWZ5IGZyb20gYENvcHkgZG9ja2VyLWNvbXBvc2UueW1sYCBzdGlsbCBjb2xsYXBzZXMgaW50byBhIHNpbmdsZSByZXN0YXJ0LgoKVGhpcyBtaXJyb3JzIHRoZSBtYW5hZ2VyLXJvbGUgZml4IGluICMyMTA2IChyb290IGNhdXNlICMyMTA1KS4KCkNsb3NlcyAjMjEwNw==
      patchset: 61d4d1bdf61d7fb55ebd19dba43e179c33391054
      pipeline: check
      playbook_context:
        playbook_projects:
          trusted/project_0/github.com/osism/zuul-config:
            canonical_name: github.com/osism/zuul-config
            checkout: main
            commit: 3d5c7b5973754999f7005857a00ce9168944f0f1
          trusted/project_1/github.com/osism/openinfra-zuul-jobs:
            canonical_name: github.com/osism/openinfra-zuul-jobs
            checkout: master
            commit: 038dd8b856c62af4433c8477c5cb3d0480847059
          trusted/project_2/github.com/osism/zuul-jobs:
            canonical_name: github.com/osism/zuul-jobs
            checkout: main
            commit: 0c74c57cedff2b36bb37ca68a5338d1c49991496
          untrusted/project_0/github.com/osism/zuul-jobs:
            canonical_name: github.com/osism/zuul-jobs
            checkout: main
            commit: 0c74c57cedff2b36bb37ca68a5338d1c49991496
          untrusted/project_1/github.com/osism/zuul-config:
            canonical_name: github.com/osism/zuul-config
            checkout: main
            commit: 3d5c7b5973754999f7005857a00ce9168944f0f1
          untrusted/project_2/github.com/osism/openinfra-zuul-jobs:
            canonical_name: github.com/osism/openinfra-zuul-jobs
            checkout: master
            commit: 038dd8b856c62af4433c8477c5cb3d0480847059
        playbooks:
        - path: untrusted/project_0/github.com/osism/zuul-jobs/playbooks/ansible-collection-ensure-readme/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/ansible-collection-services
        name: osism/ansible-collection-services
        short_name: ansible-collection-services
        src_dir: src/github.com/osism/ansible-collection-services
      projects:
        github.com/osism/ansible-collection-services:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-services
          checkout: main
          checkout_description: zuul branch
          commit: 748f757a38869f840db090175193b030ea4eca0e
          name: osism/ansible-collection-services
          required: false
          short_name: ansible-collection-services
          src_dir: src/github.com/osism/ansible-collection-services
      ref: refs/pull/2109/head
      resources: {}
      tenant: osism
      timeout: 1800
      topic: null
      voting: true
