all: children: zuul_unreachable: hosts: {} hosts: controller: ansible_connection: ssh ansible_host: 162.253.55.43 ansible_port: 22 ansible_python_interpreter: auto ansible_user: zuul nodepool: az: nova cloud: ansible-vexxhost external_id: 007f82fe-b7cc-4b62-a17c-094e90db5f8e host_id: 6b8d58a114f50c983ebf6931b748184c76907eec51ac86ada773f491 interface_ip: 162.253.55.43 label: ansible-fedora-37-1vcpu private_ipv4: 192.168.0.163 private_ipv6: null provider: ansible-vexxhost-ca-ymq-1 public_ipv4: 162.253.55.43 public_ipv6: 2604:e100:1:0:f816:3eff:fe3a:6bc3 region: ca-ymq-1 slot: null zuul_use_fetch_output: true vars: zuul: _inheritance_path: - '' - '' - '' - '' ansible_version: '8' artifacts: - branch: main change: '2534' job: build-ansible-collection metadata: type: zuul_manifest name: Zuul Manifest patchset: 144359f93506e58000ffd04362b17e0f68757acc project: ansible-collections/community.vmware url: https://7109a2abc523f6f99405-29bde77de8ea30cd780d5189e2fe8004.ssl.cf1.rackcdn.com/ansible/c71706b18f2545018dd8fc5ef7493f5a/zuul-manifest.json - branch: main change: '2534' job: build-ansible-collection metadata: type: ansible_collection version: 6.2.0 name: community.vmware patchset: 144359f93506e58000ffd04362b17e0f68757acc project: ansible-collections/community.vmware url: https://7109a2abc523f6f99405-29bde77de8ea30cd780d5189e2fe8004.ssl.cf1.rackcdn.com/ansible/c71706b18f2545018dd8fc5ef7493f5a/artifacts/community-vmware-6.2.0.tar.gz attempts: 1 branch: main build: 9beba899261e4349b7f2fbed3713a050 build_refs: - branch: main change: '2534' change_message: "vmware_guest: Allow modifying hardware when cloning a template which is powered on\n\n##### SUMMARY\r\nThis change allows modifying of hardware resources (cpu, memory, etc.) when cloning a template which is powered on.\r\n\r\nThe hardware modifications are safe as cloning a template which is powered on will create a vm which is powered off. The module later powers on the cloned vm.\r\n\r\n##### ISSUE TYPE\r\n- Bugfix Pull Request\r\n\r\n##### COMPONENT NAME\r\nvmware_guest\r\n\r\n##### ADDITIONAL INFORMATION\r\nOne can reproduce this behaviour by creating a template and starting it. Then clone this template with the `vmware_guest` module using other hardware resources than the template. For example, if the template has `4096` MB memory, the hardware.memory_mb parameter should use another value (e. g. `2048`).\r\n\r\nIn this example we would get the error `memoryHotAdd is not enabled`.\r\n\r\nAfter this change, the vm is successfully cloned." change_url: https://github.com/ansible-collections/community.vmware/pull/2534 commit_id: 144359f93506e58000ffd04362b17e0f68757acc patchset: 144359f93506e58000ffd04362b17e0f68757acc project: canonical_hostname: github.com canonical_name: github.com/ansible-collections/community.vmware name: ansible-collections/community.vmware short_name: community.vmware src_dir: src/github.com/ansible-collections/community.vmware topic: null buildset: 622c8d3b8f2b49c286384de3108f4e8b buildset_refs: - branch: main change: '2534' change_message: "vmware_guest: Allow modifying hardware when cloning a template which is powered on\n\n##### SUMMARY\r\nThis change allows modifying of hardware resources (cpu, memory, etc.) when cloning a template which is powered on.\r\n\r\nThe hardware modifications are safe as cloning a template which is powered on will create a vm which is powered off. The module later powers on the cloned vm.\r\n\r\n##### ISSUE TYPE\r\n- Bugfix Pull Request\r\n\r\n##### COMPONENT NAME\r\nvmware_guest\r\n\r\n##### ADDITIONAL INFORMATION\r\nOne can reproduce this behaviour by creating a template and starting it. Then clone this template with the `vmware_guest` module using other hardware resources than the template. For example, if the template has `4096` MB memory, the hardware.memory_mb parameter should use another value (e. g. `2048`).\r\n\r\nIn this example we would get the error `memoryHotAdd is not enabled`.\r\n\r\nAfter this change, the vm is successfully cloned." change_url: https://github.com/ansible-collections/community.vmware/pull/2534 commit_id: 144359f93506e58000ffd04362b17e0f68757acc patchset: 144359f93506e58000ffd04362b17e0f68757acc project: canonical_hostname: github.com canonical_name: github.com/ansible-collections/community.vmware name: ansible-collections/community.vmware short_name: community.vmware src_dir: src/github.com/ansible-collections/community.vmware topic: null change: '2534' change_message: "vmware_guest: Allow modifying hardware when cloning a template which is powered on\n\n##### SUMMARY\r\nThis change allows modifying of hardware resources (cpu, memory, etc.) when cloning a template which is powered on.\r\n\r\nThe hardware modifications are safe as cloning a template which is powered on will create a vm which is powered off. The module later powers on the cloned vm.\r\n\r\n##### ISSUE TYPE\r\n- Bugfix Pull Request\r\n\r\n##### COMPONENT NAME\r\nvmware_guest\r\n\r\n##### ADDITIONAL INFORMATION\r\nOne can reproduce this behaviour by creating a template and starting it. Then clone this template with the `vmware_guest` module using other hardware resources than the template. For example, if the template has `4096` MB memory, the hardware.memory_mb parameter should use another value (e. g. `2048`).\r\n\r\nIn this example we would get the error `memoryHotAdd is not enabled`.\r\n\r\nAfter this change, the vm is successfully cloned." change_url: https://github.com/ansible-collections/community.vmware/pull/2534 child_jobs: [] commit_id: 144359f93506e58000ffd04362b17e0f68757acc event_id: ce600ff0-f138-11f0-98f2-29c088d3ba46 executor: hostname: ze03.softwarefactory-project.io inventory_file: /var/lib/zuul/builds/9beba899261e4349b7f2fbed3713a050/ansible/inventory.yaml log_root: /var/lib/zuul/builds/9beba899261e4349b7f2fbed3713a050/work/logs result_data_file: /var/lib/zuul/builds/9beba899261e4349b7f2fbed3713a050/work/results.json src_root: /var/lib/zuul/builds/9beba899261e4349b7f2fbed3713a050/work/src work_root: /var/lib/zuul/builds/9beba899261e4349b7f2fbed3713a050/work items: - branch: main change: '2534' change_message: "vmware_guest: Allow modifying hardware when cloning a template which is powered on\n\n##### SUMMARY\r\nThis change allows modifying of hardware resources (cpu, memory, etc.) when cloning a template which is powered on.\r\n\r\nThe hardware modifications are safe as cloning a template which is powered on will create a vm which is powered off. The module later powers on the cloned vm.\r\n\r\n##### ISSUE TYPE\r\n- Bugfix Pull Request\r\n\r\n##### COMPONENT NAME\r\nvmware_guest\r\n\r\n##### ADDITIONAL INFORMATION\r\nOne can reproduce this behaviour by creating a template and starting it. Then clone this template with the `vmware_guest` module using other hardware resources than the template. For example, if the template has `4096` MB memory, the hardware.memory_mb parameter should use another value (e. g. `2048`).\r\n\r\nIn this example we would get the error `memoryHotAdd is not enabled`.\r\n\r\nAfter this change, the vm is successfully cloned." change_url: https://github.com/ansible-collections/community.vmware/pull/2534 commit_id: 144359f93506e58000ffd04362b17e0f68757acc patchset: 144359f93506e58000ffd04362b17e0f68757acc project: canonical_hostname: github.com canonical_name: github.com/ansible-collections/community.vmware name: ansible-collections/community.vmware short_name: community.vmware src_dir: src/github.com/ansible-collections/community.vmware topic: null job: ansible-galaxy-importer jobtags: [] max_attempts: 3 message: dm13YXJlX2d1ZXN0OiBBbGxvdyBtb2RpZnlpbmcgaGFyZHdhcmUgd2hlbiBjbG9uaW5nIGEgdGVtcGxhdGUgd2hpY2ggaXMgcG93ZXJlZCBvbgoKIyMjIyMgU1VNTUFSWQ0KVGhpcyBjaGFuZ2UgYWxsb3dzIG1vZGlmeWluZyBvZiBoYXJkd2FyZSByZXNvdXJjZXMgKGNwdSwgbWVtb3J5LCBldGMuKSB3aGVuIGNsb25pbmcgYSB0ZW1wbGF0ZSB3aGljaCBpcyBwb3dlcmVkIG9uLg0KDQpUaGUgaGFyZHdhcmUgbW9kaWZpY2F0aW9ucyBhcmUgc2FmZSBhcyBjbG9uaW5nIGEgdGVtcGxhdGUgd2hpY2ggaXMgcG93ZXJlZCBvbiB3aWxsIGNyZWF0ZSBhIHZtIHdoaWNoIGlzIHBvd2VyZWQgb2ZmLiBUaGUgbW9kdWxlIGxhdGVyIHBvd2VycyBvbiB0aGUgY2xvbmVkIHZtLg0KDQojIyMjIyBJU1NVRSBUWVBFDQotIEJ1Z2ZpeCBQdWxsIFJlcXVlc3QNCg0KIyMjIyMgQ09NUE9ORU5UIE5BTUUNCnZtd2FyZV9ndWVzdA0KDQojIyMjIyBBRERJVElPTkFMIElORk9STUFUSU9ODQpPbmUgY2FuIHJlcHJvZHVjZSB0aGlzIGJlaGF2aW91ciBieSBjcmVhdGluZyBhIHRlbXBsYXRlIGFuZCBzdGFydGluZyBpdC4gVGhlbiBjbG9uZSB0aGlzIHRlbXBsYXRlIHdpdGggdGhlIGB2bXdhcmVfZ3Vlc3RgIG1vZHVsZSB1c2luZyBvdGhlciBoYXJkd2FyZSByZXNvdXJjZXMgdGhhbiB0aGUgdGVtcGxhdGUuIEZvciBleGFtcGxlLCBpZiB0aGUgdGVtcGxhdGUgaGFzIGA0MDk2YCBNQiBtZW1vcnksIHRoZSBoYXJkd2FyZS5tZW1vcnlfbWIgcGFyYW1ldGVyIHNob3VsZCB1c2UgYW5vdGhlciB2YWx1ZSAoZS4gZy4gYDIwNDhgKS4NCg0KSW4gdGhpcyBleGFtcGxlIHdlIHdvdWxkIGdldCB0aGUgZXJyb3IgYG1lbW9yeUhvdEFkZCBpcyBub3QgZW5hYmxlZGAuDQoNCkFmdGVyIHRoaXMgY2hhbmdlLCB0aGUgdm0gaXMgc3VjY2Vzc2Z1bGx5IGNsb25lZC4= patchset: 144359f93506e58000ffd04362b17e0f68757acc pipeline: third-party-check playbook_context: playbook_projects: trusted/project_0/github.com/ansible/zuul-config: canonical_name: github.com/ansible/zuul-config checkout: master commit: 6303810c5fc44be3b18d2561af41581d5d7c3359 trusted/project_1/opendev.org/zuul/zuul-jobs: canonical_name: opendev.org/zuul/zuul-jobs checkout: master commit: 691c03cc007bee9934da14cf46c86009616a2aef untrusted/project_0/github.com/ansible/ansible-zuul-jobs: canonical_name: github.com/ansible/ansible-zuul-jobs checkout: master commit: e7ff49de526383ec1701720d6aed921160ec3931 untrusted/project_1/github.com/ansible/zuul-config: canonical_name: github.com/ansible/zuul-config checkout: master commit: 6303810c5fc44be3b18d2561af41581d5d7c3359 untrusted/project_2/opendev.org/zuul/zuul-jobs: canonical_name: opendev.org/zuul/zuul-jobs checkout: master commit: 691c03cc007bee9934da14cf46c86009616a2aef playbooks: - path: untrusted/project_0/github.com/ansible/ansible-zuul-jobs/playbooks/ansible-galaxy-importer/run.yaml roles: - checkout: master checkout_description: playbook branch link_name: ansible/playbook_0/role_0/zuul-jobs link_target: untrusted/project_0/github.com/ansible/ansible-zuul-jobs role_path: ansible/playbook_0/role_0/zuul-jobs/roles - checkout: master checkout_description: project default branch link_name: ansible/playbook_0/role_1/zuul-config link_target: untrusted/project_1/github.com/ansible/zuul-config role_path: ansible/playbook_0/role_1/zuul-config/roles - checkout: master checkout_description: project default branch link_name: ansible/playbook_0/role_2/zuul-jobs link_target: untrusted/project_2/opendev.org/zuul/zuul-jobs role_path: ansible/playbook_0/role_2/zuul-jobs/roles post_review: false project: canonical_hostname: github.com canonical_name: github.com/ansible-collections/community.vmware name: ansible-collections/community.vmware short_name: community.vmware src_dir: src/github.com/ansible-collections/community.vmware projects: github.com/ansible-collections/community.vmware: canonical_hostname: github.com canonical_name: github.com/ansible-collections/community.vmware checkout: main checkout_description: zuul branch commit: 1c11bdb59208daa4d6dc94020169a95b21da11aa name: ansible-collections/community.vmware required: false short_name: community.vmware src_dir: src/github.com/ansible-collections/community.vmware github.com/ansible-network/releases: canonical_hostname: github.com canonical_name: github.com/ansible-network/releases checkout: master checkout_description: project default branch commit: 646b310655c531e4904be07f4ff8fc3a29addd09 name: ansible-network/releases required: true short_name: releases src_dir: src/github.com/ansible-network/releases ref: refs/pull/2534/head resources: {} tenant: ansible timeout: 1800 topic: null voting: false zuul_use_fetch_output: true