all: children: zuul_unreachable: hosts: {} hosts: controller: ansible_connection: kubectl ansible_host: zuul-worker-ansible-0005523870 ansible_kubectl_context: main:zuul-worker/38-129-16-117:9023 ansible_port: null ansible_python_interpreter: /bin/python3 ansible_ssh_common_args: -o StrictHostKeyChecking=false ansible_user: zuul nodepool: az: null cloud: /sf-container-worker-1/ external_id: main-zuul-worker-ansible-0005523870 host_id: null interface_ip: zuul-worker-ansible-0005523870 label: zuul-worker-ansible private_ipv4: null private_ipv6: null provider: sf-container-worker-1 public_ipv4: null public_ipv6: null region: null slot: null zuul_use_fetch_output: true vars: zuul: _inheritance_path: - '' - '' - '' ansible_version: '8' attempts: 1 branch: main build: 225326445ebe4994a3df84f24cabccf8 build_refs: - branch: main change: '2346' change_message: "[WIP] vcenter_object_move: add module to move vCenter inventory object\n\n##### SUMMARY\r\nThis commit introduces the new module `vcenter_object_move` which allows moving vCenter inventory objects (e.g., Virtual Machines, Hosts, Datastores, Networks) into a specified destination folder. The module ensures idempotence by checking if the object is already located in the target folder and supports Ansible check mode for dry-run operations. This feature simplifies inventory management in vCenter environments and aids in maintaining an organized structure.\r\n\r\n##### ISSUE TYPE\r\n- New Module Pull Request\r\n\r\n##### COMPONENT NAME\r\nvcenter_object_move\r\n\r\n##### ADDITIONAL INFORMATION\r\nThe module leverages pyVmomi to interact with the vCenter API and integrates with the existing utilities from the `community.vmware` collection. It performs the following steps:\r\n1. Validates input parameters (datacenter, object_name, object_type, destination_folder).\r\n2. Locates the vCenter datacenter and the specified inventory object.\r\n3. Traverses the folder structure to locate the destination folder.\r\n4. Moves the object if it is not already in the target folder; if it is, no action is taken.\r\n5. Supports check mode to simulate the move without applying changes.\r\n\r\nExample command output:\r\n```paste below\r\n{\r\n \"changed\": true,\r\n \"msg\": \"Object 'MyVM' was successfully moved to folder 'NewFolder/SubFolder'.\"\r\n}\r\n" change_url: https://github.com/ansible-collections/community.vmware/pull/2346 commit_id: 753186a5aaa54aaf8d6cac2b5545fd5dbe3b5f93 patchset: 753186a5aaa54aaf8d6cac2b5545fd5dbe3b5f93 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: 8e815cbda12a476992bf87feca8a5b6d buildset_refs: - branch: main change: '2346' change_message: "[WIP] vcenter_object_move: add module to move vCenter inventory object\n\n##### SUMMARY\r\nThis commit introduces the new module `vcenter_object_move` which allows moving vCenter inventory objects (e.g., Virtual Machines, Hosts, Datastores, Networks) into a specified destination folder. The module ensures idempotence by checking if the object is already located in the target folder and supports Ansible check mode for dry-run operations. This feature simplifies inventory management in vCenter environments and aids in maintaining an organized structure.\r\n\r\n##### ISSUE TYPE\r\n- New Module Pull Request\r\n\r\n##### COMPONENT NAME\r\nvcenter_object_move\r\n\r\n##### ADDITIONAL INFORMATION\r\nThe module leverages pyVmomi to interact with the vCenter API and integrates with the existing utilities from the `community.vmware` collection. It performs the following steps:\r\n1. Validates input parameters (datacenter, object_name, object_type, destination_folder).\r\n2. Locates the vCenter datacenter and the specified inventory object.\r\n3. Traverses the folder structure to locate the destination folder.\r\n4. Moves the object if it is not already in the target folder; if it is, no action is taken.\r\n5. Supports check mode to simulate the move without applying changes.\r\n\r\nExample command output:\r\n```paste below\r\n{\r\n \"changed\": true,\r\n \"msg\": \"Object 'MyVM' was successfully moved to folder 'NewFolder/SubFolder'.\"\r\n}\r\n" change_url: https://github.com/ansible-collections/community.vmware/pull/2346 commit_id: 753186a5aaa54aaf8d6cac2b5545fd5dbe3b5f93 patchset: 753186a5aaa54aaf8d6cac2b5545fd5dbe3b5f93 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: '2346' change_message: "[WIP] vcenter_object_move: add module to move vCenter inventory object\n\n##### SUMMARY\r\nThis commit introduces the new module `vcenter_object_move` which allows moving vCenter inventory objects (e.g., Virtual Machines, Hosts, Datastores, Networks) into a specified destination folder. The module ensures idempotence by checking if the object is already located in the target folder and supports Ansible check mode for dry-run operations. This feature simplifies inventory management in vCenter environments and aids in maintaining an organized structure.\r\n\r\n##### ISSUE TYPE\r\n- New Module Pull Request\r\n\r\n##### COMPONENT NAME\r\nvcenter_object_move\r\n\r\n##### ADDITIONAL INFORMATION\r\nThe module leverages pyVmomi to interact with the vCenter API and integrates with the existing utilities from the `community.vmware` collection. It performs the following steps:\r\n1. Validates input parameters (datacenter, object_name, object_type, destination_folder).\r\n2. Locates the vCenter datacenter and the specified inventory object.\r\n3. Traverses the folder structure to locate the destination folder.\r\n4. Moves the object if it is not already in the target folder; if it is, no action is taken.\r\n5. Supports check mode to simulate the move without applying changes.\r\n\r\nExample command output:\r\n```paste below\r\n{\r\n \"changed\": true,\r\n \"msg\": \"Object 'MyVM' was successfully moved to folder 'NewFolder/SubFolder'.\"\r\n}\r\n" change_url: https://github.com/ansible-collections/community.vmware/pull/2346 child_jobs: - ansible-galaxy-importer commit_id: 753186a5aaa54aaf8d6cac2b5545fd5dbe3b5f93 event_id: 42bd2ad0-c26e-11f0-9173-7bd119af4009 executor: hostname: ze04.softwarefactory-project.io inventory_file: /var/lib/zuul/builds/225326445ebe4994a3df84f24cabccf8/ansible/inventory.yaml log_root: /var/lib/zuul/builds/225326445ebe4994a3df84f24cabccf8/work/logs result_data_file: /var/lib/zuul/builds/225326445ebe4994a3df84f24cabccf8/work/results.json src_root: /var/lib/zuul/builds/225326445ebe4994a3df84f24cabccf8/work/src work_root: /var/lib/zuul/builds/225326445ebe4994a3df84f24cabccf8/work items: - branch: main change: '2346' change_message: "[WIP] vcenter_object_move: add module to move vCenter inventory object\n\n##### SUMMARY\r\nThis commit introduces the new module `vcenter_object_move` which allows moving vCenter inventory objects (e.g., Virtual Machines, Hosts, Datastores, Networks) into a specified destination folder. The module ensures idempotence by checking if the object is already located in the target folder and supports Ansible check mode for dry-run operations. This feature simplifies inventory management in vCenter environments and aids in maintaining an organized structure.\r\n\r\n##### ISSUE TYPE\r\n- New Module Pull Request\r\n\r\n##### COMPONENT NAME\r\nvcenter_object_move\r\n\r\n##### ADDITIONAL INFORMATION\r\nThe module leverages pyVmomi to interact with the vCenter API and integrates with the existing utilities from the `community.vmware` collection. It performs the following steps:\r\n1. Validates input parameters (datacenter, object_name, object_type, destination_folder).\r\n2. Locates the vCenter datacenter and the specified inventory object.\r\n3. Traverses the folder structure to locate the destination folder.\r\n4. Moves the object if it is not already in the target folder; if it is, no action is taken.\r\n5. Supports check mode to simulate the move without applying changes.\r\n\r\nExample command output:\r\n```paste below\r\n{\r\n \"changed\": true,\r\n \"msg\": \"Object 'MyVM' was successfully moved to folder 'NewFolder/SubFolder'.\"\r\n}\r\n" change_url: https://github.com/ansible-collections/community.vmware/pull/2346 commit_id: 753186a5aaa54aaf8d6cac2b5545fd5dbe3b5f93 patchset: 753186a5aaa54aaf8d6cac2b5545fd5dbe3b5f93 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: build-ansible-collection jobtags: [] max_attempts: 3 message: W1dJUF0gdmNlbnRlcl9vYmplY3RfbW92ZTogYWRkIG1vZHVsZSB0byBtb3ZlIHZDZW50ZXIgaW52ZW50b3J5IG9iamVjdAoKIyMjIyMgU1VNTUFSWQ0KVGhpcyBjb21taXQgaW50cm9kdWNlcyB0aGUgbmV3IG1vZHVsZSBgdmNlbnRlcl9vYmplY3RfbW92ZWAgd2hpY2ggYWxsb3dzIG1vdmluZyB2Q2VudGVyIGludmVudG9yeSBvYmplY3RzIChlLmcuLCBWaXJ0dWFsIE1hY2hpbmVzLCBIb3N0cywgRGF0YXN0b3JlcywgTmV0d29ya3MpIGludG8gYSBzcGVjaWZpZWQgZGVzdGluYXRpb24gZm9sZGVyLiBUaGUgbW9kdWxlIGVuc3VyZXMgaWRlbXBvdGVuY2UgYnkgY2hlY2tpbmcgaWYgdGhlIG9iamVjdCBpcyBhbHJlYWR5IGxvY2F0ZWQgaW4gdGhlIHRhcmdldCBmb2xkZXIgYW5kIHN1cHBvcnRzIEFuc2libGUgY2hlY2sgbW9kZSBmb3IgZHJ5LXJ1biBvcGVyYXRpb25zLiBUaGlzIGZlYXR1cmUgc2ltcGxpZmllcyBpbnZlbnRvcnkgbWFuYWdlbWVudCBpbiB2Q2VudGVyIGVudmlyb25tZW50cyBhbmQgYWlkcyBpbiBtYWludGFpbmluZyBhbiBvcmdhbml6ZWQgc3RydWN0dXJlLg0KDQojIyMjIyBJU1NVRSBUWVBFDQotIE5ldyBNb2R1bGUgUHVsbCBSZXF1ZXN0DQoNCiMjIyMjIENPTVBPTkVOVCBOQU1FDQp2Y2VudGVyX29iamVjdF9tb3ZlDQoNCiMjIyMjIEFERElUSU9OQUwgSU5GT1JNQVRJT04NClRoZSBtb2R1bGUgbGV2ZXJhZ2VzIHB5Vm1vbWkgdG8gaW50ZXJhY3Qgd2l0aCB0aGUgdkNlbnRlciBBUEkgYW5kIGludGVncmF0ZXMgd2l0aCB0aGUgZXhpc3RpbmcgdXRpbGl0aWVzIGZyb20gdGhlIGBjb21tdW5pdHkudm13YXJlYCBjb2xsZWN0aW9uLiBJdCBwZXJmb3JtcyB0aGUgZm9sbG93aW5nIHN0ZXBzOg0KMS4gVmFsaWRhdGVzIGlucHV0IHBhcmFtZXRlcnMgKGRhdGFjZW50ZXIsIG9iamVjdF9uYW1lLCBvYmplY3RfdHlwZSwgZGVzdGluYXRpb25fZm9sZGVyKS4NCjIuIExvY2F0ZXMgdGhlIHZDZW50ZXIgZGF0YWNlbnRlciBhbmQgdGhlIHNwZWNpZmllZCBpbnZlbnRvcnkgb2JqZWN0Lg0KMy4gVHJhdmVyc2VzIHRoZSBmb2xkZXIgc3RydWN0dXJlIHRvIGxvY2F0ZSB0aGUgZGVzdGluYXRpb24gZm9sZGVyLg0KNC4gTW92ZXMgdGhlIG9iamVjdCBpZiBpdCBpcyBub3QgYWxyZWFkeSBpbiB0aGUgdGFyZ2V0IGZvbGRlcjsgaWYgaXQgaXMsIG5vIGFjdGlvbiBpcyB0YWtlbi4NCjUuIFN1cHBvcnRzIGNoZWNrIG1vZGUgdG8gc2ltdWxhdGUgdGhlIG1vdmUgd2l0aG91dCBhcHBseWluZyBjaGFuZ2VzLg0KDQpFeGFtcGxlIGNvbW1hbmQgb3V0cHV0Og0KYGBgcGFzdGUgYmVsb3cNCnsNCiAgICAiY2hhbmdlZCI6IHRydWUsDQogICAgIm1zZyI6ICJPYmplY3QgJ015Vk0nIHdhcyBzdWNjZXNzZnVsbHkgbW92ZWQgdG8gZm9sZGVyICdOZXdGb2xkZXIvU3ViRm9sZGVyJy4iDQp9DQo= patchset: 753186a5aaa54aaf8d6cac2b5545fd5dbe3b5f93 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: 3e667f4d3a5f14620cbe10b052c77698fa883471 trusted/project_1/opendev.org/zuul/zuul-jobs: canonical_name: opendev.org/zuul/zuul-jobs checkout: master commit: ca9686a93bf15ac1c0497871dba7eb1018c93d4e 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: 3e667f4d3a5f14620cbe10b052c77698fa883471 untrusted/project_2/opendev.org/zuul/zuul-jobs: canonical_name: opendev.org/zuul/zuul-jobs checkout: master commit: ca9686a93bf15ac1c0497871dba7eb1018c93d4e playbooks: - path: untrusted/project_0/github.com/ansible/ansible-zuul-jobs/playbooks/build-ansible-collection/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: 60e0254f4cca30286d6acffd9ab21ca4324802fc 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/2346/head resources: controller: context: main:zuul-worker/38-129-16-117:9023 namespace: main pod: zuul-worker-ansible-0005523870 stream_port: '46569' tenant: ansible timeout: 1800 topic: null voting: true zuul_use_fetch_output: true