all: children: zuul_unreachable: hosts: {} hosts: controller: ansible_connection: ssh ansible_host: 162.253.55.204 ansible_port: 22 ansible_python_interpreter: auto ansible_user: zuul nodepool: az: nova cloud: ansible-vexxhost external_id: 6426475a-f049-44b6-8b3a-53eeb43be16f host_id: 255e89a37b31d8382bf95f3b683f2848cfbe15cdca14e2955b593ebe interface_ip: 162.253.55.204 label: ansible-fedora-37-1vcpu private_ipv4: 192.168.0.106 private_ipv6: null provider: ansible-vexxhost-ca-ymq-1 public_ipv4: 162.253.55.204 public_ipv6: 2604:e100:1:0:f816:3eff:feca:f140 region: ca-ymq-1 slot: null zuul_use_fetch_output: true vars: zuul: _inheritance_path: - '' - '' - '' ansible_version: '8' artifacts: - branch: dev change: '1149' job: build-ansible-collection metadata: type: zuul_manifest name: Zuul Manifest patchset: 925bc7b551e6283cb1590be5aed96824d96870aa project: sap-linuxlab/community.sap_install url: https://00032543bf38c4d31a06-ea3b3444f219601deb357124ea002294.ssl.cf5.rackcdn.com/ansible/896abd05e0d3428f92b435da68520e04/zuul-manifest.json - branch: dev change: '1149' job: build-ansible-collection metadata: type: ansible_collection version: 1.8.1 name: community.sap_install patchset: 925bc7b551e6283cb1590be5aed96824d96870aa project: sap-linuxlab/community.sap_install url: https://00032543bf38c4d31a06-ea3b3444f219601deb357124ea002294.ssl.cf5.rackcdn.com/ansible/896abd05e0d3428f92b435da68520e04/artifacts/community-sap_install-1.8.1.tar.gz attempts: 1 branch: dev build: 9578417beca248d1b83c32095319a8a2 build_refs: - branch: dev change: '1149' change_message: "sap_swpm: Allow user defined environment variables when executing swpm\n\nThis PR adds relatively simple functionality to SWPM which allows custom defined environment shell variables to be set before executing SWPM. This is something we have briefly discussed @berndfinger more than a year ago.\r\n\r\nRationale:\r\n- Many production systems have noexec and nosuid flag set /tmp filesystem which is preventing SWPM from starting. As per SAP Notes [3651688](http://me.sap.com/notes/3651688) and [2063079](http://me.sap.com/notes/2063079) solution is to set TMP environment variable to a more suitable location.\r\n- Some database libraries e.g. for DB/2 zOS require environment variables to be set during installation (e.g. sdb_ssfs_connect).\r\n\r\nThis change makes a generic provision to define any helpful environment variables.\r\n\r\n @marcelmamula @berndfinger @sean-freeman the variable is currently called sap_swpm_swpm_env_vars which is in-line with the naming convention used in this role (e.g. `sap_swpm_swpm_installation_type: , sap_swpm_swpm_installation_header: \ sap_swpm_swpm_command_virtual_hostname:, sap_swpm_swpm_command_mp_stack:` etc). If you want to start moving towards a different naming convention, happy to change it, but I am mentioning it because Marcel had concerns about the name of this variable.\r\n" change_url: https://github.com/sap-linuxlab/community.sap_install/pull/1149 commit_id: 925bc7b551e6283cb1590be5aed96824d96870aa patchset: 925bc7b551e6283cb1590be5aed96824d96870aa project: canonical_hostname: github.com canonical_name: github.com/sap-linuxlab/community.sap_install name: sap-linuxlab/community.sap_install short_name: community.sap_install src_dir: src/github.com/sap-linuxlab/community.sap_install topic: null buildset: 7ee426e965cc4e74a30df663b8614105 buildset_refs: - branch: dev change: '1149' change_message: "sap_swpm: Allow user defined environment variables when executing swpm\n\nThis PR adds relatively simple functionality to SWPM which allows custom defined environment shell variables to be set before executing SWPM. This is something we have briefly discussed @berndfinger more than a year ago.\r\n\r\nRationale:\r\n- Many production systems have noexec and nosuid flag set /tmp filesystem which is preventing SWPM from starting. As per SAP Notes [3651688](http://me.sap.com/notes/3651688) and [2063079](http://me.sap.com/notes/2063079) solution is to set TMP environment variable to a more suitable location.\r\n- Some database libraries e.g. for DB/2 zOS require environment variables to be set during installation (e.g. sdb_ssfs_connect).\r\n\r\nThis change makes a generic provision to define any helpful environment variables.\r\n\r\n @marcelmamula @berndfinger @sean-freeman the variable is currently called sap_swpm_swpm_env_vars which is in-line with the naming convention used in this role (e.g. `sap_swpm_swpm_installation_type: , sap_swpm_swpm_installation_header: \ sap_swpm_swpm_command_virtual_hostname:, sap_swpm_swpm_command_mp_stack:` etc). If you want to start moving towards a different naming convention, happy to change it, but I am mentioning it because Marcel had concerns about the name of this variable.\r\n" change_url: https://github.com/sap-linuxlab/community.sap_install/pull/1149 commit_id: 925bc7b551e6283cb1590be5aed96824d96870aa patchset: 925bc7b551e6283cb1590be5aed96824d96870aa project: canonical_hostname: github.com canonical_name: github.com/sap-linuxlab/community.sap_install name: sap-linuxlab/community.sap_install short_name: community.sap_install src_dir: src/github.com/sap-linuxlab/community.sap_install topic: null change: '1149' change_message: "sap_swpm: Allow user defined environment variables when executing swpm\n\nThis PR adds relatively simple functionality to SWPM which allows custom defined environment shell variables to be set before executing SWPM. This is something we have briefly discussed @berndfinger more than a year ago.\r\n\r\nRationale:\r\n- Many production systems have noexec and nosuid flag set /tmp filesystem which is preventing SWPM from starting. As per SAP Notes [3651688](http://me.sap.com/notes/3651688) and [2063079](http://me.sap.com/notes/2063079) solution is to set TMP environment variable to a more suitable location.\r\n- Some database libraries e.g. for DB/2 zOS require environment variables to be set during installation (e.g. sdb_ssfs_connect).\r\n\r\nThis change makes a generic provision to define any helpful environment variables.\r\n\r\n @marcelmamula @berndfinger @sean-freeman the variable is currently called sap_swpm_swpm_env_vars which is in-line with the naming convention used in this role (e.g. `sap_swpm_swpm_installation_type: , sap_swpm_swpm_installation_header: sap_swpm_swpm_command_virtual_hostname:, sap_swpm_swpm_command_mp_stack:` etc). If you want to start moving towards a different naming convention, happy to change it, but I am mentioning it because Marcel had concerns about the name of this variable.\r\n" change_url: https://github.com/sap-linuxlab/community.sap_install/pull/1149 child_jobs: [] commit_id: 925bc7b551e6283cb1590be5aed96824d96870aa event_id: e798a470-08fb-11f1-930a-62c5462886c2 executor: hostname: ze01.softwarefactory-project.io inventory_file: /var/lib/zuul/builds/9578417beca248d1b83c32095319a8a2/ansible/inventory.yaml log_root: /var/lib/zuul/builds/9578417beca248d1b83c32095319a8a2/work/logs result_data_file: /var/lib/zuul/builds/9578417beca248d1b83c32095319a8a2/work/results.json src_root: /var/lib/zuul/builds/9578417beca248d1b83c32095319a8a2/work/src work_root: /var/lib/zuul/builds/9578417beca248d1b83c32095319a8a2/work items: - branch: dev change: '1149' change_message: "sap_swpm: Allow user defined environment variables when executing swpm\n\nThis PR adds relatively simple functionality to SWPM which allows custom defined environment shell variables to be set before executing SWPM. This is something we have briefly discussed @berndfinger more than a year ago.\r\n\r\nRationale:\r\n- Many production systems have noexec and nosuid flag set /tmp filesystem which is preventing SWPM from starting. As per SAP Notes [3651688](http://me.sap.com/notes/3651688) and [2063079](http://me.sap.com/notes/2063079) solution is to set TMP environment variable to a more suitable location.\r\n- Some database libraries e.g. for DB/2 zOS require environment variables to be set during installation (e.g. sdb_ssfs_connect).\r\n\r\nThis change makes a generic provision to define any helpful environment variables.\r\n\r\n @marcelmamula @berndfinger @sean-freeman the variable is currently called sap_swpm_swpm_env_vars which is in-line with the naming convention used in this role (e.g. `sap_swpm_swpm_installation_type: , sap_swpm_swpm_installation_header: \ sap_swpm_swpm_command_virtual_hostname:, sap_swpm_swpm_command_mp_stack:` etc). If you want to start moving towards a different naming convention, happy to change it, but I am mentioning it because Marcel had concerns about the name of this variable.\r\n" change_url: https://github.com/sap-linuxlab/community.sap_install/pull/1149 commit_id: 925bc7b551e6283cb1590be5aed96824d96870aa patchset: 925bc7b551e6283cb1590be5aed96824d96870aa project: canonical_hostname: github.com canonical_name: github.com/sap-linuxlab/community.sap_install name: sap-linuxlab/community.sap_install short_name: community.sap_install src_dir: src/github.com/sap-linuxlab/community.sap_install topic: null job: ansible-galaxy-importer jobtags: [] max_attempts: 3 message: c2FwX3N3cG06IEFsbG93IHVzZXIgZGVmaW5lZCBlbnZpcm9ubWVudCB2YXJpYWJsZXMgd2hlbiBleGVjdXRpbmcgc3dwbQoKVGhpcyBQUiBhZGRzIHJlbGF0aXZlbHkgc2ltcGxlIGZ1bmN0aW9uYWxpdHkgdG8gU1dQTSB3aGljaCBhbGxvd3MgY3VzdG9tIGRlZmluZWQgZW52aXJvbm1lbnQgc2hlbGwgdmFyaWFibGVzIHRvIGJlIHNldCBiZWZvcmUgZXhlY3V0aW5nIFNXUE0uIFRoaXMgaXMgc29tZXRoaW5nIHdlIGhhdmUgYnJpZWZseSBkaXNjdXNzZWQgQGJlcm5kZmluZ2VyIG1vcmUgdGhhbiBhIHllYXIgYWdvLg0KDQpSYXRpb25hbGU6DQotIE1hbnkgcHJvZHVjdGlvbiBzeXN0ZW1zIGhhdmUgbm9leGVjIGFuZCBub3N1aWQgZmxhZyBzZXQgL3RtcCBmaWxlc3lzdGVtIHdoaWNoIGlzIHByZXZlbnRpbmcgU1dQTSBmcm9tIHN0YXJ0aW5nLiBBcyBwZXIgU0FQIE5vdGVzIFszNjUxNjg4XShodHRwOi8vbWUuc2FwLmNvbS9ub3Rlcy8zNjUxNjg4KSBhbmQgWzIwNjMwNzldKGh0dHA6Ly9tZS5zYXAuY29tL25vdGVzLzIwNjMwNzkpIHNvbHV0aW9uIGlzIHRvIHNldCBUTVAgZW52aXJvbm1lbnQgdmFyaWFibGUgdG8gYSBtb3JlIHN1aXRhYmxlIGxvY2F0aW9uLg0KLSBTb21lIGRhdGFiYXNlIGxpYnJhcmllcyBlLmcuIGZvciBEQi8yIHpPUyByZXF1aXJlIGVudmlyb25tZW50IHZhcmlhYmxlcyB0byBiZSBzZXQgZHVyaW5nIGluc3RhbGxhdGlvbiAoZS5nLiBzZGJfc3Nmc19jb25uZWN0KS4NCg0KVGhpcyBjaGFuZ2UgbWFrZXMgYSBnZW5lcmljIHByb3Zpc2lvbiB0byBkZWZpbmUgYW55IGhlbHBmdWwgZW52aXJvbm1lbnQgdmFyaWFibGVzLg0KDQogQG1hcmNlbG1hbXVsYSBAYmVybmRmaW5nZXIgQHNlYW4tZnJlZW1hbiB0aGUgdmFyaWFibGUgaXMgY3VycmVudGx5IGNhbGxlZCBzYXBfc3dwbV9zd3BtX2Vudl92YXJzIHdoaWNoIGlzIGluLWxpbmUgd2l0aCB0aGUgbmFtaW5nIGNvbnZlbnRpb24gdXNlZCBpbiB0aGlzIHJvbGUgKGUuZy4gYHNhcF9zd3BtX3N3cG1faW5zdGFsbGF0aW9uX3R5cGU6ICwgc2FwX3N3cG1fc3dwbV9pbnN0YWxsYXRpb25faGVhZGVyOiAgICAgc2FwX3N3cG1fc3dwbV9jb21tYW5kX3ZpcnR1YWxfaG9zdG5hbWU6LCBzYXBfc3dwbV9zd3BtX2NvbW1hbmRfbXBfc3RhY2s6YCBldGMpLiBJZiB5b3Ugd2FudCB0byBzdGFydCBtb3ZpbmcgdG93YXJkcyBhIGRpZmZlcmVudCBuYW1pbmcgY29udmVudGlvbiwgaGFwcHkgdG8gY2hhbmdlIGl0LCBidXQgSSBhbSBtZW50aW9uaW5nIGl0IGJlY2F1c2UgTWFyY2VsIGhhZCBjb25jZXJucyBhYm91dCB0aGUgbmFtZSBvZiB0aGlzIHZhcmlhYmxlLg0K patchset: 925bc7b551e6283cb1590be5aed96824d96870aa 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: 136c2ca4768bb203c1d07eb9abd7f696213921b6 trusted/project_1/opendev.org/zuul/zuul-jobs: canonical_name: opendev.org/zuul/zuul-jobs checkout: master commit: 571c0efa3491d12ecb8fc1169c510716d55c0fc2 untrusted/project_0/github.com/ansible/ansible-zuul-jobs: canonical_name: github.com/ansible/ansible-zuul-jobs checkout: master commit: 192320b9d41936ac6065fcaf6e286bf4dca783a5 untrusted/project_1/github.com/ansible/zuul-config: canonical_name: github.com/ansible/zuul-config checkout: master commit: 136c2ca4768bb203c1d07eb9abd7f696213921b6 untrusted/project_2/opendev.org/zuul/zuul-jobs: canonical_name: opendev.org/zuul/zuul-jobs checkout: master commit: 571c0efa3491d12ecb8fc1169c510716d55c0fc2 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/sap-linuxlab/community.sap_install name: sap-linuxlab/community.sap_install short_name: community.sap_install src_dir: src/github.com/sap-linuxlab/community.sap_install projects: 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 github.com/sap-linuxlab/community.sap_install: canonical_hostname: github.com canonical_name: github.com/sap-linuxlab/community.sap_install checkout: dev checkout_description: zuul branch commit: ceee0d6e6cd7feb032fb6968202b4cf4e228b034 name: sap-linuxlab/community.sap_install required: false short_name: community.sap_install src_dir: src/github.com/sap-linuxlab/community.sap_install ref: refs/pull/1149/head resources: {} tenant: ansible timeout: 1800 topic: null voting: true zuul_use_fetch_output: true