ansible-playbook [core 2.16.14] config file = None configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /usr/local/lib/python3.12/site-packages/ansible ansible collection location = /tmp/collections-Tk5 executable location = /usr/local/bin/ansible-playbook python version = 3.12.1 (main, Feb 21 2024, 14:18:26) [GCC 8.5.0 20210514 (Red Hat 8.5.0-21)] (/usr/bin/python3.12) jinja version = 3.1.6 libyaml = True No config file found; using defaults running playbook inside collection fedora.linux_system_roles Skipping callback 'debug', as we already have a stdout callback. Skipping callback 'json', as we already have a stdout callback. Skipping callback 'jsonl', as we already have a stdout callback. Skipping callback 'default', as we already have a stdout callback. Skipping callback 'minimal', as we already have a stdout callback. Skipping callback 'oneline', as we already have a stdout callback. PLAYBOOK: tests_quadlet_basic.yml ********************************************** 2 plays in /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml PLAY [all] ********************************************************************* TASK [Include vault variables] ************************************************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:5 Monday 07 July 2025 20:34:27 -0400 (0:00:00.017) 0:00:00.017 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_test_password": { "__ansible_vault": "$ANSIBLE_VAULT;1.1;AES256\n35383939616163653333633431363463313831383037386236646138333162396161356130303461\n3932623930643263313563336163316337643562333936360a363538636631313039343233383732\n38666530383538656639363465313230343533386130303833336434303438333161656262346562\n3362626538613031640a663330613638366132356534363534353239616666653466353961323533\n6565\n" }, "mysql_container_root_password": { "__ansible_vault": "$ANSIBLE_VAULT;1.1;AES256\n61333932373230333539663035366431326163363166363036323963623131363530326231303634\n6635326161643165363366323062333334363730376631660a393566366139353861656364656661\n38653463363837336639363032646433666361646535366137303464623261313663643336306465\n6264663730656337310a343962353137386238383064646533366433333437303566656433386233\n34343235326665646661623131643335313236313131353661386338343366316261643634653633\n3832313034366536616531323963333234326461353130303532\n" } }, "ansible_included_var_files": [ "/tmp/podman-43J/tests/vars/vault-variables.yml" ], "changed": false } PLAY [Ensure that the role can manage quadlet specs] *************************** TASK [Gathering Facts] ********************************************************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:9 Monday 07 July 2025 20:34:27 -0400 (0:00:00.032) 0:00:00.050 *********** ok: [managed-node1] TASK [Test is only supported on x86_64] **************************************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:55 Monday 07 July 2025 20:34:28 -0400 (0:00:01.072) 0:00:01.122 *********** skipping: [managed-node1] => { "false_condition": "ansible_facts[\"architecture\"] != \"x86_64\"" } TASK [End test] **************************************************************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:62 Monday 07 July 2025 20:34:28 -0400 (0:00:00.021) 0:00:01.144 *********** META: end_play conditional evaluated to False, continuing play skipping: [managed-node1] => { "skip_reason": "end_play conditional evaluated to False, continuing play" } MSG: end_play TASK [Run role - do not pull images] ******************************************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:70 Monday 07 July 2025 20:34:28 -0400 (0:00:00.014) 0:00:01.158 *********** TASK [fedora.linux_system_roles.podman : Set platform/version specific variables] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:3 Monday 07 July 2025 20:34:28 -0400 (0:00:00.077) 0:00:01.236 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure ansible_facts used by role] **** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:3 Monday 07 July 2025 20:34:28 -0400 (0:00:00.035) 0:00:01.271 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_required_facts | difference(ansible_facts.keys() | list) | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check if system is ostree] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:11 Monday 07 July 2025 20:34:28 -0400 (0:00:00.050) 0:00:01.322 *********** ok: [managed-node1] => { "changed": false, "stat": { "exists": false } } TASK [fedora.linux_system_roles.podman : Set flag to indicate system is ostree] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:16 Monday 07 July 2025 20:34:28 -0400 (0:00:00.443) 0:00:01.765 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_is_ostree": false }, "changed": false } TASK [fedora.linux_system_roles.podman : Check if transactional-update exists in /sbin] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:23 Monday 07 July 2025 20:34:28 -0400 (0:00:00.022) 0:00:01.788 *********** ok: [managed-node1] => { "changed": false, "stat": { "exists": false } } TASK [fedora.linux_system_roles.podman : Set flag if transactional-update exists] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:28 Monday 07 July 2025 20:34:29 -0400 (0:00:00.321) 0:00:02.109 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_is_transactional": false }, "changed": false } TASK [fedora.linux_system_roles.podman : Set platform/version specific variables] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:32 Monday 07 July 2025 20:34:29 -0400 (0:00:00.024) 0:00:02.133 *********** ok: [managed-node1] => (item=RedHat.yml) => { "ansible_facts": { "__podman_packages": [ "podman", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/RedHat.yml" ], "ansible_loop_var": "item", "changed": false, "item": "RedHat.yml" } skipping: [managed-node1] => (item=CentOS.yml) => { "ansible_loop_var": "item", "changed": false, "false_condition": "__vars_file is file", "item": "CentOS.yml", "skip_reason": "Conditional result was False" } ok: [managed-node1] => (item=CentOS_8.yml) => { "ansible_facts": { "__podman_packages": [ "crun", "podman", "podman-plugins", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/CentOS_8.yml" ], "ansible_loop_var": "item", "changed": false, "item": "CentOS_8.yml" } ok: [managed-node1] => (item=CentOS_8.yml) => { "ansible_facts": { "__podman_packages": [ "crun", "podman", "podman-plugins", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/CentOS_8.yml" ], "ansible_loop_var": "item", "changed": false, "item": "CentOS_8.yml" } TASK [fedora.linux_system_roles.podman : Gather the package facts] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 Monday 07 July 2025 20:34:29 -0400 (0:00:00.042) 0:00:02.176 *********** ok: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Enable copr if requested] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:10 Monday 07 July 2025 20:34:30 -0400 (0:00:01.693) 0:00:03.869 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_use_copr | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Ensure required packages are installed] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:14 Monday 07 July 2025 20:34:30 -0400 (0:00:00.071) 0:00:03.941 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "(__podman_packages | difference(ansible_facts.packages)) | list | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Notify user that reboot is needed to apply changes] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:28 Monday 07 July 2025 20:34:31 -0400 (0:00:00.083) 0:00:04.025 *********** skipping: [managed-node1] => { "false_condition": "__podman_is_transactional | d(false)" } TASK [fedora.linux_system_roles.podman : Reboot transactional update systems] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:33 Monday 07 July 2025 20:34:31 -0400 (0:00:00.073) 0:00:04.099 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_is_transactional | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if reboot is needed and not set] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:38 Monday 07 July 2025 20:34:31 -0400 (0:00:00.073) 0:00:04.173 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_is_transactional | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get podman version] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:46 Monday 07 July 2025 20:34:31 -0400 (0:00:00.059) 0:00:04.232 *********** ok: [managed-node1] => { "changed": false, "cmd": [ "podman", "--version" ], "delta": "0:00:00.028367", "end": "2025-07-07 20:34:31.642738", "rc": 0, "start": "2025-07-07 20:34:31.614371" } STDOUT: podman version 4.9.4-dev TASK [fedora.linux_system_roles.podman : Set podman version] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:52 Monday 07 July 2025 20:34:31 -0400 (0:00:00.484) 0:00:04.717 *********** ok: [managed-node1] => { "ansible_facts": { "podman_version": "4.9.4-dev" }, "changed": false } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.2 or later] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:56 Monday 07 July 2025 20:34:31 -0400 (0:00:00.050) 0:00:04.768 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_version is version(\"4.2\", \"<\")", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.4 or later for quadlet, secrets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:63 Monday 07 July 2025 20:34:31 -0400 (0:00:00.050) 0:00:04.818 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_version is version(\"4.4\", \"<\")", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.4 or later for quadlet, secrets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:73 Monday 07 July 2025 20:34:31 -0400 (0:00:00.081) 0:00:04.900 *********** META: end_host conditional evaluated to False, continuing execution for managed-node1 skipping: [managed-node1] => { "skip_reason": "end_host conditional evaluated to False, continuing execution for managed-node1" } MSG: end_host conditional evaluated to false, continuing execution for managed-node1 TASK [fedora.linux_system_roles.podman : Podman package version must be 5.0 or later for Pod quadlets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:80 Monday 07 July 2025 20:34:31 -0400 (0:00:00.090) 0:00:04.991 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__has_type_pod or __has_pod_file_ext or __has_pod_file_src_ext or __has_pod_template_src_ext or __has_pod_template_src_ext_j2", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 5.0 or later for Pod quadlets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:96 Monday 07 July 2025 20:34:32 -0400 (0:00:00.107) 0:00:05.099 *********** META: end_host conditional evaluated to False, continuing execution for managed-node1 skipping: [managed-node1] => { "skip_reason": "end_host conditional evaluated to False, continuing execution for managed-node1" } MSG: end_host conditional evaluated to false, continuing execution for managed-node1 TASK [fedora.linux_system_roles.podman : Check user and group information] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:109 Monday 07 July 2025 20:34:32 -0400 (0:00:00.078) 0:00:05.177 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Get user information] ***************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:2 Monday 07 July 2025 20:34:32 -0400 (0:00:00.096) 0:00:05.274 *********** ok: [managed-node1] => { "ansible_facts": { "getent_passwd": { "root": [ "x", "0", "0", "root", "/root", "/bin/bash" ] } }, "changed": false } TASK [fedora.linux_system_roles.podman : Fail if user does not exist] ********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:9 Monday 07 July 2025 20:34:32 -0400 (0:00:00.532) 0:00:05.806 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not ansible_facts[\"getent_passwd\"][__podman_user]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set group for podman user] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:16 Monday 07 July 2025 20:34:32 -0400 (0:00:00.056) 0:00:05.862 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_group": "0" }, "changed": false } TASK [fedora.linux_system_roles.podman : See if getsubids exists] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:31 Monday 07 July 2025 20:34:32 -0400 (0:00:00.063) 0:00:05.926 *********** ok: [managed-node1] => { "changed": false, "stat": { "atime": 1751934613.4192193, "attr_flags": "", "attributes": [], "block_size": 4096, "blocks": 32, "charset": "binary", "checksum": "bb5b46ffbafcaa8c4021f3c8b3cb8594f48ef34b", "ctime": 1751934581.384895, "dev": 51713, "device_type": 0, "executable": true, "exists": true, "gid": 0, "gr_name": "root", "inode": 6986653, "isblk": false, "ischr": false, "isdir": false, "isfifo": false, "isgid": false, "islnk": false, "isreg": true, "issock": false, "isuid": false, "mimetype": "application/x-sharedlib", "mode": "0755", "mtime": 1700557386.0, "nlink": 1, "path": "/usr/bin/getsubids", "pw_name": "root", "readable": true, "rgrp": true, "roth": true, "rusr": true, "size": 12640, "uid": 0, "version": "4263604762", "wgrp": false, "woth": false, "writeable": true, "wusr": true, "xgrp": true, "xoth": true, "xusr": true } } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subuids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:42 Monday 07 July 2025 20:34:33 -0400 (0:00:00.386) 0:00:06.312 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subgids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:47 Monday 07 July 2025 20:34:33 -0400 (0:00:00.053) 0:00:06.366 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:52 Monday 07 July 2025 20:34:33 -0400 (0:00:00.051) 0:00:06.417 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subuid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:65 Monday 07 July 2025 20:34:33 -0400 (0:00:00.053) 0:00:06.471 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subgid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:70 Monday 07 July 2025 20:34:33 -0400 (0:00:00.049) 0:00:06.520 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:75 Monday 07 July 2025 20:34:33 -0400 (0:00:00.049) 0:00:06.570 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subuid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:85 Monday 07 July 2025 20:34:33 -0400 (0:00:00.046) 0:00:06.616 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subgid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:92 Monday 07 July 2025 20:34:33 -0400 (0:00:00.047) 0:00:06.664 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set config file paths] **************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:115 Monday 07 July 2025 20:34:33 -0400 (0:00:00.063) 0:00:06.727 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_container_conf_file": "/etc/containers/containers.conf.d/50-systemroles.conf", "__podman_parent_mode": "0755", "__podman_parent_path": "/etc/containers", "__podman_policy_json_file": "/etc/containers/policy.json", "__podman_registries_conf_file": "/etc/containers/registries.conf.d/50-systemroles.conf", "__podman_storage_conf_file": "/etc/containers/storage.conf" }, "changed": false } TASK [fedora.linux_system_roles.podman : Handle container.conf.d] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:126 Monday 07 July 2025 20:34:33 -0400 (0:00:00.093) 0:00:06.821 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_container_conf_d.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure containers.d exists] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_container_conf_d.yml:5 Monday 07 July 2025 20:34:33 -0400 (0:00:00.131) 0:00:06.953 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_containers_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Update container config file] ********* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_container_conf_d.yml:13 Monday 07 July 2025 20:34:34 -0400 (0:00:00.048) 0:00:07.001 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_containers_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Handle registries.conf.d] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:129 Monday 07 July 2025 20:34:34 -0400 (0:00:00.044) 0:00:07.046 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_registries_conf_d.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure registries.d exists] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_registries_conf_d.yml:5 Monday 07 July 2025 20:34:34 -0400 (0:00:00.095) 0:00:07.142 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_registries_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Update registries config file] ******** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_registries_conf_d.yml:13 Monday 07 July 2025 20:34:34 -0400 (0:00:00.045) 0:00:07.187 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_registries_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Handle storage.conf] ****************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:132 Monday 07 July 2025 20:34:34 -0400 (0:00:00.048) 0:00:07.236 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_storage_conf.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure storage.conf parent dir exists] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_storage_conf.yml:7 Monday 07 July 2025 20:34:34 -0400 (0:00:00.097) 0:00:07.334 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_storage_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Update storage config file] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_storage_conf.yml:15 Monday 07 July 2025 20:34:34 -0400 (0:00:00.040) 0:00:07.374 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_storage_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Handle policy.json] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:135 Monday 07 July 2025 20:34:34 -0400 (0:00:00.030) 0:00:07.404 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure policy.json parent dir exists] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:8 Monday 07 July 2025 20:34:34 -0400 (0:00:00.072) 0:00:07.477 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Stat the policy.json file] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:16 Monday 07 July 2025 20:34:34 -0400 (0:00:00.030) 0:00:07.508 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get the existing policy.json] ********* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:21 Monday 07 July 2025 20:34:34 -0400 (0:00:00.028) 0:00:07.536 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Write new policy.json file] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:27 Monday 07 July 2025 20:34:34 -0400 (0:00:00.026) 0:00:07.563 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [Manage firewall for specified ports] ************************************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:141 Monday 07 July 2025 20:34:34 -0400 (0:00:00.027) 0:00:07.591 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_firewall | length > 0", "skip_reason": "Conditional result was False" } TASK [Manage selinux for specified ports] ************************************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:148 Monday 07 July 2025 20:34:34 -0400 (0:00:00.026) 0:00:07.617 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_selinux_ports | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Keep track of users that need to cancel linger] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:155 Monday 07 July 2025 20:34:34 -0400 (0:00:00.056) 0:00:07.674 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_cancel_user_linger": [] }, "changed": false } TASK [fedora.linux_system_roles.podman : Handle certs.d files - present] ******* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:159 Monday 07 July 2025 20:34:34 -0400 (0:00:00.042) 0:00:07.717 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle credential files - present] **** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:168 Monday 07 July 2025 20:34:34 -0400 (0:00:00.060) 0:00:07.777 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle secrets] *********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:177 Monday 07 July 2025 20:34:34 -0400 (0:00:00.045) 0:00:07.823 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle Kubernetes specifications] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:184 Monday 07 July 2025 20:34:34 -0400 (0:00:00.042) 0:00:07.866 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle Quadlet specifications] ******** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:191 Monday 07 July 2025 20:34:34 -0400 (0:00:00.044) 0:00:07.910 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml for managed-node1 => (item=(censored due to no_log)) TASK [fedora.linux_system_roles.podman : Set per-container variables part 0] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:14 Monday 07 July 2025 20:34:35 -0400 (0:00:00.087) 0:00:07.998 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_quadlet_file_src": "", "__podman_quadlet_spec": { "Container": { "ContainerName": "nopull", "Image": "quay.io/libpod/testimage:20210610" }, "Install": { "WantedBy": "default.target" } }, "__podman_quadlet_str": "", "__podman_quadlet_template_src": "" }, "changed": false } TASK [fedora.linux_system_roles.podman : Set per-container variables part 1] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:25 Monday 07 July 2025 20:34:35 -0400 (0:00:00.044) 0:00:08.043 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_continue_if_pull_fails": false, "__podman_pull_image": false, "__podman_state": "created", "__podman_systemd_unit_scope": "", "__podman_user": "root" }, "changed": false } TASK [fedora.linux_system_roles.podman : Fail if no quadlet spec is given] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:35 Monday 07 July 2025 20:34:35 -0400 (0:00:00.037) 0:00:08.080 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_quadlet_spec | length == 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set per-container variables part 2] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:48 Monday 07 July 2025 20:34:35 -0400 (0:00:00.027) 0:00:08.107 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_quadlet_name": "nopull", "__podman_quadlet_type": "container", "__podman_rootless": false }, "changed": false } TASK [fedora.linux_system_roles.podman : Check user and group information] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:57 Monday 07 July 2025 20:34:35 -0400 (0:00:00.042) 0:00:08.150 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Get user information] ***************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:2 Monday 07 July 2025 20:34:35 -0400 (0:00:00.053) 0:00:08.203 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "'getent_passwd' not in ansible_facts or __podman_user not in ansible_facts['getent_passwd']", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user does not exist] ********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:9 Monday 07 July 2025 20:34:35 -0400 (0:00:00.033) 0:00:08.237 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not ansible_facts[\"getent_passwd\"][__podman_user]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set group for podman user] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:16 Monday 07 July 2025 20:34:35 -0400 (0:00:00.049) 0:00:08.286 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_group": "0" }, "changed": false } TASK [fedora.linux_system_roles.podman : See if getsubids exists] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:31 Monday 07 July 2025 20:34:35 -0400 (0:00:00.056) 0:00:08.343 *********** ok: [managed-node1] => { "changed": false, "stat": { "atime": 1751934613.4192193, "attr_flags": "", "attributes": [], "block_size": 4096, "blocks": 32, "charset": "binary", "checksum": "bb5b46ffbafcaa8c4021f3c8b3cb8594f48ef34b", "ctime": 1751934581.384895, "dev": 51713, "device_type": 0, "executable": true, "exists": true, "gid": 0, "gr_name": "root", "inode": 6986653, "isblk": false, "ischr": false, "isdir": false, "isfifo": false, "isgid": false, "islnk": false, "isreg": true, "issock": false, "isuid": false, "mimetype": "application/x-sharedlib", "mode": "0755", "mtime": 1700557386.0, "nlink": 1, "path": "/usr/bin/getsubids", "pw_name": "root", "readable": true, "rgrp": true, "roth": true, "rusr": true, "size": 12640, "uid": 0, "version": "4263604762", "wgrp": false, "woth": false, "writeable": true, "wusr": true, "xgrp": true, "xoth": true, "xusr": true } } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subuids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:42 Monday 07 July 2025 20:34:35 -0400 (0:00:00.369) 0:00:08.713 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subgids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:47 Monday 07 July 2025 20:34:35 -0400 (0:00:00.067) 0:00:08.780 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:52 Monday 07 July 2025 20:34:35 -0400 (0:00:00.043) 0:00:08.824 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subuid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:65 Monday 07 July 2025 20:34:35 -0400 (0:00:00.032) 0:00:08.856 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subgid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:70 Monday 07 July 2025 20:34:35 -0400 (0:00:00.029) 0:00:08.886 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:75 Monday 07 July 2025 20:34:35 -0400 (0:00:00.027) 0:00:08.914 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subuid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:85 Monday 07 July 2025 20:34:35 -0400 (0:00:00.029) 0:00:08.944 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subgid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:92 Monday 07 July 2025 20:34:35 -0400 (0:00:00.028) 0:00:08.972 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set per-container variables part 3] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:62 Monday 07 July 2025 20:34:36 -0400 (0:00:00.029) 0:00:09.001 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_activate_systemd_unit": false, "__podman_images_found": [ "quay.io/libpod/testimage:20210610" ], "__podman_kube_yamls_raw": "", "__podman_service_name": "nopull.service", "__podman_systemd_scope": "system", "__podman_user_home_dir": "/root", "__podman_xdg_runtime_dir": "/run/user/0" }, "changed": false } TASK [fedora.linux_system_roles.podman : Set per-container variables part 4] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:73 Monday 07 July 2025 20:34:36 -0400 (0:00:00.061) 0:00:09.063 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_quadlet_path": "/etc/containers/systemd" }, "changed": false } TASK [fedora.linux_system_roles.podman : Get kube yaml contents] *************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:77 Monday 07 July 2025 20:34:36 -0400 (0:00:00.051) 0:00:09.114 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_kube_yamls_raw | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set per-container variables part 5] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:88 Monday 07 July 2025 20:34:36 -0400 (0:00:00.052) 0:00:09.167 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_images": [ "quay.io/libpod/testimage:20210610" ], "__podman_quadlet_file": "/etc/containers/systemd/nopull.container", "__podman_volumes": [] }, "changed": false } TASK [fedora.linux_system_roles.podman : Set per-container variables part 6] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:106 Monday 07 July 2025 20:34:36 -0400 (0:00:00.113) 0:00:09.280 *********** ok: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Cleanup quadlets] ********************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:113 Monday 07 July 2025 20:34:36 -0400 (0:00:00.055) 0:00:09.335 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_state == \"absent\"", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Create and update quadlets] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:117 Monday 07 July 2025 20:34:36 -0400 (0:00:00.043) 0:00:09.379 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Manage linger] ************************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:2 Monday 07 July 2025 20:34:36 -0400 (0:00:00.115) 0:00:09.494 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/manage_linger.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Enable linger if needed] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/manage_linger.yml:12 Monday 07 July 2025 20:34:36 -0400 (0:00:00.087) 0:00:09.582 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_rootless | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Mark user as not yet needing to cancel linger] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/manage_linger.yml:18 Monday 07 July 2025 20:34:36 -0400 (0:00:00.086) 0:00:09.668 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_rootless | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Mark user for possible linger cancel] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/manage_linger.yml:22 Monday 07 July 2025 20:34:36 -0400 (0:00:00.048) 0:00:09.717 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_rootless | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Create host directories] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:7 Monday 07 July 2025 20:34:36 -0400 (0:00:00.047) 0:00:09.765 *********** skipping: [managed-node1] => { "changed": false, "skipped_reason": "No items in the list" } TASK [fedora.linux_system_roles.podman : Ensure container images are present] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:18 Monday 07 July 2025 20:34:36 -0400 (0:00:00.042) 0:00:09.807 *********** skipping: [managed-node1] => (item=None) => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Ensure the quadlet directory is present] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:39 Monday 07 July 2025 20:34:36 -0400 (0:00:00.063) 0:00:09.871 *********** ok: [managed-node1] => { "changed": false, "gid": 0, "group": "root", "mode": "0755", "owner": "root", "path": "/etc/containers/systemd", "secontext": "system_u:object_r:etc_t:s0", "size": 43, "state": "directory", "uid": 0 } TASK [fedora.linux_system_roles.podman : Ensure quadlet file is copied] ******** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:50 Monday 07 July 2025 20:34:37 -0400 (0:00:00.526) 0:00:10.397 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_quadlet_file_src | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Ensure quadlet file content is present] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:62 Monday 07 July 2025 20:34:37 -0400 (0:00:00.050) 0:00:10.448 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_quadlet_str | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Ensure quadlet file is present] ******* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:75 Monday 07 July 2025 20:34:37 -0400 (0:00:00.049) 0:00:10.497 *********** changed: [managed-node1] => { "changed": true, "checksum": "670d64fc68a9768edb20cad26df2acc703542d85", "dest": "/etc/containers/systemd/nopull.container", "gid": 0, "group": "root", "md5sum": "cedb6667f6cd1b033fe06e2810fe6b19", "mode": "0644", "owner": "root", "secontext": "system_u:object_r:etc_t:s0", "size": 151, "src": "/root/.ansible/tmp/ansible-tmp-1751934877.5450642-17711-142143421897050/source", "state": "file", "uid": 0 } TASK [fedora.linux_system_roles.podman : Reload systemctl] ********************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:87 Monday 07 July 2025 20:34:38 -0400 (0:00:00.795) 0:00:11.293 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_activate_systemd_unit | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Start service] ************************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:115 Monday 07 July 2025 20:34:38 -0400 (0:00:00.031) 0:00:11.325 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_activate_systemd_unit | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Restart service] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:131 Monday 07 July 2025 20:34:38 -0400 (0:00:00.034) 0:00:11.359 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_activate_systemd_unit | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Cancel linger] ************************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:198 Monday 07 July 2025 20:34:38 -0400 (0:00:00.035) 0:00:11.395 *********** skipping: [managed-node1] => { "changed": false, "skipped_reason": "No items in the list" } TASK [fedora.linux_system_roles.podman : Handle credential files - absent] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:204 Monday 07 July 2025 20:34:38 -0400 (0:00:00.026) 0:00:11.421 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle certs.d files - absent] ******** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:213 Monday 07 July 2025 20:34:38 -0400 (0:00:00.024) 0:00:11.446 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [Verify image not pulled] ************************************************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:86 Monday 07 July 2025 20:34:38 -0400 (0:00:00.040) 0:00:11.486 *********** ok: [managed-node1] => { "changed": false } MSG: All assertions passed TASK [Run role - try to pull bogus image] ************************************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:90 Monday 07 July 2025 20:34:38 -0400 (0:00:00.030) 0:00:11.517 *********** TASK [fedora.linux_system_roles.podman : Set platform/version specific variables] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:3 Monday 07 July 2025 20:34:38 -0400 (0:00:00.122) 0:00:11.639 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure ansible_facts used by role] **** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:3 Monday 07 July 2025 20:34:38 -0400 (0:00:00.049) 0:00:11.689 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_required_facts | difference(ansible_facts.keys() | list) | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check if system is ostree] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:11 Monday 07 July 2025 20:34:38 -0400 (0:00:00.033) 0:00:11.723 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_ostree is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set flag to indicate system is ostree] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:16 Monday 07 July 2025 20:34:38 -0400 (0:00:00.027) 0:00:11.751 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_ostree is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check if transactional-update exists in /sbin] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:23 Monday 07 July 2025 20:34:38 -0400 (0:00:00.027) 0:00:11.778 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_transactional is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set flag if transactional-update exists] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:28 Monday 07 July 2025 20:34:38 -0400 (0:00:00.027) 0:00:11.806 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_transactional is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set platform/version specific variables] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:32 Monday 07 July 2025 20:34:38 -0400 (0:00:00.028) 0:00:11.834 *********** ok: [managed-node1] => (item=RedHat.yml) => { "ansible_facts": { "__podman_packages": [ "podman", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/RedHat.yml" ], "ansible_loop_var": "item", "changed": false, "item": "RedHat.yml" } skipping: [managed-node1] => (item=CentOS.yml) => { "ansible_loop_var": "item", "changed": false, "false_condition": "__vars_file is file", "item": "CentOS.yml", "skip_reason": "Conditional result was False" } ok: [managed-node1] => (item=CentOS_8.yml) => { "ansible_facts": { "__podman_packages": [ "crun", "podman", "podman-plugins", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/CentOS_8.yml" ], "ansible_loop_var": "item", "changed": false, "item": "CentOS_8.yml" } ok: [managed-node1] => (item=CentOS_8.yml) => { "ansible_facts": { "__podman_packages": [ "crun", "podman", "podman-plugins", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/CentOS_8.yml" ], "ansible_loop_var": "item", "changed": false, "item": "CentOS_8.yml" } TASK [fedora.linux_system_roles.podman : Gather the package facts] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 Monday 07 July 2025 20:34:38 -0400 (0:00:00.074) 0:00:11.909 *********** ok: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Enable copr if requested] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:10 Monday 07 July 2025 20:34:40 -0400 (0:00:01.539) 0:00:13.448 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_use_copr | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Ensure required packages are installed] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:14 Monday 07 July 2025 20:34:40 -0400 (0:00:00.047) 0:00:13.496 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "(__podman_packages | difference(ansible_facts.packages)) | list | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Notify user that reboot is needed to apply changes] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:28 Monday 07 July 2025 20:34:40 -0400 (0:00:00.061) 0:00:13.557 *********** skipping: [managed-node1] => { "false_condition": "__podman_is_transactional | d(false)" } TASK [fedora.linux_system_roles.podman : Reboot transactional update systems] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:33 Monday 07 July 2025 20:34:40 -0400 (0:00:00.047) 0:00:13.604 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_is_transactional | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if reboot is needed and not set] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:38 Monday 07 July 2025 20:34:40 -0400 (0:00:00.048) 0:00:13.652 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_is_transactional | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get podman version] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:46 Monday 07 July 2025 20:34:40 -0400 (0:00:00.049) 0:00:13.702 *********** ok: [managed-node1] => { "changed": false, "cmd": [ "podman", "--version" ], "delta": "0:00:00.025953", "end": "2025-07-07 20:34:41.034608", "rc": 0, "start": "2025-07-07 20:34:41.008655" } STDOUT: podman version 4.9.4-dev TASK [fedora.linux_system_roles.podman : Set podman version] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:52 Monday 07 July 2025 20:34:41 -0400 (0:00:00.393) 0:00:14.096 *********** ok: [managed-node1] => { "ansible_facts": { "podman_version": "4.9.4-dev" }, "changed": false } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.2 or later] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:56 Monday 07 July 2025 20:34:41 -0400 (0:00:00.075) 0:00:14.171 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_version is version(\"4.2\", \"<\")", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.4 or later for quadlet, secrets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:63 Monday 07 July 2025 20:34:41 -0400 (0:00:00.029) 0:00:14.200 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_version is version(\"4.4\", \"<\")", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.4 or later for quadlet, secrets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:73 Monday 07 July 2025 20:34:41 -0400 (0:00:00.032) 0:00:14.232 *********** META: end_host conditional evaluated to False, continuing execution for managed-node1 skipping: [managed-node1] => { "skip_reason": "end_host conditional evaluated to False, continuing execution for managed-node1" } MSG: end_host conditional evaluated to false, continuing execution for managed-node1 TASK [fedora.linux_system_roles.podman : Podman package version must be 5.0 or later for Pod quadlets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:80 Monday 07 July 2025 20:34:41 -0400 (0:00:00.034) 0:00:14.267 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__has_type_pod or __has_pod_file_ext or __has_pod_file_src_ext or __has_pod_template_src_ext or __has_pod_template_src_ext_j2", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 5.0 or later for Pod quadlets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:96 Monday 07 July 2025 20:34:41 -0400 (0:00:00.042) 0:00:14.310 *********** META: end_host conditional evaluated to False, continuing execution for managed-node1 skipping: [managed-node1] => { "skip_reason": "end_host conditional evaluated to False, continuing execution for managed-node1" } MSG: end_host conditional evaluated to false, continuing execution for managed-node1 TASK [fedora.linux_system_roles.podman : Check user and group information] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:109 Monday 07 July 2025 20:34:41 -0400 (0:00:00.060) 0:00:14.370 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Get user information] ***************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:2 Monday 07 July 2025 20:34:41 -0400 (0:00:00.097) 0:00:14.468 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "'getent_passwd' not in ansible_facts or __podman_user not in ansible_facts['getent_passwd']", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user does not exist] ********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:9 Monday 07 July 2025 20:34:41 -0400 (0:00:00.057) 0:00:14.526 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not ansible_facts[\"getent_passwd\"][__podman_user]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set group for podman user] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:16 Monday 07 July 2025 20:34:41 -0400 (0:00:00.051) 0:00:14.578 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_group": "0" }, "changed": false } TASK [fedora.linux_system_roles.podman : See if getsubids exists] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:31 Monday 07 July 2025 20:34:41 -0400 (0:00:00.046) 0:00:14.624 *********** ok: [managed-node1] => { "changed": false, "stat": { "atime": 1751934613.4192193, "attr_flags": "", "attributes": [], "block_size": 4096, "blocks": 32, "charset": "binary", "checksum": "bb5b46ffbafcaa8c4021f3c8b3cb8594f48ef34b", "ctime": 1751934581.384895, "dev": 51713, "device_type": 0, "executable": true, "exists": true, "gid": 0, "gr_name": "root", "inode": 6986653, "isblk": false, "ischr": false, "isdir": false, "isfifo": false, "isgid": false, "islnk": false, "isreg": true, "issock": false, "isuid": false, "mimetype": "application/x-sharedlib", "mode": "0755", "mtime": 1700557386.0, "nlink": 1, "path": "/usr/bin/getsubids", "pw_name": "root", "readable": true, "rgrp": true, "roth": true, "rusr": true, "size": 12640, "uid": 0, "version": "4263604762", "wgrp": false, "woth": false, "writeable": true, "wusr": true, "xgrp": true, "xoth": true, "xusr": true } } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subuids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:42 Monday 07 July 2025 20:34:42 -0400 (0:00:00.381) 0:00:15.006 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subgids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:47 Monday 07 July 2025 20:34:42 -0400 (0:00:00.052) 0:00:15.059 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:52 Monday 07 July 2025 20:34:42 -0400 (0:00:00.050) 0:00:15.109 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subuid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:65 Monday 07 July 2025 20:34:42 -0400 (0:00:00.052) 0:00:15.162 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subgid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:70 Monday 07 July 2025 20:34:42 -0400 (0:00:00.045) 0:00:15.207 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:75 Monday 07 July 2025 20:34:42 -0400 (0:00:00.050) 0:00:15.258 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subuid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:85 Monday 07 July 2025 20:34:42 -0400 (0:00:00.096) 0:00:15.354 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subgid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:92 Monday 07 July 2025 20:34:42 -0400 (0:00:00.050) 0:00:15.405 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set config file paths] **************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:115 Monday 07 July 2025 20:34:42 -0400 (0:00:00.051) 0:00:15.456 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_container_conf_file": "/etc/containers/containers.conf.d/50-systemroles.conf", "__podman_parent_mode": "0755", "__podman_parent_path": "/etc/containers", "__podman_policy_json_file": "/etc/containers/policy.json", "__podman_registries_conf_file": "/etc/containers/registries.conf.d/50-systemroles.conf", "__podman_storage_conf_file": "/etc/containers/storage.conf" }, "changed": false } TASK [fedora.linux_system_roles.podman : Handle container.conf.d] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:126 Monday 07 July 2025 20:34:42 -0400 (0:00:00.063) 0:00:15.520 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_container_conf_d.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure containers.d exists] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_container_conf_d.yml:5 Monday 07 July 2025 20:34:42 -0400 (0:00:00.096) 0:00:15.617 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_containers_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Update container config file] ********* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_container_conf_d.yml:13 Monday 07 July 2025 20:34:42 -0400 (0:00:00.050) 0:00:15.667 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_containers_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Handle registries.conf.d] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:129 Monday 07 July 2025 20:34:42 -0400 (0:00:00.050) 0:00:15.717 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_registries_conf_d.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure registries.d exists] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_registries_conf_d.yml:5 Monday 07 July 2025 20:34:42 -0400 (0:00:00.096) 0:00:15.813 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_registries_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Update registries config file] ******** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_registries_conf_d.yml:13 Monday 07 July 2025 20:34:42 -0400 (0:00:00.047) 0:00:15.861 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_registries_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Handle storage.conf] ****************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:132 Monday 07 July 2025 20:34:42 -0400 (0:00:00.046) 0:00:15.907 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_storage_conf.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure storage.conf parent dir exists] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_storage_conf.yml:7 Monday 07 July 2025 20:34:42 -0400 (0:00:00.080) 0:00:15.988 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_storage_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Update storage config file] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_storage_conf.yml:15 Monday 07 July 2025 20:34:43 -0400 (0:00:00.034) 0:00:16.023 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_storage_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Handle policy.json] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:135 Monday 07 July 2025 20:34:43 -0400 (0:00:00.043) 0:00:16.066 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure policy.json parent dir exists] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:8 Monday 07 July 2025 20:34:43 -0400 (0:00:00.063) 0:00:16.130 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Stat the policy.json file] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:16 Monday 07 July 2025 20:34:43 -0400 (0:00:00.029) 0:00:16.159 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get the existing policy.json] ********* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:21 Monday 07 July 2025 20:34:43 -0400 (0:00:00.059) 0:00:16.219 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Write new policy.json file] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:27 Monday 07 July 2025 20:34:43 -0400 (0:00:00.029) 0:00:16.249 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [Manage firewall for specified ports] ************************************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:141 Monday 07 July 2025 20:34:43 -0400 (0:00:00.031) 0:00:16.280 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_firewall | length > 0", "skip_reason": "Conditional result was False" } TASK [Manage selinux for specified ports] ************************************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:148 Monday 07 July 2025 20:34:43 -0400 (0:00:00.043) 0:00:16.323 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_selinux_ports | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Keep track of users that need to cancel linger] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:155 Monday 07 July 2025 20:34:43 -0400 (0:00:00.048) 0:00:16.372 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_cancel_user_linger": [] }, "changed": false } TASK [fedora.linux_system_roles.podman : Handle certs.d files - present] ******* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:159 Monday 07 July 2025 20:34:43 -0400 (0:00:00.047) 0:00:16.419 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle credential files - present] **** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:168 Monday 07 July 2025 20:34:43 -0400 (0:00:00.047) 0:00:16.467 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle secrets] *********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:177 Monday 07 July 2025 20:34:43 -0400 (0:00:00.043) 0:00:16.510 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle Kubernetes specifications] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:184 Monday 07 July 2025 20:34:43 -0400 (0:00:00.047) 0:00:16.557 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle Quadlet specifications] ******** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:191 Monday 07 July 2025 20:34:43 -0400 (0:00:00.041) 0:00:16.599 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml for managed-node1 => (item=(censored due to no_log)) TASK [fedora.linux_system_roles.podman : Set per-container variables part 0] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:14 Monday 07 July 2025 20:34:43 -0400 (0:00:00.100) 0:00:16.700 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_quadlet_file_src": "", "__podman_quadlet_spec": { "Container": { "ContainerName": "bogus", "Image": "this_is_a_bogus_image" }, "Install": { "WantedBy": "default.target" } }, "__podman_quadlet_str": "", "__podman_quadlet_template_src": "" }, "changed": false } TASK [fedora.linux_system_roles.podman : Set per-container variables part 1] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:25 Monday 07 July 2025 20:34:43 -0400 (0:00:00.043) 0:00:16.744 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_continue_if_pull_fails": true, "__podman_pull_image": true, "__podman_state": "created", "__podman_systemd_unit_scope": "", "__podman_user": "root" }, "changed": false } TASK [fedora.linux_system_roles.podman : Fail if no quadlet spec is given] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:35 Monday 07 July 2025 20:34:43 -0400 (0:00:00.049) 0:00:16.793 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_quadlet_spec | length == 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set per-container variables part 2] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:48 Monday 07 July 2025 20:34:43 -0400 (0:00:00.031) 0:00:16.825 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_quadlet_name": "bogus", "__podman_quadlet_type": "container", "__podman_rootless": false }, "changed": false } TASK [fedora.linux_system_roles.podman : Check user and group information] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:57 Monday 07 July 2025 20:34:43 -0400 (0:00:00.043) 0:00:16.869 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Get user information] ***************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:2 Monday 07 July 2025 20:34:43 -0400 (0:00:00.055) 0:00:16.924 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "'getent_passwd' not in ansible_facts or __podman_user not in ansible_facts['getent_passwd']", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user does not exist] ********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:9 Monday 07 July 2025 20:34:43 -0400 (0:00:00.065) 0:00:16.990 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not ansible_facts[\"getent_passwd\"][__podman_user]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set group for podman user] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:16 Monday 07 July 2025 20:34:44 -0400 (0:00:00.032) 0:00:17.022 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_group": "0" }, "changed": false } TASK [fedora.linux_system_roles.podman : See if getsubids exists] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:31 Monday 07 July 2025 20:34:44 -0400 (0:00:00.048) 0:00:17.071 *********** ok: [managed-node1] => { "changed": false, "stat": { "atime": 1751934613.4192193, "attr_flags": "", "attributes": [], "block_size": 4096, "blocks": 32, "charset": "binary", "checksum": "bb5b46ffbafcaa8c4021f3c8b3cb8594f48ef34b", "ctime": 1751934581.384895, "dev": 51713, "device_type": 0, "executable": true, "exists": true, "gid": 0, "gr_name": "root", "inode": 6986653, "isblk": false, "ischr": false, "isdir": false, "isfifo": false, "isgid": false, "islnk": false, "isreg": true, "issock": false, "isuid": false, "mimetype": "application/x-sharedlib", "mode": "0755", "mtime": 1700557386.0, "nlink": 1, "path": "/usr/bin/getsubids", "pw_name": "root", "readable": true, "rgrp": true, "roth": true, "rusr": true, "size": 12640, "uid": 0, "version": "4263604762", "wgrp": false, "woth": false, "writeable": true, "wusr": true, "xgrp": true, "xoth": true, "xusr": true } } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subuids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:42 Monday 07 July 2025 20:34:44 -0400 (0:00:00.344) 0:00:17.415 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subgids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:47 Monday 07 July 2025 20:34:44 -0400 (0:00:00.032) 0:00:17.447 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:52 Monday 07 July 2025 20:34:44 -0400 (0:00:00.031) 0:00:17.479 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subuid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:65 Monday 07 July 2025 20:34:44 -0400 (0:00:00.030) 0:00:17.509 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subgid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:70 Monday 07 July 2025 20:34:44 -0400 (0:00:00.031) 0:00:17.540 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:75 Monday 07 July 2025 20:34:44 -0400 (0:00:00.029) 0:00:17.570 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subuid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:85 Monday 07 July 2025 20:34:44 -0400 (0:00:00.030) 0:00:17.601 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subgid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:92 Monday 07 July 2025 20:34:44 -0400 (0:00:00.030) 0:00:17.631 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set per-container variables part 3] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:62 Monday 07 July 2025 20:34:44 -0400 (0:00:00.028) 0:00:17.660 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_activate_systemd_unit": false, "__podman_images_found": [ "this_is_a_bogus_image" ], "__podman_kube_yamls_raw": "", "__podman_service_name": "bogus.service", "__podman_systemd_scope": "system", "__podman_user_home_dir": "/root", "__podman_xdg_runtime_dir": "/run/user/0" }, "changed": false } TASK [fedora.linux_system_roles.podman : Set per-container variables part 4] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:73 Monday 07 July 2025 20:34:44 -0400 (0:00:00.049) 0:00:17.710 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_quadlet_path": "/etc/containers/systemd" }, "changed": false } TASK [fedora.linux_system_roles.podman : Get kube yaml contents] *************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:77 Monday 07 July 2025 20:34:44 -0400 (0:00:00.031) 0:00:17.741 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_kube_yamls_raw | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set per-container variables part 5] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:88 Monday 07 July 2025 20:34:44 -0400 (0:00:00.035) 0:00:17.777 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_images": [ "this_is_a_bogus_image" ], "__podman_quadlet_file": "/etc/containers/systemd/bogus.container", "__podman_volumes": [] }, "changed": false } TASK [fedora.linux_system_roles.podman : Set per-container variables part 6] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:106 Monday 07 July 2025 20:34:44 -0400 (0:00:00.106) 0:00:17.883 *********** ok: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Cleanup quadlets] ********************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:113 Monday 07 July 2025 20:34:44 -0400 (0:00:00.039) 0:00:17.923 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_state == \"absent\"", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Create and update quadlets] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:117 Monday 07 July 2025 20:34:44 -0400 (0:00:00.032) 0:00:17.955 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Manage linger] ************************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:2 Monday 07 July 2025 20:34:45 -0400 (0:00:00.116) 0:00:18.072 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/manage_linger.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Enable linger if needed] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/manage_linger.yml:12 Monday 07 July 2025 20:34:45 -0400 (0:00:00.054) 0:00:18.126 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_rootless | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Mark user as not yet needing to cancel linger] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/manage_linger.yml:18 Monday 07 July 2025 20:34:45 -0400 (0:00:00.029) 0:00:18.156 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_rootless | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Mark user for possible linger cancel] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/manage_linger.yml:22 Monday 07 July 2025 20:34:45 -0400 (0:00:00.029) 0:00:18.185 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_rootless | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Create host directories] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:7 Monday 07 July 2025 20:34:45 -0400 (0:00:00.035) 0:00:18.221 *********** skipping: [managed-node1] => { "changed": false, "skipped_reason": "No items in the list" } TASK [fedora.linux_system_roles.podman : Ensure container images are present] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:18 Monday 07 July 2025 20:34:45 -0400 (0:00:00.045) 0:00:18.266 *********** ok: [managed-node1] => (item=None) => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } ok: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Ensure the quadlet directory is present] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:39 Monday 07 July 2025 20:34:46 -0400 (0:00:00.986) 0:00:19.253 *********** ok: [managed-node1] => { "changed": false, "gid": 0, "group": "root", "mode": "0755", "owner": "root", "path": "/etc/containers/systemd", "secontext": "system_u:object_r:etc_t:s0", "size": 67, "state": "directory", "uid": 0 } TASK [fedora.linux_system_roles.podman : Ensure quadlet file is copied] ******** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:50 Monday 07 July 2025 20:34:46 -0400 (0:00:00.400) 0:00:19.653 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_quadlet_file_src | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Ensure quadlet file content is present] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:62 Monday 07 July 2025 20:34:46 -0400 (0:00:00.051) 0:00:19.705 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_quadlet_str | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Ensure quadlet file is present] ******* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:75 Monday 07 July 2025 20:34:46 -0400 (0:00:00.053) 0:00:19.758 *********** changed: [managed-node1] => { "changed": true, "checksum": "1d087e679d135214e8ac9ccaf33b2222916efb7f", "dest": "/etc/containers/systemd/bogus.container", "gid": 0, "group": "root", "md5sum": "97480a9a73734d9f8007d2c06e7fed1f", "mode": "0644", "owner": "root", "secontext": "system_u:object_r:etc_t:s0", "size": 138, "src": "/root/.ansible/tmp/ansible-tmp-1751934886.8113573-18040-140717157966343/source", "state": "file", "uid": 0 } TASK [fedora.linux_system_roles.podman : Reload systemctl] ********************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:87 Monday 07 July 2025 20:34:47 -0400 (0:00:00.720) 0:00:20.479 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_activate_systemd_unit | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Start service] ************************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:115 Monday 07 July 2025 20:34:47 -0400 (0:00:00.054) 0:00:20.533 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_activate_systemd_unit | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Restart service] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:131 Monday 07 July 2025 20:34:47 -0400 (0:00:00.059) 0:00:20.593 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_activate_systemd_unit | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Cancel linger] ************************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:198 Monday 07 July 2025 20:34:47 -0400 (0:00:00.057) 0:00:20.650 *********** skipping: [managed-node1] => { "changed": false, "skipped_reason": "No items in the list" } TASK [fedora.linux_system_roles.podman : Handle credential files - absent] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:204 Monday 07 July 2025 20:34:47 -0400 (0:00:00.044) 0:00:20.694 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle certs.d files - absent] ******** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:213 Monday 07 July 2025 20:34:47 -0400 (0:00:00.044) 0:00:20.739 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [Verify image not pulled and no error] ************************************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:106 Monday 07 July 2025 20:34:47 -0400 (0:00:00.073) 0:00:20.812 *********** ok: [managed-node1] => { "changed": false } MSG: All assertions passed TASK [Cleanup] ***************************************************************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:113 Monday 07 July 2025 20:34:47 -0400 (0:00:00.103) 0:00:20.916 *********** TASK [fedora.linux_system_roles.podman : Set platform/version specific variables] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:3 Monday 07 July 2025 20:34:48 -0400 (0:00:00.291) 0:00:21.207 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure ansible_facts used by role] **** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:3 Monday 07 July 2025 20:34:48 -0400 (0:00:00.084) 0:00:21.291 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_required_facts | difference(ansible_facts.keys() | list) | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check if system is ostree] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:11 Monday 07 July 2025 20:34:48 -0400 (0:00:00.063) 0:00:21.354 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_ostree is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set flag to indicate system is ostree] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:16 Monday 07 July 2025 20:34:48 -0400 (0:00:00.052) 0:00:21.407 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_ostree is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check if transactional-update exists in /sbin] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:23 Monday 07 July 2025 20:34:48 -0400 (0:00:00.050) 0:00:21.458 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_transactional is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set flag if transactional-update exists] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:28 Monday 07 July 2025 20:34:48 -0400 (0:00:00.048) 0:00:21.506 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_transactional is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set platform/version specific variables] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:32 Monday 07 July 2025 20:34:48 -0400 (0:00:00.043) 0:00:21.550 *********** [WARNING]: TASK: fedora.linux_system_roles.podman : Set platform/version specific variables: The loop variable 'item' is already in use. You should set the `loop_var` value in the `loop_control` option for the task to something else to avoid variable collisions and unexpected behavior. ok: [managed-node1] => (item=RedHat.yml) => { "ansible_facts": { "__podman_packages": [ "podman", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/RedHat.yml" ], "ansible_loop_var": "item", "changed": false, "item": "RedHat.yml" } skipping: [managed-node1] => (item=CentOS.yml) => { "ansible_loop_var": "item", "changed": false, "false_condition": "__vars_file is file", "item": "CentOS.yml", "skip_reason": "Conditional result was False" } ok: [managed-node1] => (item=CentOS_8.yml) => { "ansible_facts": { "__podman_packages": [ "crun", "podman", "podman-plugins", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/CentOS_8.yml" ], "ansible_loop_var": "item", "changed": false, "item": "CentOS_8.yml" } ok: [managed-node1] => (item=CentOS_8.yml) => { "ansible_facts": { "__podman_packages": [ "crun", "podman", "podman-plugins", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/CentOS_8.yml" ], "ansible_loop_var": "item", "changed": false, "item": "CentOS_8.yml" } TASK [fedora.linux_system_roles.podman : Gather the package facts] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 Monday 07 July 2025 20:34:48 -0400 (0:00:00.074) 0:00:21.624 *********** ok: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Enable copr if requested] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:10 Monday 07 July 2025 20:34:50 -0400 (0:00:01.439) 0:00:23.063 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_use_copr | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Ensure required packages are installed] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:14 Monday 07 July 2025 20:34:50 -0400 (0:00:00.034) 0:00:23.098 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "(__podman_packages | difference(ansible_facts.packages)) | list | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Notify user that reboot is needed to apply changes] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:28 Monday 07 July 2025 20:34:50 -0400 (0:00:00.114) 0:00:23.212 *********** skipping: [managed-node1] => { "false_condition": "__podman_is_transactional | d(false)" } TASK [fedora.linux_system_roles.podman : Reboot transactional update systems] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:33 Monday 07 July 2025 20:34:50 -0400 (0:00:00.037) 0:00:23.250 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_is_transactional | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if reboot is needed and not set] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:38 Monday 07 July 2025 20:34:50 -0400 (0:00:00.037) 0:00:23.288 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_is_transactional | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get podman version] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:46 Monday 07 July 2025 20:34:50 -0400 (0:00:00.038) 0:00:23.326 *********** ok: [managed-node1] => { "changed": false, "cmd": [ "podman", "--version" ], "delta": "0:00:00.027969", "end": "2025-07-07 20:34:50.635100", "rc": 0, "start": "2025-07-07 20:34:50.607131" } STDOUT: podman version 4.9.4-dev TASK [fedora.linux_system_roles.podman : Set podman version] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:52 Monday 07 July 2025 20:34:50 -0400 (0:00:00.374) 0:00:23.701 *********** ok: [managed-node1] => { "ansible_facts": { "podman_version": "4.9.4-dev" }, "changed": false } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.2 or later] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:56 Monday 07 July 2025 20:34:50 -0400 (0:00:00.039) 0:00:23.740 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_version is version(\"4.2\", \"<\")", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.4 or later for quadlet, secrets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:63 Monday 07 July 2025 20:34:50 -0400 (0:00:00.029) 0:00:23.769 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_version is version(\"4.4\", \"<\")", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.4 or later for quadlet, secrets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:73 Monday 07 July 2025 20:34:50 -0400 (0:00:00.033) 0:00:23.803 *********** META: end_host conditional evaluated to False, continuing execution for managed-node1 skipping: [managed-node1] => { "skip_reason": "end_host conditional evaluated to False, continuing execution for managed-node1" } MSG: end_host conditional evaluated to false, continuing execution for managed-node1 TASK [fedora.linux_system_roles.podman : Podman package version must be 5.0 or later for Pod quadlets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:80 Monday 07 July 2025 20:34:50 -0400 (0:00:00.035) 0:00:23.838 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__has_type_pod or __has_pod_file_ext or __has_pod_file_src_ext or __has_pod_template_src_ext or __has_pod_template_src_ext_j2", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 5.0 or later for Pod quadlets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:96 Monday 07 July 2025 20:34:50 -0400 (0:00:00.042) 0:00:23.881 *********** META: end_host conditional evaluated to False, continuing execution for managed-node1 skipping: [managed-node1] => { "skip_reason": "end_host conditional evaluated to False, continuing execution for managed-node1" } MSG: end_host conditional evaluated to false, continuing execution for managed-node1 TASK [fedora.linux_system_roles.podman : Check user and group information] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:109 Monday 07 July 2025 20:34:50 -0400 (0:00:00.046) 0:00:23.927 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Get user information] ***************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:2 Monday 07 July 2025 20:34:50 -0400 (0:00:00.061) 0:00:23.989 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "'getent_passwd' not in ansible_facts or __podman_user not in ansible_facts['getent_passwd']", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user does not exist] ********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:9 Monday 07 July 2025 20:34:51 -0400 (0:00:00.039) 0:00:24.028 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not ansible_facts[\"getent_passwd\"][__podman_user]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set group for podman user] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:16 Monday 07 July 2025 20:34:51 -0400 (0:00:00.056) 0:00:24.085 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_group": "0" }, "changed": false } TASK [fedora.linux_system_roles.podman : See if getsubids exists] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:31 Monday 07 July 2025 20:34:51 -0400 (0:00:00.057) 0:00:24.142 *********** ok: [managed-node1] => { "changed": false, "stat": { "atime": 1751934613.4192193, "attr_flags": "", "attributes": [], "block_size": 4096, "blocks": 32, "charset": "binary", "checksum": "bb5b46ffbafcaa8c4021f3c8b3cb8594f48ef34b", "ctime": 1751934581.384895, "dev": 51713, "device_type": 0, "executable": true, "exists": true, "gid": 0, "gr_name": "root", "inode": 6986653, "isblk": false, "ischr": false, "isdir": false, "isfifo": false, "isgid": false, "islnk": false, "isreg": true, "issock": false, "isuid": false, "mimetype": "application/x-sharedlib", "mode": "0755", "mtime": 1700557386.0, "nlink": 1, "path": "/usr/bin/getsubids", "pw_name": "root", "readable": true, "rgrp": true, "roth": true, "rusr": true, "size": 12640, "uid": 0, "version": "4263604762", "wgrp": false, "woth": false, "writeable": true, "wusr": true, "xgrp": true, "xoth": true, "xusr": true } } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subuids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:42 Monday 07 July 2025 20:34:51 -0400 (0:00:00.375) 0:00:24.517 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subgids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:47 Monday 07 July 2025 20:34:51 -0400 (0:00:00.107) 0:00:24.624 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:52 Monday 07 July 2025 20:34:51 -0400 (0:00:00.052) 0:00:24.677 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subuid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:65 Monday 07 July 2025 20:34:51 -0400 (0:00:00.052) 0:00:24.729 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subgid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:70 Monday 07 July 2025 20:34:51 -0400 (0:00:00.051) 0:00:24.781 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:75 Monday 07 July 2025 20:34:51 -0400 (0:00:00.052) 0:00:24.834 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subuid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:85 Monday 07 July 2025 20:34:51 -0400 (0:00:00.055) 0:00:24.889 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subgid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:92 Monday 07 July 2025 20:34:51 -0400 (0:00:00.052) 0:00:24.942 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set config file paths] **************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:115 Monday 07 July 2025 20:34:51 -0400 (0:00:00.054) 0:00:24.996 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_container_conf_file": "/etc/containers/containers.conf.d/50-systemroles.conf", "__podman_parent_mode": "0755", "__podman_parent_path": "/etc/containers", "__podman_policy_json_file": "/etc/containers/policy.json", "__podman_registries_conf_file": "/etc/containers/registries.conf.d/50-systemroles.conf", "__podman_storage_conf_file": "/etc/containers/storage.conf" }, "changed": false } TASK [fedora.linux_system_roles.podman : Handle container.conf.d] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:126 Monday 07 July 2025 20:34:52 -0400 (0:00:00.066) 0:00:25.062 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_container_conf_d.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure containers.d exists] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_container_conf_d.yml:5 Monday 07 July 2025 20:34:52 -0400 (0:00:00.100) 0:00:25.163 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_containers_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Update container config file] ********* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_container_conf_d.yml:13 Monday 07 July 2025 20:34:52 -0400 (0:00:00.049) 0:00:25.213 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_containers_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Handle registries.conf.d] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:129 Monday 07 July 2025 20:34:52 -0400 (0:00:00.057) 0:00:25.270 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_registries_conf_d.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure registries.d exists] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_registries_conf_d.yml:5 Monday 07 July 2025 20:34:52 -0400 (0:00:00.085) 0:00:25.356 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_registries_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Update registries config file] ******** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_registries_conf_d.yml:13 Monday 07 July 2025 20:34:52 -0400 (0:00:00.036) 0:00:25.392 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_registries_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Handle storage.conf] ****************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:132 Monday 07 July 2025 20:34:52 -0400 (0:00:00.034) 0:00:25.427 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_storage_conf.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure storage.conf parent dir exists] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_storage_conf.yml:7 Monday 07 July 2025 20:34:52 -0400 (0:00:00.061) 0:00:25.488 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_storage_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Update storage config file] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_storage_conf.yml:15 Monday 07 July 2025 20:34:52 -0400 (0:00:00.063) 0:00:25.552 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_storage_conf | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Handle policy.json] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:135 Monday 07 July 2025 20:34:52 -0400 (0:00:00.031) 0:00:25.583 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure policy.json parent dir exists] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:8 Monday 07 July 2025 20:34:52 -0400 (0:00:00.065) 0:00:25.648 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Stat the policy.json file] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:16 Monday 07 July 2025 20:34:52 -0400 (0:00:00.049) 0:00:25.698 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get the existing policy.json] ********* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:21 Monday 07 July 2025 20:34:52 -0400 (0:00:00.051) 0:00:25.749 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Write new policy.json file] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_policy_json.yml:27 Monday 07 July 2025 20:34:52 -0400 (0:00:00.049) 0:00:25.799 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_policy_json | length > 0", "skip_reason": "Conditional result was False" } TASK [Manage firewall for specified ports] ************************************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:141 Monday 07 July 2025 20:34:52 -0400 (0:00:00.049) 0:00:25.848 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_firewall | length > 0", "skip_reason": "Conditional result was False" } TASK [Manage selinux for specified ports] ************************************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:148 Monday 07 July 2025 20:34:52 -0400 (0:00:00.047) 0:00:25.896 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_selinux_ports | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Keep track of users that need to cancel linger] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:155 Monday 07 July 2025 20:34:52 -0400 (0:00:00.049) 0:00:25.946 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_cancel_user_linger": [] }, "changed": false } TASK [fedora.linux_system_roles.podman : Handle certs.d files - present] ******* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:159 Monday 07 July 2025 20:34:52 -0400 (0:00:00.049) 0:00:25.995 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle credential files - present] **** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:168 Monday 07 July 2025 20:34:53 -0400 (0:00:00.031) 0:00:26.027 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle secrets] *********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:177 Monday 07 July 2025 20:34:53 -0400 (0:00:00.029) 0:00:26.056 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle Kubernetes specifications] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:184 Monday 07 July 2025 20:34:53 -0400 (0:00:00.030) 0:00:26.087 *********** skipping: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Handle Quadlet specifications] ******** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:191 Monday 07 July 2025 20:34:53 -0400 (0:00:00.033) 0:00:26.121 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml for managed-node1 => (item=(censored due to no_log)) TASK [fedora.linux_system_roles.podman : Set per-container variables part 0] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:14 Monday 07 July 2025 20:34:53 -0400 (0:00:00.076) 0:00:26.197 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_quadlet_file_src": "", "__podman_quadlet_spec": {}, "__podman_quadlet_str": "", "__podman_quadlet_template_src": "" }, "changed": false } TASK [fedora.linux_system_roles.podman : Set per-container variables part 1] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:25 Monday 07 July 2025 20:34:53 -0400 (0:00:00.037) 0:00:26.235 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_continue_if_pull_fails": false, "__podman_pull_image": true, "__podman_state": "absent", "__podman_systemd_unit_scope": "", "__podman_user": "root" }, "changed": false } TASK [fedora.linux_system_roles.podman : Fail if no quadlet spec is given] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:35 Monday 07 July 2025 20:34:53 -0400 (0:00:00.078) 0:00:26.313 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_state != \"absent\"", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set per-container variables part 2] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:48 Monday 07 July 2025 20:34:53 -0400 (0:00:00.039) 0:00:26.353 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_quadlet_name": "nopull", "__podman_quadlet_type": "container", "__podman_rootless": false }, "changed": false } TASK [fedora.linux_system_roles.podman : Check user and group information] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:57 Monday 07 July 2025 20:34:53 -0400 (0:00:00.071) 0:00:26.424 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Get user information] ***************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:2 Monday 07 July 2025 20:34:53 -0400 (0:00:00.066) 0:00:26.491 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "'getent_passwd' not in ansible_facts or __podman_user not in ansible_facts['getent_passwd']", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user does not exist] ********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:9 Monday 07 July 2025 20:34:53 -0400 (0:00:00.055) 0:00:26.546 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not ansible_facts[\"getent_passwd\"][__podman_user]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set group for podman user] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:16 Monday 07 July 2025 20:34:53 -0400 (0:00:00.054) 0:00:26.601 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_group": "0" }, "changed": false } TASK [fedora.linux_system_roles.podman : See if getsubids exists] ************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:31 Monday 07 July 2025 20:34:53 -0400 (0:00:00.056) 0:00:26.657 *********** ok: [managed-node1] => { "changed": false, "stat": { "atime": 1751934613.4192193, "attr_flags": "", "attributes": [], "block_size": 4096, "blocks": 32, "charset": "binary", "checksum": "bb5b46ffbafcaa8c4021f3c8b3cb8594f48ef34b", "ctime": 1751934581.384895, "dev": 51713, "device_type": 0, "executable": true, "exists": true, "gid": 0, "gr_name": "root", "inode": 6986653, "isblk": false, "ischr": false, "isdir": false, "isfifo": false, "isgid": false, "islnk": false, "isreg": true, "issock": false, "isuid": false, "mimetype": "application/x-sharedlib", "mode": "0755", "mtime": 1700557386.0, "nlink": 1, "path": "/usr/bin/getsubids", "pw_name": "root", "readable": true, "rgrp": true, "roth": true, "rusr": true, "size": 12640, "uid": 0, "version": "4263604762", "wgrp": false, "woth": false, "writeable": true, "wusr": true, "xgrp": true, "xoth": true, "xusr": true } } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subuids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:42 Monday 07 July 2025 20:34:54 -0400 (0:00:00.368) 0:00:27.026 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check with getsubids for user subgids] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:47 Monday 07 July 2025 20:34:54 -0400 (0:00:00.035) 0:00:27.062 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:52 Monday 07 July 2025 20:34:54 -0400 (0:00:00.035) 0:00:27.097 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_user not in [\"root\", \"0\"]", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subuid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:65 Monday 07 July 2025 20:34:54 -0400 (0:00:00.037) 0:00:27.135 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get subgid file] ********************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:70 Monday 07 July 2025 20:34:54 -0400 (0:00:00.033) 0:00:27.168 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set user subuid and subgid info] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:75 Monday 07 July 2025 20:34:54 -0400 (0:00:00.029) 0:00:27.197 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subuid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:85 Monday 07 July 2025 20:34:54 -0400 (0:00:00.030) 0:00:27.228 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if user not in subgid file] ****** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:92 Monday 07 July 2025 20:34:54 -0400 (0:00:00.029) 0:00:27.257 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_stat_getsubids.stat.exists", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set per-container variables part 3] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:62 Monday 07 July 2025 20:34:54 -0400 (0:00:00.030) 0:00:27.287 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_activate_systemd_unit": true, "__podman_images_found": [], "__podman_kube_yamls_raw": "", "__podman_service_name": "nopull.service", "__podman_systemd_scope": "system", "__podman_user_home_dir": "/root", "__podman_xdg_runtime_dir": "/run/user/0" }, "changed": false } TASK [fedora.linux_system_roles.podman : Set per-container variables part 4] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:73 Monday 07 July 2025 20:34:54 -0400 (0:00:00.057) 0:00:27.345 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_quadlet_path": "/etc/containers/systemd" }, "changed": false } TASK [fedora.linux_system_roles.podman : Get kube yaml contents] *************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:77 Monday 07 July 2025 20:34:54 -0400 (0:00:00.030) 0:00:27.375 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_state != \"absent\"", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set per-container variables part 5] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:88 Monday 07 July 2025 20:34:54 -0400 (0:00:00.084) 0:00:27.460 *********** ok: [managed-node1] => { "ansible_facts": { "__podman_images": [], "__podman_quadlet_file": "/etc/containers/systemd/nopull.container", "__podman_volumes": [] }, "changed": false } TASK [fedora.linux_system_roles.podman : Set per-container variables part 6] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:106 Monday 07 July 2025 20:34:54 -0400 (0:00:00.087) 0:00:27.548 *********** ok: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Cleanup quadlets] ********************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_quadlet_spec.yml:113 Monday 07 July 2025 20:34:54 -0400 (0:00:00.046) 0:00:27.594 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/cleanup_quadlet_spec.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Stat XDG_RUNTIME_DIR] ***************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/cleanup_quadlet_spec.yml:4 Monday 07 July 2025 20:34:54 -0400 (0:00:00.077) 0:00:27.672 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_rootless | bool", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Stop and disable service] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/cleanup_quadlet_spec.yml:12 Monday 07 July 2025 20:34:54 -0400 (0:00:00.028) 0:00:27.701 *********** ok: [managed-node1] => { "changed": false, "failed_when_result": false } MSG: Could not find the requested service nopull.service: host TASK [fedora.linux_system_roles.podman : See if quadlet file exists] *********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/cleanup_quadlet_spec.yml:34 Monday 07 July 2025 20:34:55 -0400 (0:00:00.747) 0:00:28.449 *********** ok: [managed-node1] => { "changed": false, "stat": { "atime": 1751934878.2269151, "attr_flags": "", "attributes": [], "block_size": 4096, "blocks": 8, "charset": "us-ascii", "checksum": "670d64fc68a9768edb20cad26df2acc703542d85", "ctime": 1751934878.230915, "dev": 51713, "device_type": 0, "executable": false, "exists": true, "gid": 0, "gr_name": "root", "inode": 52429002, "isblk": false, "ischr": false, "isdir": false, "isfifo": false, "isgid": false, "islnk": false, "isreg": true, "issock": false, "isuid": false, "mimetype": "text/plain", "mode": "0644", "mtime": 1751934877.8619115, "nlink": 1, "path": "/etc/containers/systemd/nopull.container", "pw_name": "root", "readable": true, "rgrp": true, "roth": true, "rusr": true, "size": 151, "uid": 0, "version": "846800825", "wgrp": false, "woth": false, "writeable": true, "wusr": true, "xgrp": false, "xoth": false, "xusr": false } } TASK [fedora.linux_system_roles.podman : Parse quadlet file] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/cleanup_quadlet_spec.yml:39 Monday 07 July 2025 20:34:55 -0400 (0:00:00.372) 0:00:28.821 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/parse_quadlet_file.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Slurp quadlet file] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/parse_quadlet_file.yml:6 Monday 07 July 2025 20:34:55 -0400 (0:00:00.090) 0:00:28.912 *********** ok: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Parse quadlet file] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/parse_quadlet_file.yml:12 Monday 07 July 2025 20:34:56 -0400 (0:00:00.489) 0:00:29.401 *********** fatal: [managed-node1]: FAILED! => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result" } TASK [Debug3] ****************************************************************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:270 Monday 07 July 2025 20:34:56 -0400 (0:00:00.037) 0:00:29.439 *********** fatal: [managed-node1]: FAILED! => { "changed": false, "cmd": "set -x\nset -o pipefail\nexec 1>&2\n#podman volume rm --all\n#podman network prune -f\npodman volume ls\npodman network ls\npodman secret ls\npodman container ls\npodman pod ls\npodman images\nsystemctl list-units | grep quadlet\n", "delta": "0:00:00.217019", "end": "2025-07-07 20:34:56.933901", "rc": 1, "start": "2025-07-07 20:34:56.716882" } STDERR: + set -o pipefail + exec + podman volume ls + podman network ls NETWORK ID NAME DRIVER 2f259bab93aa podman bridge a4dcf21f020e podman-default-kube-network bridge + podman secret ls ID NAME DRIVER CREATED UPDATED + podman container ls CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES + podman pod ls POD ID NAME STATUS CREATED INFRA ID # OF CONTAINERS + podman images REPOSITORY TAG IMAGE ID CREATED SIZE localhost/podman-pause 4.9.4-dev-1708535009 e367d92780ab 3 minutes ago 769 kB quay.io/libpod/registry 2.8.2 0030ba3d620c 23 months ago 24.6 MB localhost:5000/libpod/testimage 20210610 9f9ec7f2fdef 4 years ago 7.99 MB quay.io/libpod/testimage 20210610 9f9ec7f2fdef 4 years ago 7.99 MB + systemctl list-units + grep quadlet MSG: non-zero return code TASK [Cleanup user] ************************************************************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:299 Monday 07 July 2025 20:34:56 -0400 (0:00:00.554) 0:00:29.993 *********** TASK [fedora.linux_system_roles.podman : Set platform/version specific variables] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:3 Monday 07 July 2025 20:34:57 -0400 (0:00:00.075) 0:00:30.069 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Ensure ansible_facts used by role] **** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:3 Monday 07 July 2025 20:34:57 -0400 (0:00:00.050) 0:00:30.119 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_required_facts | difference(ansible_facts.keys() | list) | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check if system is ostree] ************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:11 Monday 07 July 2025 20:34:57 -0400 (0:00:00.072) 0:00:30.192 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_ostree is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set flag to indicate system is ostree] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:16 Monday 07 July 2025 20:34:57 -0400 (0:00:00.033) 0:00:30.225 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_ostree is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Check if transactional-update exists in /sbin] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:23 Monday 07 July 2025 20:34:57 -0400 (0:00:00.048) 0:00:30.274 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_transactional is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set flag if transactional-update exists] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:28 Monday 07 July 2025 20:34:57 -0400 (0:00:00.045) 0:00:30.320 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "not __podman_is_transactional is defined", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Set platform/version specific variables] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:32 Monday 07 July 2025 20:34:57 -0400 (0:00:00.033) 0:00:30.353 *********** ok: [managed-node1] => (item=RedHat.yml) => { "ansible_facts": { "__podman_packages": [ "podman", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/RedHat.yml" ], "ansible_loop_var": "item", "changed": false, "item": "RedHat.yml" } skipping: [managed-node1] => (item=CentOS.yml) => { "ansible_loop_var": "item", "changed": false, "false_condition": "__vars_file is file", "item": "CentOS.yml", "skip_reason": "Conditional result was False" } ok: [managed-node1] => (item=CentOS_8.yml) => { "ansible_facts": { "__podman_packages": [ "crun", "podman", "podman-plugins", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/CentOS_8.yml" ], "ansible_loop_var": "item", "changed": false, "item": "CentOS_8.yml" } ok: [managed-node1] => (item=CentOS_8.yml) => { "ansible_facts": { "__podman_packages": [ "crun", "podman", "podman-plugins", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/vars/CentOS_8.yml" ], "ansible_loop_var": "item", "changed": false, "item": "CentOS_8.yml" } TASK [fedora.linux_system_roles.podman : Gather the package facts] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 Monday 07 July 2025 20:34:57 -0400 (0:00:00.086) 0:00:30.439 *********** ok: [managed-node1] => { "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false } TASK [fedora.linux_system_roles.podman : Enable copr if requested] ************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:10 Monday 07 July 2025 20:34:58 -0400 (0:00:01.492) 0:00:31.931 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_use_copr | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Ensure required packages are installed] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:14 Monday 07 July 2025 20:34:58 -0400 (0:00:00.049) 0:00:31.981 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "(__podman_packages | difference(ansible_facts.packages)) | list | length > 0", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Notify user that reboot is needed to apply changes] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:28 Monday 07 July 2025 20:34:59 -0400 (0:00:00.061) 0:00:32.043 *********** skipping: [managed-node1] => { "false_condition": "__podman_is_transactional | d(false)" } TASK [fedora.linux_system_roles.podman : Reboot transactional update systems] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:33 Monday 07 July 2025 20:34:59 -0400 (0:00:00.048) 0:00:32.092 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_is_transactional | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Fail if reboot is needed and not set] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:38 Monday 07 July 2025 20:34:59 -0400 (0:00:00.046) 0:00:32.138 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__podman_is_transactional | d(false)", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Get podman version] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:46 Monday 07 July 2025 20:34:59 -0400 (0:00:00.046) 0:00:32.184 *********** ok: [managed-node1] => { "changed": false, "cmd": [ "podman", "--version" ], "delta": "0:00:00.027672", "end": "2025-07-07 20:34:59.512148", "rc": 0, "start": "2025-07-07 20:34:59.484476" } STDOUT: podman version 4.9.4-dev TASK [fedora.linux_system_roles.podman : Set podman version] ******************* task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:52 Monday 07 July 2025 20:34:59 -0400 (0:00:00.399) 0:00:32.584 *********** ok: [managed-node1] => { "ansible_facts": { "podman_version": "4.9.4-dev" }, "changed": false } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.2 or later] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:56 Monday 07 July 2025 20:34:59 -0400 (0:00:00.037) 0:00:32.621 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_version is version(\"4.2\", \"<\")", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.4 or later for quadlet, secrets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:63 Monday 07 July 2025 20:34:59 -0400 (0:00:00.028) 0:00:32.650 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "podman_version is version(\"4.4\", \"<\")", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 4.4 or later for quadlet, secrets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:73 Monday 07 July 2025 20:34:59 -0400 (0:00:00.060) 0:00:32.710 *********** META: end_host conditional evaluated to False, continuing execution for managed-node1 skipping: [managed-node1] => { "skip_reason": "end_host conditional evaluated to False, continuing execution for managed-node1" } MSG: end_host conditional evaluated to false, continuing execution for managed-node1 TASK [fedora.linux_system_roles.podman : Podman package version must be 5.0 or later for Pod quadlets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:80 Monday 07 July 2025 20:34:59 -0400 (0:00:00.100) 0:00:32.811 *********** skipping: [managed-node1] => { "changed": false, "false_condition": "__has_type_pod or __has_pod_file_ext or __has_pod_file_src_ext or __has_pod_template_src_ext or __has_pod_template_src_ext_j2", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Podman package version must be 5.0 or later for Pod quadlets] *** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:96 Monday 07 July 2025 20:34:59 -0400 (0:00:00.059) 0:00:32.871 *********** META: end_host conditional evaluated to False, continuing execution for managed-node1 skipping: [managed-node1] => { "skip_reason": "end_host conditional evaluated to False, continuing execution for managed-node1" } MSG: end_host conditional evaluated to false, continuing execution for managed-node1 TASK [fedora.linux_system_roles.podman : Check user and group information] ***** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:109 Monday 07 July 2025 20:34:59 -0400 (0:00:00.061) 0:00:32.932 *********** included: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml for managed-node1 TASK [fedora.linux_system_roles.podman : Get user information] ***************** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:2 Monday 07 July 2025 20:34:59 -0400 (0:00:00.058) 0:00:32.991 *********** ok: [managed-node1] => { "ansible_facts": { "getent_passwd": { "user_quadlet_basic": null } }, "changed": false } MSG: One or more supplied key could not be found in the database. TASK [fedora.linux_system_roles.podman : Fail if user does not exist] ********** task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:9 Monday 07 July 2025 20:35:00 -0400 (0:00:00.353) 0:00:33.345 *********** fatal: [managed-node1]: FAILED! => { "changed": false } MSG: The given podman user [user_quadlet_basic] does not exist - cannot continue TASK [Dump journal] ************************************************************ task path: /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:336 Monday 07 July 2025 20:35:00 -0400 (0:00:00.039) 0:00:33.384 *********** fatal: [managed-node1]: FAILED! => { "changed": false, "cmd": [ "journalctl", "-ex" ], "delta": "0:00:00.036524", "end": "2025-07-07 20:35:00.699117", "failed_when_result": true, "rc": 0, "start": "2025-07-07 20:35:00.662593" } STDOUT: -- Logs begin at Mon 2025-07-07 20:24:02 EDT, end at Mon 2025-07-07 20:35:00 EDT. -- Jul 07 20:31:19 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:19 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:19 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:20 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:20 managed-node1 platform-python[22146]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:20 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:20 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:20 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:20 managed-node1 systemd[1]: NetworkManager-dispatcher.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state. Jul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:20 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.sGRdhJ.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.sGRdhJ.mount has successfully entered the 'dead' state. Jul 07 20:31:20 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:21 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:21 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:21 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:21 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:21 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 40ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:22 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:22 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:22 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:23 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:23 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:23 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:23 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:23 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:24 managed-node1 platform-python[23011]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 40ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:24 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:24 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:24 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:24 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:24 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:25 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:25 managed-node1 platform-python[23363]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:31:25 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:25 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:25 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:25 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:26 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:26 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:26 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 29ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:26 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:26 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:27 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:27 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:27 managed-node1 platform-python[23886]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:31:27 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:27 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:27 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:28 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:28 managed-node1 platform-python[24157]: ansible-ansible.legacy.command Invoked with _raw_params=systemd-escape --template podman-kube@.service /etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:31:28 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:28 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:28 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:29 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:29 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:29 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:29 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:30 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:30 managed-node1 platform-python[24720]: ansible-stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:31:30 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:30 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:30 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:30 managed-node1 platform-python[24926]: ansible-file Invoked with path=/etc/containers/ansible-kubernetes.d state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:31 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:31 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:31 managed-node1 platform-python[25113]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:31 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:31 managed-node1 platform-python[25220]: ansible-ansible.legacy.file Invoked with owner=root group=0 mode=0644 dest=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _original_basename=tmpy1far6e3 recurse=False state=file path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:31 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:31 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:32 managed-node1 platform-python[25435]: ansible-containers.podman.podman_play Invoked with state=started kube_file=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml executable=podman annotation=None kube_file_content=None authfile=None build=None cert_dir=None configmap=None context_dir=None seccomp_profile_root=None username=None password=NOT_LOGGING_PARAMETER log_driver=None log_opt=None network=None tls_verify=None debug=None quiet=None recreate=None userns=None log_level=None quadlet_dir=None quadlet_filename=None quadlet_file_mode=None quadlet_options=None Jul 07 20:31:32 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:32 managed-node1 systemd[1]: Created slice cgroup machine-libpod_pod_26187f14f9c4b507874813d35719d651aec1c468a139d8f52b69af81b7eb9493.slice. -- Subject: Unit machine-libpod_pod_26187f14f9c4b507874813d35719d651aec1c468a139d8f52b69af81b7eb9493.slice has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit machine-libpod_pod_26187f14f9c4b507874813d35719d651aec1c468a139d8f52b69af81b7eb9493.slice has finished starting up. -- -- The start-up result is done. Jul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:32 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:32 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:32 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:33 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:33 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:33 managed-node1 platform-python[25787]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:33 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:33 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:33 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:34 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:34 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:34 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:34 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.gaXZHn.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.gaXZHn.mount has successfully entered the 'dead' state. Jul 07 20:31:34 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:35 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:35 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:35 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:35 managed-node1 platform-python[26426]: ansible-file Invoked with path=/etc/containers/systemd state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:35 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:35 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:36 managed-node1 platform-python[26644]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/systemd/auth_test_1_quadlet.container follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:31:36 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:36 managed-node1 platform-python[26744]: ansible-ansible.legacy.file Invoked with owner=root group=0 mode=0644 dest=/etc/containers/systemd/auth_test_1_quadlet.container _original_basename=systemd.j2 recurse=False state=file path=/etc/containers/systemd/auth_test_1_quadlet.container force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:31:36 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.lgCkUK.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.lgCkUK.mount has successfully entered the 'dead' state. Jul 07 20:31:36 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:36 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:36 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:37 managed-node1 platform-python[26973]: ansible-ansible.legacy.stat Invoked with path=/tmp/lsr_enzzya10_podman/auth/auth.json follow=True get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:31:37 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:37 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:37 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:37 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:38 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:38 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:38 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:38 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:39 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:39 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:39 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:39 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:40 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:40 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:40 managed-node1 platform-python[27704]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:40 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:40 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:40 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:41 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:41 managed-node1 platform-python[28002]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:31:41 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:41 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:41 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:41 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:42 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:42 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:42 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:42 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:42 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:43 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:43 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:43 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:43 managed-node1 platform-python[28520]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:43 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:43 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:44 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:44 managed-node1 platform-python[28782]: ansible-file Invoked with path=/root/.config/containers state=directory owner=root group=0 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:31:44 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:44 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:44 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:45 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:45 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:45 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:45 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:45 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:46 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:46 managed-node1 platform-python[29420]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:46 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:46 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:46 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:47 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:47 managed-node1 platform-python[29699]: ansible-ansible.legacy.command Invoked with _raw_params=systemd-escape --template podman-kube@.service /etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:31:47 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:47 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:47 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:47 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:48 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:48 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.XnSr0M.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.XnSr0M.mount has successfully entered the 'dead' state. Jul 07 20:31:48 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:48 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:48 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:49 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:49 managed-node1 platform-python[30302]: ansible-stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 40ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:49 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:49 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:49 managed-node1 platform-python[30516]: ansible-file Invoked with path=/etc/containers/ansible-kubernetes.d state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:31:49 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:50 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:50 managed-node1 platform-python[30709]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:31:50 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:50 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:50 managed-node1 platform-python[30820]: ansible-ansible.legacy.file Invoked with owner=root group=0 mode=0644 dest=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _original_basename=tmpk2notagu recurse=False state=file path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:50 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:51 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.Z88O18.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.Z88O18.mount has successfully entered the 'dead' state. Jul 07 20:31:51 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:51 managed-node1 platform-python[31008]: ansible-containers.podman.podman_play Invoked with state=started kube_file=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml executable=podman annotation=None kube_file_content=None authfile=None build=None cert_dir=None configmap=None context_dir=None seccomp_profile_root=None username=None password=NOT_LOGGING_PARAMETER log_driver=None log_opt=None network=None tls_verify=None debug=None quiet=None recreate=None userns=None log_level=None quadlet_dir=None quadlet_filename=None quadlet_file_mode=None quadlet_options=None Jul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:51 managed-node1 systemd[1]: Created slice cgroup machine-libpod_pod_1c5eaac72e7ad98e81aa8b06110c85ea50fb6de81ed2bd08a87824550176526c.slice. -- Subject: Unit machine-libpod_pod_1c5eaac72e7ad98e81aa8b06110c85ea50fb6de81ed2bd08a87824550176526c.slice has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit machine-libpod_pod_1c5eaac72e7ad98e81aa8b06110c85ea50fb6de81ed2bd08a87824550176526c.slice has finished starting up. -- -- The start-up result is done. Jul 07 20:31:51 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:51 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:51 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:51 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:52 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:52 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.KbsEoW.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.KbsEoW.mount has successfully entered the 'dead' state. Jul 07 20:31:52 managed-node1 platform-python[31375]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:31:52 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:52 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:52 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:52 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:53 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:53 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:53 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:53 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:53 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:54 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:54 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:54 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:54 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:55 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:55 managed-node1 platform-python[32129]: ansible-file Invoked with path=/etc/containers/systemd state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:55 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:55 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:55 managed-node1 platform-python[32352]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/systemd/auth_test_1_quadlet.container follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:31:55 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:56 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:56 managed-node1 platform-python[32463]: ansible-ansible.legacy.file Invoked with owner=root group=0 mode=0644 dest=/etc/containers/systemd/auth_test_1_quadlet.container _original_basename=systemd.j2 recurse=False state=file path=/etc/containers/systemd/auth_test_1_quadlet.container force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:56 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:56 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:56 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:56 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:57 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:57 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:57 managed-node1 platform-python[32793]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:57 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:57 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:57 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:59 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:59 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 40ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:31:59 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:00 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.mD2v1O.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.mD2v1O.mount has successfully entered the 'dead' state. Jul 07 20:32:00 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:00 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:00 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:00 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:01 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:01 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:01 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:01 managed-node1 platform-python[33742]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:01 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:01 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:02 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:02 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:02 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:02 managed-node1 platform-python[34021]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:02 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:02 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:03 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:03 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:03 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:03 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:03 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:04 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:04 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:04 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:04 managed-node1 platform-python[34528]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:04 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:04 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:05 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:05 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:05 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:05 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:05 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:06 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:06 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:06 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:06 managed-node1 platform-python[35007]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:06 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:06 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:07 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:07 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:07 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:07 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:07 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:08 managed-node1 platform-python[35379]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:08 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:08 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:08 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:08 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:09 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:09 managed-node1 platform-python[35649]: ansible-ansible.legacy.command Invoked with _raw_params=systemd-escape --template podman-kube@.service /etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:09 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:09 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:09 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:09 managed-node1 platform-python[35885]: ansible-systemd Invoked with name=podman-kube@-etc-containers-ansible\x2dkubernetes.d-auth_test_1_kube.yml.service scope=system state=stopped enabled=False daemon_reload=False daemon_reexec=False no_block=False force=None masked=None Jul 07 20:32:09 managed-node1 systemd[1]: Reloading. Jul 07 20:32:10 managed-node1 systemd[1]: Stopping A template for running K8s workloads via podman-kube-play... -- Subject: Unit podman-kube@-etc-containers-ansible\x2dkubernetes.d-auth_test_1_kube.yml.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit podman-kube@-etc-containers-ansible\x2dkubernetes.d-auth_test_1_kube.yml.service has begun shutting down. Jul 07 20:32:10 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.HMD3NQ.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.HMD3NQ.mount has successfully entered the 'dead' state. Jul 07 20:32:10 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74. -- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up. -- -- The start-up result is done. Jul 07 20:32:10 managed-node1 systemd[1]: libpod-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859.scope has successfully entered the 'dead' state. Jul 07 20:32:10 managed-node1 systemd[1]: libpod-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859.scope: Consumed 31ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859.scope completed and consumed the indicated resources. Jul 07 20:32:10 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state. Jul 07 20:32:10 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources. Jul 07 20:32:10 managed-node1 kernel: cni-podman1: port 1(veth81789425) entered disabled state Jul 07 20:32:10 managed-node1 kernel: device veth81789425 left promiscuous mode Jul 07 20:32:10 managed-node1 kernel: cni-podman1: port 1(veth81789425) entered disabled state Jul 07 20:32:10 managed-node1 systemd[1]: var-lib-containers-storage-overlay-a0264b07b668c5f99351ee5979367e21ea3e4db5eef7a31ae6e36f31a1ff3ac6-merged.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay-a0264b07b668c5f99351ee5979367e21ea3e4db5eef7a31ae6e36f31a1ff3ac6-merged.mount has successfully entered the 'dead' state. Jul 07 20:32:10 managed-node1 systemd[1]: run-netns-netns\x2da914b079\x2d5dce\x2d3fbb\x2d0751\x2d5a1358ca4a4d.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-netns-netns\x2da914b079\x2d5dce\x2d3fbb\x2d0751\x2d5a1358ca4a4d.mount has successfully entered the 'dead' state. Jul 07 20:32:10 managed-node1 systemd[1]: Removed slice cgroup machine-libpod_pod_0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae.slice. -- Subject: Unit machine-libpod_pod_0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae.slice has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit machine-libpod_pod_0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae.slice has finished shutting down. Jul 07 20:32:10 managed-node1 systemd[1]: machine-libpod_pod_0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae.slice: Consumed 8.805s CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit machine-libpod_pod_0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae.slice completed and consumed the indicated resources. Jul 07 20:32:10 managed-node1 systemd[1]: libpod-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7.scope has successfully entered the 'dead' state. Jul 07 20:32:10 managed-node1 systemd[1]: libpod-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7.scope: Consumed 34ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7.scope completed and consumed the indicated resources. Jul 07 20:32:10 managed-node1 podman[35963]: Pods stopped: Jul 07 20:32:10 managed-node1 podman[35963]: 0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae Jul 07 20:32:10 managed-node1 podman[35963]: Pods removed: Jul 07 20:32:10 managed-node1 podman[35963]: 0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae Jul 07 20:32:10 managed-node1 podman[35963]: Secrets removed: Jul 07 20:32:10 managed-node1 podman[35963]: Volumes removed: Jul 07 20:32:10 managed-node1 systemd[1]: podman-kube@-etc-containers-ansible\x2dkubernetes.d-auth_test_1_kube.yml.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit podman-kube@-etc-containers-ansible\x2dkubernetes.d-auth_test_1_kube.yml.service has successfully entered the 'dead' state. Jul 07 20:32:10 managed-node1 systemd[1]: Stopped A template for running K8s workloads via podman-kube-play. -- Subject: Unit podman-kube@-etc-containers-ansible\x2dkubernetes.d-auth_test_1_kube.yml.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit podman-kube@-etc-containers-ansible\x2dkubernetes.d-auth_test_1_kube.yml.service has finished shutting down. Jul 07 20:32:10 managed-node1 systemd[1]: var-lib-containers-storage-overlay-bef2e75cd4a1c6c29f14edd3c7277da84bdff203a6db927ab3ef03d04d42e329-merged.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay-bef2e75cd4a1c6c29f14edd3c7277da84bdff203a6db927ab3ef03d04d42e329-merged.mount has successfully entered the 'dead' state. Jul 07 20:32:10 managed-node1 systemd[1]: var-lib-containers-storage-overlay\x2dcontainers-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859-userdata-shm.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay\x2dcontainers-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859-userdata-shm.mount has successfully entered the 'dead' state. Jul 07 20:32:10 managed-node1 systemd[1]: var-lib-containers-storage-overlay-e7539ffa66e0669082b0b0eab1d85eebe740fd81b15c798adbcdf8f353278edd-merged.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay-e7539ffa66e0669082b0b0eab1d85eebe740fd81b15c798adbcdf8f353278edd-merged.mount has successfully entered the 'dead' state. Jul 07 20:32:10 managed-node1 systemd[1]: var-lib-containers-storage-overlay\x2dcontainers-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7-userdata-shm.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay\x2dcontainers-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7-userdata-shm.mount has successfully entered the 'dead' state. Jul 07 20:32:10 managed-node1 platform-python[36237]: ansible-stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:11 managed-node1 platform-python[36362]: ansible-containers.podman.podman_play Invoked with state=absent kube_file=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml executable=podman annotation=None kube_file_content=None authfile=None build=None cert_dir=None configmap=None context_dir=None seccomp_profile_root=None username=None password=NOT_LOGGING_PARAMETER log_driver=None log_opt=None network=None tls_verify=None debug=None quiet=None recreate=None userns=None log_level=None quadlet_dir=None quadlet_filename=None quadlet_file_mode=None quadlet_options=None Jul 07 20:32:11 managed-node1 platform-python[36362]: ansible-containers.podman.podman_play version: 4.9.4-dev, kube file /etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml Jul 07 20:32:11 managed-node1 platform-python[36498]: ansible-file Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml state=absent recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:12 managed-node1 platform-python[36621]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:14 managed-node1 platform-python[36746]: ansible-systemd Invoked with name=auth_test_1_quadlet.service scope=system state=stopped enabled=False force=True daemon_reload=False daemon_reexec=False no_block=False masked=None Jul 07 20:32:14 managed-node1 systemd[1]: Reloading. Jul 07 20:32:14 managed-node1 platform-python[36901]: ansible-stat Invoked with path=/etc/containers/systemd/auth_test_1_quadlet.container follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:15 managed-node1 platform-python[37149]: ansible-ansible.legacy.command Invoked with _raw_params=journalctl -ex _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:17 managed-node1 platform-python[37398]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:18 managed-node1 platform-python[37527]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:20 managed-node1 platform-python[37652]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:22 managed-node1 platform-python[37777]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:24 managed-node1 platform-python[37902]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:25 managed-node1 platform-python[38027]: ansible-ansible.legacy.command Invoked with _raw_params=systemd-escape --template podman-kube@.service /etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:25 managed-node1 platform-python[38151]: ansible-systemd Invoked with name=podman-kube@-etc-containers-ansible\x2dkubernetes.d-auth_test_1_kube.yml.service scope=system state=stopped enabled=False daemon_reload=False daemon_reexec=False no_block=False force=None masked=None Jul 07 20:32:26 managed-node1 platform-python[38278]: ansible-stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:26 managed-node1 platform-python[38401]: ansible-file Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml state=absent recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:27 managed-node1 platform-python[38524]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:29 managed-node1 platform-python[38649]: ansible-systemd Invoked with name=auth_test_1_quadlet.service scope=system state=stopped enabled=False force=True daemon_reload=False daemon_reexec=False no_block=False masked=None Jul 07 20:32:29 managed-node1 systemd[1]: Reloading. Jul 07 20:32:29 managed-node1 platform-python[38804]: ansible-stat Invoked with path=/etc/containers/systemd/auth_test_1_quadlet.container follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:30 managed-node1 platform-python[39052]: ansible-ansible.legacy.command Invoked with _raw_params=journalctl -ex _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:33 managed-node1 platform-python[39301]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:34 managed-node1 platform-python[39430]: ansible-getent Invoked with database=passwd key=auth_test_user1 fail_key=False service=None split=None Jul 07 20:32:34 managed-node1 platform-python[39554]: ansible-ansible.legacy.command Invoked with _raw_params=journalctl -ex _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:35 managed-node1 platform-python[39678]: ansible-user Invoked with name=auth_test_user1 state=absent non_unique=False force=False remove=False create_home=True system=False move_home=False append=False ssh_key_bits=0 ssh_key_type=rsa ssh_key_comment=ansible-generated on managed-node1 update_password=always uid=None group=None groups=None comment=None home=None shell=None password=NOT_LOGGING_PARAMETER login_class=None password_expire_max=None password_expire_min=None password_expire_warn=None hidden=None seuser=None skeleton=None generate_ssh_key=None ssh_key_file=None ssh_key_passphrase=NOT_LOGGING_PARAMETER expires=None password_lock=None local=None profile=None authorization=None role=None umask=None Jul 07 20:32:35 managed-node1 platform-python[39804]: ansible-file Invoked with path=/home/auth_test_user1 state=absent recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:36 managed-node1 platform-python[39927]: ansible-ansible.legacy.command Invoked with _raw_params=podman inspect podman_registry --format '{{range .}}{{range .Mounts}}{{if eq .Type "volume"}}{{.Name}}{{end}}{{end}}{{end}}' _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:36 managed-node1 platform-python[40058]: ansible-ansible.legacy.command Invoked with _raw_params=podman rm -f podman_registry _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:36 managed-node1 systemd[1]: libpod-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope has successfully entered the 'dead' state. Jul 07 20:32:36 managed-node1 systemd[1]: libpod-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope: Consumed 290ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope completed and consumed the indicated resources. Jul 07 20:32:36 managed-node1 kernel: cni-podman0: port 1(vethf474aada) entered disabled state Jul 07 20:32:36 managed-node1 kernel: device vethf474aada left promiscuous mode Jul 07 20:32:36 managed-node1 kernel: cni-podman0: port 1(vethf474aada) entered disabled state Jul 07 20:32:36 managed-node1 systemd[1]: run-netns-netns\x2d0f80910f\x2d0f2a\x2ddea6\x2d8cd8\x2dfd5fd57e9ef2.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-netns-netns\x2d0f80910f\x2d0f2a\x2ddea6\x2d8cd8\x2dfd5fd57e9ef2.mount has successfully entered the 'dead' state. Jul 07 20:32:36 managed-node1 systemd[1]: var-lib-containers-storage-overlay\x2dcontainers-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7-userdata-shm.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay\x2dcontainers-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7-userdata-shm.mount has successfully entered the 'dead' state. Jul 07 20:32:36 managed-node1 systemd[1]: var-lib-containers-storage-overlay-7a1c676216f60cbaa5d9869b5875719d7ec38ff22a557a447c21b392281f894a-merged.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay-7a1c676216f60cbaa5d9869b5875719d7ec38ff22a557a447c21b392281f894a-merged.mount has successfully entered the 'dead' state. Jul 07 20:32:36 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state. Jul 07 20:32:37 managed-node1 systemd[1]: libpod-conmon-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libpod-conmon-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope has successfully entered the 'dead' state. Jul 07 20:32:38 managed-node1 platform-python[40289]: ansible-ansible.legacy.command Invoked with _raw_params=podman volume rm b3c17191dae8c001c0511bbbe09617d4a57c3787f6e19f787f81800428f3f416 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:38 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state. Jul 07 20:32:38 managed-node1 platform-python[40419]: ansible-file Invoked with path=/tmp/lsr_enzzya10_podman state=absent recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:40 managed-node1 platform-python[40581]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d Jul 07 20:32:41 managed-node1 platform-python[40741]: ansible-stat Invoked with path=/run/ostree-booted follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:42 managed-node1 platform-python[40864]: ansible-stat Invoked with path=/sbin/transactional-update follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:44 managed-node1 platform-python[41112]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:45 managed-node1 platform-python[41241]: ansible-getent Invoked with database=passwd key=root fail_key=False service=None split=None Jul 07 20:32:45 managed-node1 platform-python[41365]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:47 managed-node1 platform-python[41490]: ansible-tempfile Invoked with state=directory prefix=lsr_podman_config_ suffix= path=None Jul 07 20:32:47 managed-node1 platform-python[41613]: ansible-ansible.legacy.command Invoked with _raw_params=tar --ignore-failed-read -c -P -v -p -f /tmp/lsr_podman_config_8qm8wgwl/backup.tar /etc/containers/containers.conf.d/50-systemroles.conf /etc/containers/registries.conf.d/50-systemroles.conf /etc/containers/storage.conf /etc/containers/policy.json _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:48 managed-node1 platform-python[41737]: ansible-user Invoked with name=user1 state=present non_unique=False force=False remove=False create_home=True system=False move_home=False append=False ssh_key_bits=0 ssh_key_type=rsa ssh_key_comment=ansible-generated on managed-node1 update_password=always uid=None group=None groups=None comment=None home=None shell=None password=NOT_LOGGING_PARAMETER login_class=None password_expire_max=None password_expire_min=None password_expire_warn=None hidden=None seuser=None skeleton=None generate_ssh_key=None ssh_key_file=None ssh_key_passphrase=NOT_LOGGING_PARAMETER expires=None password_lock=None local=None profile=None authorization=None role=None umask=None Jul 07 20:32:48 managed-node1 useradd[41742]: new group: name=user1, GID=1000 Jul 07 20:32:48 managed-node1 useradd[41742]: new user: name=user1, UID=1000, GID=1000, home=/home/user1, shell=/bin/bash Jul 07 20:32:50 managed-node1 platform-python[41995]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:51 managed-node1 platform-python[42124]: ansible-getent Invoked with database=passwd key=user1 fail_key=False service=None split=None Jul 07 20:32:51 managed-node1 platform-python[42248]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:52 managed-node1 platform-python[42373]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:52 managed-node1 platform-python[42497]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:53 managed-node1 platform-python[42621]: ansible-file Invoked with path=/home/user1/.config/containers/containers.conf.d state=directory owner=user1 group=user1 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:53 managed-node1 platform-python[42744]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:32:54 managed-node1 platform-python[42843]: ansible-ansible.legacy.copy Invoked with dest=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf owner=user1 group=user1 mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934773.4083917-13555-16022273701041/source _original_basename=tmpo5idzwrq follow=False checksum=b1776092f2908d76e11fd6af87267469b2c17d5a backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:54 managed-node1 platform-python[42968]: ansible-file Invoked with path=/home/user1/.config/containers/registries.conf.d state=directory owner=user1 group=user1 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:54 managed-node1 platform-python[43091]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:32:55 managed-node1 platform-python[43190]: ansible-ansible.legacy.copy Invoked with dest=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf owner=user1 group=user1 mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934774.589606-13584-198443904655296/source _original_basename=tmpq9zidsm3 follow=False checksum=fde25488ce7040f1639af7bfc88ed125318cc0b0 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:55 managed-node1 platform-python[43315]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:56 managed-node1 platform-python[43438]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/storage.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:32:56 managed-node1 platform-python[43537]: ansible-ansible.legacy.copy Invoked with dest=/home/user1/.config/containers/storage.conf owner=user1 group=user1 mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934775.8582168-13631-148070678999800/source _original_basename=tmpltolsywp follow=False checksum=38f015f4780579bd388dd955b42916199fd7fe19 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:56 managed-node1 platform-python[43662]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:57 managed-node1 platform-python[43785]: ansible-stat Invoked with path=/home/user1/.config/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:57 managed-node1 platform-python[43908]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/policy.json follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:32:57 managed-node1 platform-python[44007]: ansible-ansible.legacy.copy Invoked with dest=/home/user1/.config/containers/policy.json owner=user1 group=user1 mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934777.330279-13702-122659933500562/source _original_basename=tmpkmgqgexc follow=False checksum=6746c079ad563b735fc39f73d4876654b80b0a0d backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:32:58 managed-node1 platform-python[44132]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:32:59 managed-node1 platform-python[44257]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:32:59 managed-node1 platform-python[44381]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:00 managed-node1 platform-python[44505]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:01 managed-node1 platform-python[44852]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:02 managed-node1 platform-python[44977]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:02 managed-node1 platform-python[45101]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:03 managed-node1 platform-python[45225]: ansible-stat Invoked with path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:03 managed-node1 platform-python[45350]: ansible-stat Invoked with path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:03 managed-node1 platform-python[45475]: ansible-stat Invoked with path=/home/user1/.config/containers/storage.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:04 managed-node1 platform-python[45600]: ansible-stat Invoked with path=/home/user1/.config/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:04 managed-node1 platform-python[45725]: ansible-ansible.legacy.command Invoked with _raw_params=grep 'container_name_as_hostname[ ]*=[ ]*true' /home/user1/.config/containers/containers.conf.d/50-systemroles.conf _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:07 managed-node1 platform-python[45974]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:08 managed-node1 platform-python[46103]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:08 managed-node1 platform-python[46228]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:08 managed-node1 platform-python[46352]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:09 managed-node1 platform-python[46476]: ansible-file Invoked with path=/home/user1/.config/containers/containers.conf.d state=directory owner=user1 group=user1 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:09 managed-node1 platform-python[46599]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:10 managed-node1 platform-python[46663]: ansible-ansible.legacy.file Invoked with owner=user1 group=user1 mode=0644 dest=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf _original_basename=tmpsld9zrjm recurse=False state=file path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:10 managed-node1 platform-python[46786]: ansible-file Invoked with path=/home/user1/.config/containers/registries.conf.d state=directory owner=user1 group=user1 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:11 managed-node1 platform-python[46909]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:11 managed-node1 platform-python[46973]: ansible-ansible.legacy.file Invoked with owner=user1 group=user1 mode=0644 dest=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf _original_basename=tmpk0q11pu7 recurse=False state=file path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:11 managed-node1 platform-python[47096]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:12 managed-node1 platform-python[47219]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/storage.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:12 managed-node1 platform-python[47283]: ansible-ansible.legacy.file Invoked with owner=user1 group=user1 mode=0644 dest=/home/user1/.config/containers/storage.conf _original_basename=tmpb7cut1r3 recurse=False state=file path=/home/user1/.config/containers/storage.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:12 managed-node1 platform-python[47406]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:13 managed-node1 platform-python[47529]: ansible-stat Invoked with path=/home/user1/.config/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:13 managed-node1 platform-python[47654]: ansible-slurp Invoked with path=/home/user1/.config/containers/policy.json src=/home/user1/.config/containers/policy.json Jul 07 20:33:14 managed-node1 platform-python[47777]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:14 managed-node1 platform-python[47902]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:15 managed-node1 platform-python[48026]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:15 managed-node1 platform-python[48150]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:17 managed-node1 platform-python[48460]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:18 managed-node1 platform-python[48585]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:18 managed-node1 platform-python[48709]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:19 managed-node1 platform-python[48833]: ansible-stat Invoked with path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:19 managed-node1 platform-python[48958]: ansible-stat Invoked with path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:20 managed-node1 platform-python[49083]: ansible-stat Invoked with path=/home/user1/.config/containers/storage.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:20 managed-node1 platform-python[49208]: ansible-stat Invoked with path=/home/user1/.config/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:22 managed-node1 platform-python[49458]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:23 managed-node1 platform-python[49587]: ansible-getent Invoked with database=passwd key=root fail_key=False service=None split=None Jul 07 20:33:24 managed-node1 platform-python[49711]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:24 managed-node1 platform-python[49836]: ansible-file Invoked with path=/etc/containers/containers.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:25 managed-node1 platform-python[49959]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:25 managed-node1 platform-python[50058]: ansible-ansible.legacy.copy Invoked with dest=/etc/containers/containers.conf.d/50-systemroles.conf owner=root mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934805.1493864-14753-170699386031760/source _original_basename=tmp5gsrdcbw follow=False checksum=b1776092f2908d76e11fd6af87267469b2c17d5a backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:26 managed-node1 platform-python[50183]: ansible-file Invoked with path=/etc/containers/registries.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:26 managed-node1 platform-python[50306]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:26 managed-node1 platform-python[50405]: ansible-ansible.legacy.copy Invoked with dest=/etc/containers/registries.conf.d/50-systemroles.conf owner=root mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934806.275409-14790-40277132360154/source _original_basename=tmpflqhaxry follow=False checksum=fde25488ce7040f1639af7bfc88ed125318cc0b0 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:27 managed-node1 platform-python[50530]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:27 managed-node1 platform-python[50653]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/storage.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:27 managed-node1 platform-python[50754]: ansible-ansible.legacy.copy Invoked with dest=/etc/containers/storage.conf owner=root mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934807.4339185-14833-193871550331891/source _original_basename=tmpsrbhn_xl follow=False checksum=38f015f4780579bd388dd955b42916199fd7fe19 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:28 managed-node1 platform-python[50879]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:28 managed-node1 platform-python[51002]: ansible-stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:29 managed-node1 platform-python[51127]: ansible-slurp Invoked with path=/etc/containers/policy.json src=/etc/containers/policy.json Jul 07 20:33:29 managed-node1 platform-python[51250]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:29 managed-node1 platform-python[51351]: ansible-ansible.legacy.copy Invoked with dest=/etc/containers/policy.json owner=root mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934809.331465-14916-21787524891337/source _original_basename=tmpaykbdix_ follow=False checksum=6746c079ad563b735fc39f73d4876654b80b0a0d backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:30 managed-node1 platform-python[51476]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:31 managed-node1 platform-python[51601]: ansible-file Invoked with path=/root/.config/containers state=directory owner=root group=0 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:33 managed-node1 platform-python[51950]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:34 managed-node1 platform-python[52075]: ansible-stat Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:34 managed-node1 platform-python[52200]: ansible-stat Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:34 managed-node1 platform-python[52325]: ansible-stat Invoked with path=/etc/containers/storage.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:35 managed-node1 platform-python[52450]: ansible-stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:38 managed-node1 platform-python[52700]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:39 managed-node1 platform-python[52829]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:39 managed-node1 platform-python[52954]: ansible-file Invoked with path=/etc/containers/containers.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:40 managed-node1 platform-python[53077]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:40 managed-node1 platform-python[53141]: ansible-ansible.legacy.file Invoked with owner=root mode=0644 dest=/etc/containers/containers.conf.d/50-systemroles.conf _original_basename=tmpfcrntls4 recurse=False state=file path=/etc/containers/containers.conf.d/50-systemroles.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:40 managed-node1 platform-python[53264]: ansible-file Invoked with path=/etc/containers/registries.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:41 managed-node1 platform-python[53387]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:41 managed-node1 platform-python[53451]: ansible-ansible.legacy.file Invoked with owner=root mode=0644 dest=/etc/containers/registries.conf.d/50-systemroles.conf _original_basename=tmplmlkwsp6 recurse=False state=file path=/etc/containers/registries.conf.d/50-systemroles.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:42 managed-node1 platform-python[53574]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:42 managed-node1 platform-python[53697]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/storage.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:42 managed-node1 platform-python[53761]: ansible-ansible.legacy.file Invoked with owner=root mode=0644 dest=/etc/containers/storage.conf _original_basename=tmpgfldooqj recurse=False state=file path=/etc/containers/storage.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:43 managed-node1 platform-python[53884]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:43 managed-node1 platform-python[54007]: ansible-stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:44 managed-node1 platform-python[54132]: ansible-slurp Invoked with path=/etc/containers/policy.json src=/etc/containers/policy.json Jul 07 20:33:45 managed-node1 platform-python[54255]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:45 managed-node1 platform-python[54380]: ansible-file Invoked with path=/root/.config/containers state=directory owner=root group=0 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:47 managed-node1 platform-python[54690]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:48 managed-node1 platform-python[54815]: ansible-stat Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:48 managed-node1 platform-python[54940]: ansible-stat Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:49 managed-node1 platform-python[55065]: ansible-stat Invoked with path=/etc/containers/storage.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:49 managed-node1 platform-python[55190]: ansible-stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:50 managed-node1 platform-python[55315]: ansible-slurp Invoked with path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf src=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf Jul 07 20:33:50 managed-node1 platform-python[55438]: ansible-slurp Invoked with path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf src=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf Jul 07 20:33:51 managed-node1 platform-python[55561]: ansible-slurp Invoked with path=/home/user1/.config/containers/storage.conf src=/home/user1/.config/containers/storage.conf Jul 07 20:33:51 managed-node1 platform-python[55684]: ansible-slurp Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf src=/etc/containers/containers.conf.d/50-systemroles.conf Jul 07 20:33:51 managed-node1 platform-python[55807]: ansible-slurp Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf src=/etc/containers/registries.conf.d/50-systemroles.conf Jul 07 20:33:52 managed-node1 platform-python[55930]: ansible-slurp Invoked with path=/etc/containers/storage.conf src=/etc/containers/storage.conf Jul 07 20:33:55 managed-node1 platform-python[56178]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:33:56 managed-node1 platform-python[56307]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:33:56 managed-node1 platform-python[56432]: ansible-file Invoked with path=/etc/containers/containers.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:57 managed-node1 platform-python[56555]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:57 managed-node1 platform-python[56656]: ansible-ansible.legacy.copy Invoked with dest=/etc/containers/containers.conf.d/50-systemroles.conf owner=root mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934837.1165416-15806-11049734104554/source _original_basename=tmpkiwyq02_ follow=False checksum=9694c1d1c700a6435eecf4066b052584f4ee94c0 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:58 managed-node1 platform-python[56781]: ansible-file Invoked with path=/etc/containers/registries.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:58 managed-node1 platform-python[56904]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:58 managed-node1 platform-python[56968]: ansible-ansible.legacy.file Invoked with owner=root mode=0644 dest=/etc/containers/registries.conf.d/50-systemroles.conf _original_basename=tmpxg73mi7m recurse=False state=file path=/etc/containers/registries.conf.d/50-systemroles.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:59 managed-node1 platform-python[57091]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:33:59 managed-node1 platform-python[57214]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/storage.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:33:59 managed-node1 platform-python[57278]: ansible-ansible.legacy.file Invoked with owner=root mode=0644 dest=/etc/containers/storage.conf _original_basename=tmp8ws7ml82 recurse=False state=file path=/etc/containers/storage.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:00 managed-node1 platform-python[57401]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:00 managed-node1 platform-python[57524]: ansible-stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:01 managed-node1 platform-python[57649]: ansible-slurp Invoked with path=/etc/containers/policy.json src=/etc/containers/policy.json Jul 07 20:34:02 managed-node1 platform-python[57772]: ansible-slurp Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf src=/etc/containers/containers.conf.d/50-systemroles.conf Jul 07 20:34:02 managed-node1 platform-python[57895]: ansible-file Invoked with state=absent path=/etc/containers/containers.conf.d/50-systemroles.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:02 managed-node1 platform-python[58018]: ansible-file Invoked with state=absent path=/etc/containers/registries.conf.d/50-systemroles.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:03 managed-node1 platform-python[58141]: ansible-file Invoked with state=absent path=/etc/containers/storage.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:03 managed-node1 platform-python[58264]: ansible-file Invoked with state=absent path=/etc/containers/policy.json recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:03 managed-node1 platform-python[58387]: ansible-file Invoked with state=absent path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:04 managed-node1 platform-python[58510]: ansible-file Invoked with state=absent path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:04 managed-node1 platform-python[58633]: ansible-file Invoked with state=absent path=/home/user1/.config/containers/storage.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:04 managed-node1 platform-python[58756]: ansible-file Invoked with state=absent path=/home/user1/.config/containers/policy.json recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:05 managed-node1 platform-python[58879]: ansible-file Invoked with state=absent path=/root/.config/containers/auth.json recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:05 managed-node1 platform-python[59002]: ansible-file Invoked with state=absent path=/home/user1/.config/containers/auth.json recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:05 managed-node1 platform-python[59125]: ansible-ansible.legacy.command Invoked with _raw_params=tar xfvpP /tmp/lsr_podman_config_8qm8wgwl/backup.tar _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:34:06 managed-node1 platform-python[59249]: ansible-file Invoked with state=absent path=/tmp/lsr_podman_config_8qm8wgwl recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:08 managed-node1 platform-python[59411]: ansible-setup Invoked with gather_subset=['!all', '!min', 'distribution', 'distribution_major_version', 'distribution_version', 'os_family'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d Jul 07 20:34:08 managed-node1 platform-python[59538]: ansible-stat Invoked with path=/run/ostree-booted follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:09 managed-node1 platform-python[59661]: ansible-stat Invoked with path=/sbin/transactional-update follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:12 managed-node1 platform-python[59909]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:34:12 managed-node1 platform-python[60038]: ansible-getent Invoked with database=passwd key=root fail_key=False service=None split=None Jul 07 20:34:13 managed-node1 platform-python[60162]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:16 managed-node1 platform-python[60326]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d Jul 07 20:34:19 managed-node1 platform-python[60486]: ansible-stat Invoked with path=/run/ostree-booted follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:20 managed-node1 platform-python[60609]: ansible-stat Invoked with path=/sbin/transactional-update follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:22 managed-node1 platform-python[60857]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:34:23 managed-node1 platform-python[60986]: ansible-getent Invoked with database=passwd key=root fail_key=False service=None split=None Jul 07 20:34:24 managed-node1 platform-python[61110]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:27 managed-node1 platform-python[61274]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d Jul 07 20:34:28 managed-node1 platform-python[61434]: ansible-stat Invoked with path=/run/ostree-booted follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:29 managed-node1 platform-python[61557]: ansible-stat Invoked with path=/sbin/transactional-update follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:31 managed-node1 platform-python[61805]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:34:32 managed-node1 platform-python[61934]: ansible-getent Invoked with database=passwd key=root fail_key=False service=None split=None Jul 07 20:34:33 managed-node1 platform-python[62058]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:35 managed-node1 platform-python[62183]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:37 managed-node1 platform-python[62308]: ansible-file Invoked with path=/etc/containers/systemd state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:37 managed-node1 platform-python[62431]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/systemd/nopull.container follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:34:38 managed-node1 platform-python[62530]: ansible-ansible.legacy.copy Invoked with src=/root/.ansible/tmp/ansible-tmp-1751934877.5450642-17711-142143421897050/source dest=/etc/containers/systemd/nopull.container owner=root group=0 mode=0644 follow=False _original_basename=systemd.j2 checksum=670d64fc68a9768edb20cad26df2acc703542d85 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:41 managed-node1 platform-python[62780]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:34:41 managed-node1 platform-python[62909]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:44 managed-node1 platform-python[63034]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:45 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state. Jul 07 20:34:46 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state. Jul 07 20:34:46 managed-node1 platform-python[63296]: ansible-file Invoked with path=/etc/containers/systemd state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:47 managed-node1 platform-python[63419]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/systemd/bogus.container follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True Jul 07 20:34:47 managed-node1 platform-python[63518]: ansible-ansible.legacy.copy Invoked with src=/root/.ansible/tmp/ansible-tmp-1751934886.8113573-18040-140717157966343/source dest=/etc/containers/systemd/bogus.container owner=root group=0 mode=0644 follow=False _original_basename=systemd.j2 checksum=1d087e679d135214e8ac9ccaf33b2222916efb7f backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None Jul 07 20:34:50 managed-node1 platform-python[63768]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:34:51 managed-node1 platform-python[63897]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:53 managed-node1 platform-python[64022]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:55 managed-node1 platform-python[64147]: ansible-systemd Invoked with name=nopull.service scope=system state=stopped enabled=False force=True daemon_reload=False daemon_reexec=False no_block=False masked=None Jul 07 20:34:55 managed-node1 platform-python[64273]: ansible-stat Invoked with path=/etc/containers/systemd/nopull.container follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 Jul 07 20:34:56 managed-node1 platform-python[64521]: ansible-ansible.legacy.command Invoked with _raw_params=set -x set -o pipefail exec 1>&2 #podman volume rm --all #podman network prune -f podman volume ls podman network ls podman secret ls podman container ls podman pod ls podman images systemctl list-units | grep quadlet _uses_shell=True expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:34:56 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state. Jul 07 20:34:57 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state. Jul 07 20:34:59 managed-node1 platform-python[64841]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 07 20:35:00 managed-node1 platform-python[64970]: ansible-getent Invoked with database=passwd key=user_quadlet_basic fail_key=False service=None split=None Jul 07 20:35:00 managed-node1 platform-python[65094]: ansible-ansible.legacy.command Invoked with _raw_params=journalctl -ex _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None PLAY RECAP ********************************************************************* managed-node1 : ok=105 changed=2 unreachable=0 failed=2 skipped=190 rescued=2 ignored=0 SYSTEM ROLES ERRORS BEGIN v1 [ { "ansible_version": "2.16.14", "end_time": "2025-07-08T00:34:56.423120+00:00Z", "host": "managed-node1", "message": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "start_time": "2025-07-08T00:34:56.405298+00:00Z", "task_name": "Parse quadlet file", "task_path": "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/parse_quadlet_file.yml:12" }, { "ansible_version": "2.16.14", "delta": "0:00:00.217019", "end_time": "2025-07-07 20:34:56.933901", "host": "managed-node1", "message": "non-zero return code", "rc": 1, "start_time": "2025-07-07 20:34:56.716882", "stderr": "+ set -o pipefail\n+ exec\n+ podman volume ls\n+ podman network ls\nNETWORK ID NAME DRIVER\n2f259bab93aa podman bridge\na4dcf21f020e podman-default-kube-network bridge\n+ podman secret ls\nID NAME DRIVER CREATED UPDATED\n+ podman container ls\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\n+ podman pod ls\nPOD ID NAME STATUS CREATED INFRA ID # OF CONTAINERS\n+ podman images\nREPOSITORY TAG IMAGE ID CREATED SIZE\nlocalhost/podman-pause 4.9.4-dev-1708535009 e367d92780ab 3 minutes ago 769 kB\nquay.io/libpod/registry 2.8.2 0030ba3d620c 23 months ago 24.6 MB\nlocalhost:5000/libpod/testimage 20210610 9f9ec7f2fdef 4 years ago 7.99 MB\nquay.io/libpod/testimage 20210610 9f9ec7f2fdef 4 years ago 7.99 MB\n+ systemctl list-units\n+ grep quadlet", "task_name": "Debug3", "task_path": "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:270" }, { "ansible_version": "2.16.14", "end_time": "2025-07-08T00:35:00.369047+00:00Z", "host": "managed-node1", "message": "The given podman user [user_quadlet_basic] does not exist - cannot continue\n", "start_time": "2025-07-08T00:35:00.349036+00:00Z", "task_name": "Fail if user does not exist", "task_path": "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:9" }, { "ansible_version": "2.16.14", "delta": "0:00:00.036524", "end_time": "2025-07-07 20:35:00.699117", "host": "managed-node1", "message": "", "rc": 0, "start_time": "2025-07-07 20:35:00.662593", "stdout": "-- Logs begin at Mon 2025-07-07 20:24:02 EDT, end at Mon 2025-07-07 20:35:00 EDT. --\nJul 07 20:31:19 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:19 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:19 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:19 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:20 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:20 managed-node1 platform-python[22146]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:20 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:20 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:20 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:20 managed-node1 systemd[1]: NetworkManager-dispatcher.service: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.\nJul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:20 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:20 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.sGRdhJ.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.sGRdhJ.mount has successfully entered the 'dead' state.\nJul 07 20:31:20 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:21 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:21 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:21 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:21 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:21 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:21 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 40ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:22 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:22 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:22 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:22 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:23 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:23 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:23 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:23 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:23 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:23 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:24 managed-node1 platform-python[23011]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 40ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:24 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:24 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:24 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:24 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:24 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:24 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:25 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:25 managed-node1 platform-python[23363]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:31:25 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:25 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:25 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:25 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:25 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:26 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:26 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:26 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 29ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:26 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:26 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:26 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:27 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:27 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:27 managed-node1 platform-python[23886]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:31:27 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:27 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:27 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:27 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:28 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:28 managed-node1 platform-python[24157]: ansible-ansible.legacy.command Invoked with _raw_params=systemd-escape --template podman-kube@.service /etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:31:28 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:28 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:28 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:28 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:29 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:29 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:29 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:29 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:29 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:30 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:30 managed-node1 platform-python[24720]: ansible-stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:31:30 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:30 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:30 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:30 managed-node1 platform-python[24926]: ansible-file Invoked with path=/etc/containers/ansible-kubernetes.d state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:30 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:31 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:31 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:31 managed-node1 platform-python[25113]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:31 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:31 managed-node1 platform-python[25220]: ansible-ansible.legacy.file Invoked with owner=root group=0 mode=0644 dest=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _original_basename=tmpy1far6e3 recurse=False state=file path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:31 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:31 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:31 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:32 managed-node1 platform-python[25435]: ansible-containers.podman.podman_play Invoked with state=started kube_file=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml executable=podman annotation=None kube_file_content=None authfile=None build=None cert_dir=None configmap=None context_dir=None seccomp_profile_root=None username=None password=NOT_LOGGING_PARAMETER log_driver=None log_opt=None network=None tls_verify=None debug=None quiet=None recreate=None userns=None log_level=None quadlet_dir=None quadlet_filename=None quadlet_file_mode=None quadlet_options=None\nJul 07 20:31:32 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:32 managed-node1 systemd[1]: Created slice cgroup machine-libpod_pod_26187f14f9c4b507874813d35719d651aec1c468a139d8f52b69af81b7eb9493.slice.\n-- Subject: Unit machine-libpod_pod_26187f14f9c4b507874813d35719d651aec1c468a139d8f52b69af81b7eb9493.slice has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit machine-libpod_pod_26187f14f9c4b507874813d35719d651aec1c468a139d8f52b69af81b7eb9493.slice has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:32 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:32 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:32 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:32 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:33 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:33 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:33 managed-node1 platform-python[25787]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:33 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:33 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:33 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:33 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:34 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:34 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:34 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:34 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.gaXZHn.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.gaXZHn.mount has successfully entered the 'dead' state.\nJul 07 20:31:34 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:34 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:35 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:35 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:35 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:35 managed-node1 platform-python[26426]: ansible-file Invoked with path=/etc/containers/systemd state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:35 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:35 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:35 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:36 managed-node1 platform-python[26644]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/systemd/auth_test_1_quadlet.container follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:31:36 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:36 managed-node1 platform-python[26744]: ansible-ansible.legacy.file Invoked with owner=root group=0 mode=0644 dest=/etc/containers/systemd/auth_test_1_quadlet.container _original_basename=systemd.j2 recurse=False state=file path=/etc/containers/systemd/auth_test_1_quadlet.container force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:31:36 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.lgCkUK.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.lgCkUK.mount has successfully entered the 'dead' state.\nJul 07 20:31:36 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:36 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:36 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:36 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:37 managed-node1 platform-python[26973]: ansible-ansible.legacy.stat Invoked with path=/tmp/lsr_enzzya10_podman/auth/auth.json follow=True get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:31:37 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:37 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:37 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:37 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:37 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:38 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:38 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:38 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:38 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:38 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:39 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:39 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:39 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:39 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:39 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:40 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:40 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:40 managed-node1 platform-python[27704]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:40 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:40 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:40 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:40 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:41 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:41 managed-node1 platform-python[28002]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:31:41 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:41 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:41 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:41 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:41 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:42 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:42 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:42 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:42 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:42 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:42 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:43 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:43 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:43 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:43 managed-node1 platform-python[28520]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:43 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:43 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:43 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:44 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:44 managed-node1 platform-python[28782]: ansible-file Invoked with path=/root/.config/containers state=directory owner=root group=0 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:31:44 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:44 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:44 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:44 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:45 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:45 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:45 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:45 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:45 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:45 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:46 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:46 managed-node1 platform-python[29420]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:46 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:46 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:46 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:46 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:47 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:47 managed-node1 platform-python[29699]: ansible-ansible.legacy.command Invoked with _raw_params=systemd-escape --template podman-kube@.service /etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:31:47 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:47 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:47 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:47 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:47 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:48 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:48 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.XnSr0M.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.XnSr0M.mount has successfully entered the 'dead' state.\nJul 07 20:31:48 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:48 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:48 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:48 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:49 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:49 managed-node1 platform-python[30302]: ansible-stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 40ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:49 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:49 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:49 managed-node1 platform-python[30516]: ansible-file Invoked with path=/etc/containers/ansible-kubernetes.d state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:31:49 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:49 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:50 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:50 managed-node1 platform-python[30709]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:31:50 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:50 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:50 managed-node1 platform-python[30820]: ansible-ansible.legacy.file Invoked with owner=root group=0 mode=0644 dest=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _original_basename=tmpk2notagu recurse=False state=file path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:50 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:50 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:51 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.Z88O18.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.Z88O18.mount has successfully entered the 'dead' state.\nJul 07 20:31:51 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:51 managed-node1 platform-python[31008]: ansible-containers.podman.podman_play Invoked with state=started kube_file=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml executable=podman annotation=None kube_file_content=None authfile=None build=None cert_dir=None configmap=None context_dir=None seccomp_profile_root=None username=None password=NOT_LOGGING_PARAMETER log_driver=None log_opt=None network=None tls_verify=None debug=None quiet=None recreate=None userns=None log_level=None quadlet_dir=None quadlet_filename=None quadlet_file_mode=None quadlet_options=None\nJul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:51 managed-node1 systemd[1]: Created slice cgroup machine-libpod_pod_1c5eaac72e7ad98e81aa8b06110c85ea50fb6de81ed2bd08a87824550176526c.slice.\n-- Subject: Unit machine-libpod_pod_1c5eaac72e7ad98e81aa8b06110c85ea50fb6de81ed2bd08a87824550176526c.slice has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit machine-libpod_pod_1c5eaac72e7ad98e81aa8b06110c85ea50fb6de81ed2bd08a87824550176526c.slice has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:51 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:51 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:51 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:51 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:51 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:52 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:52 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.KbsEoW.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.KbsEoW.mount has successfully entered the 'dead' state.\nJul 07 20:31:52 managed-node1 platform-python[31375]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:31:52 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:52 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:52 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:52 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:52 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:53 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:53 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:53 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:53 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:53 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:53 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:54 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:54 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:54 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:54 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:54 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:55 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:55 managed-node1 platform-python[32129]: ansible-file Invoked with path=/etc/containers/systemd state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:55 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:55 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:55 managed-node1 platform-python[32352]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/systemd/auth_test_1_quadlet.container follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:31:55 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:55 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:56 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:56 managed-node1 platform-python[32463]: ansible-ansible.legacy.file Invoked with owner=root group=0 mode=0644 dest=/etc/containers/systemd/auth_test_1_quadlet.container _original_basename=systemd.j2 recurse=False state=file path=/etc/containers/systemd/auth_test_1_quadlet.container force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:56 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:56 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:56 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:56 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:56 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:57 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:57 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:57 managed-node1 platform-python[32793]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:57 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:57 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:57 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:57 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:58 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:58 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:59 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:59 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 40ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:31:59 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:31:59 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:00 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.mD2v1O.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.mD2v1O.mount has successfully entered the 'dead' state.\nJul 07 20:32:00 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:00 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:00 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:00 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:00 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:01 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:01 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:01 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:01 managed-node1 platform-python[33742]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:01 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:01 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:01 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:02 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:02 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:02 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:02 managed-node1 platform-python[34021]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:02 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:02 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:02 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:03 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:03 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:03 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:03 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:03 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:03 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:04 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:04 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:04 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:04 managed-node1 platform-python[34528]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:04 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:04 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 36ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:04 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:05 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:05 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:05 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:05 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:05 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:05 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:06 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:06 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:06 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 39ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:06 managed-node1 platform-python[35007]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:06 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:06 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:06 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:07 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:07 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:07 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:07 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:07 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 33ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:07 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 38ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:08 managed-node1 platform-python[35379]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:08 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 30ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:08 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:08 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:08 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:08 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:09 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:09 managed-node1 platform-python[35649]: ansible-ansible.legacy.command Invoked with _raw_params=systemd-escape --template podman-kube@.service /etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:09 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 32ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:09 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 35ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:09 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:09 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:09 managed-node1 platform-python[35885]: ansible-systemd Invoked with name=podman-kube@-etc-containers-ansible\\x2dkubernetes.d-auth_test_1_kube.yml.service scope=system state=stopped enabled=False daemon_reload=False daemon_reexec=False no_block=False force=None masked=None\nJul 07 20:32:09 managed-node1 systemd[1]: Reloading.\nJul 07 20:32:10 managed-node1 systemd[1]: Stopping A template for running K8s workloads via podman-kube-play...\n-- Subject: Unit podman-kube@-etc-containers-ansible\\x2dkubernetes.d-auth_test_1_kube.yml.service has begun shutting down\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit podman-kube@-etc-containers-ansible\\x2dkubernetes.d-auth_test_1_kube.yml.service has begun shutting down.\nJul 07 20:32:10 managed-node1 systemd[1]: run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.HMD3NQ.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit run-runc-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74-runc.HMD3NQ.mount has successfully entered the 'dead' state.\nJul 07 20:32:10 managed-node1 systemd[1]: Started libcontainer container 0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.\n-- Subject: Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished start-up\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has finished starting up.\n-- \n-- The start-up result is done.\nJul 07 20:32:10 managed-node1 systemd[1]: libpod-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859.scope has successfully entered the 'dead' state.\nJul 07 20:32:10 managed-node1 systemd[1]: libpod-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859.scope: Consumed 31ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859.scope completed and consumed the indicated resources.\nJul 07 20:32:10 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope has successfully entered the 'dead' state.\nJul 07 20:32:10 managed-node1 systemd[1]: libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope: Consumed 37ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-0262785b0b946533c3164e354eb24cea847d66e5e3423ff2fa2783ac7b46bc74.scope completed and consumed the indicated resources.\nJul 07 20:32:10 managed-node1 kernel: cni-podman1: port 1(veth81789425) entered disabled state\nJul 07 20:32:10 managed-node1 kernel: device veth81789425 left promiscuous mode\nJul 07 20:32:10 managed-node1 kernel: cni-podman1: port 1(veth81789425) entered disabled state\nJul 07 20:32:10 managed-node1 systemd[1]: var-lib-containers-storage-overlay-a0264b07b668c5f99351ee5979367e21ea3e4db5eef7a31ae6e36f31a1ff3ac6-merged.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay-a0264b07b668c5f99351ee5979367e21ea3e4db5eef7a31ae6e36f31a1ff3ac6-merged.mount has successfully entered the 'dead' state.\nJul 07 20:32:10 managed-node1 systemd[1]: run-netns-netns\\x2da914b079\\x2d5dce\\x2d3fbb\\x2d0751\\x2d5a1358ca4a4d.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit run-netns-netns\\x2da914b079\\x2d5dce\\x2d3fbb\\x2d0751\\x2d5a1358ca4a4d.mount has successfully entered the 'dead' state.\nJul 07 20:32:10 managed-node1 systemd[1]: Removed slice cgroup machine-libpod_pod_0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae.slice.\n-- Subject: Unit machine-libpod_pod_0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae.slice has finished shutting down\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit machine-libpod_pod_0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae.slice has finished shutting down.\nJul 07 20:32:10 managed-node1 systemd[1]: machine-libpod_pod_0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae.slice: Consumed 8.805s CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit machine-libpod_pod_0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae.slice completed and consumed the indicated resources.\nJul 07 20:32:10 managed-node1 systemd[1]: libpod-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7.scope has successfully entered the 'dead' state.\nJul 07 20:32:10 managed-node1 systemd[1]: libpod-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7.scope: Consumed 34ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7.scope completed and consumed the indicated resources.\nJul 07 20:32:10 managed-node1 podman[35963]: Pods stopped:\nJul 07 20:32:10 managed-node1 podman[35963]: 0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae\nJul 07 20:32:10 managed-node1 podman[35963]: Pods removed:\nJul 07 20:32:10 managed-node1 podman[35963]: 0e0f8866c0fb4e91818c4a8f61a69ccbc3bec127e7a8fe75eba8be14c01c59ae\nJul 07 20:32:10 managed-node1 podman[35963]: Secrets removed:\nJul 07 20:32:10 managed-node1 podman[35963]: Volumes removed:\nJul 07 20:32:10 managed-node1 systemd[1]: podman-kube@-etc-containers-ansible\\x2dkubernetes.d-auth_test_1_kube.yml.service: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit podman-kube@-etc-containers-ansible\\x2dkubernetes.d-auth_test_1_kube.yml.service has successfully entered the 'dead' state.\nJul 07 20:32:10 managed-node1 systemd[1]: Stopped A template for running K8s workloads via podman-kube-play.\n-- Subject: Unit podman-kube@-etc-containers-ansible\\x2dkubernetes.d-auth_test_1_kube.yml.service has finished shutting down\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- Unit podman-kube@-etc-containers-ansible\\x2dkubernetes.d-auth_test_1_kube.yml.service has finished shutting down.\nJul 07 20:32:10 managed-node1 systemd[1]: var-lib-containers-storage-overlay-bef2e75cd4a1c6c29f14edd3c7277da84bdff203a6db927ab3ef03d04d42e329-merged.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay-bef2e75cd4a1c6c29f14edd3c7277da84bdff203a6db927ab3ef03d04d42e329-merged.mount has successfully entered the 'dead' state.\nJul 07 20:32:10 managed-node1 systemd[1]: var-lib-containers-storage-overlay\\x2dcontainers-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859-userdata-shm.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay\\x2dcontainers-d8cfad88c7f2ebb4cdbe20f4e7947480f9bc547dd80e9ebc8c27b68016788859-userdata-shm.mount has successfully entered the 'dead' state.\nJul 07 20:32:10 managed-node1 systemd[1]: var-lib-containers-storage-overlay-e7539ffa66e0669082b0b0eab1d85eebe740fd81b15c798adbcdf8f353278edd-merged.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay-e7539ffa66e0669082b0b0eab1d85eebe740fd81b15c798adbcdf8f353278edd-merged.mount has successfully entered the 'dead' state.\nJul 07 20:32:10 managed-node1 systemd[1]: var-lib-containers-storage-overlay\\x2dcontainers-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7-userdata-shm.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay\\x2dcontainers-9831112549f2921dd94d692f92c57d3075faa7db7cf3672e819fe9fd5956d7d7-userdata-shm.mount has successfully entered the 'dead' state.\nJul 07 20:32:10 managed-node1 platform-python[36237]: ansible-stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:11 managed-node1 platform-python[36362]: ansible-containers.podman.podman_play Invoked with state=absent kube_file=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml executable=podman annotation=None kube_file_content=None authfile=None build=None cert_dir=None configmap=None context_dir=None seccomp_profile_root=None username=None password=NOT_LOGGING_PARAMETER log_driver=None log_opt=None network=None tls_verify=None debug=None quiet=None recreate=None userns=None log_level=None quadlet_dir=None quadlet_filename=None quadlet_file_mode=None quadlet_options=None\nJul 07 20:32:11 managed-node1 platform-python[36362]: ansible-containers.podman.podman_play version: 4.9.4-dev, kube file /etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml\nJul 07 20:32:11 managed-node1 platform-python[36498]: ansible-file Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml state=absent recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:12 managed-node1 platform-python[36621]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:14 managed-node1 platform-python[36746]: ansible-systemd Invoked with name=auth_test_1_quadlet.service scope=system state=stopped enabled=False force=True daemon_reload=False daemon_reexec=False no_block=False masked=None\nJul 07 20:32:14 managed-node1 systemd[1]: Reloading.\nJul 07 20:32:14 managed-node1 platform-python[36901]: ansible-stat Invoked with path=/etc/containers/systemd/auth_test_1_quadlet.container follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:15 managed-node1 platform-python[37149]: ansible-ansible.legacy.command Invoked with _raw_params=journalctl -ex _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:17 managed-node1 platform-python[37398]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:18 managed-node1 platform-python[37527]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:20 managed-node1 platform-python[37652]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:22 managed-node1 platform-python[37777]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:24 managed-node1 platform-python[37902]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:25 managed-node1 platform-python[38027]: ansible-ansible.legacy.command Invoked with _raw_params=systemd-escape --template podman-kube@.service /etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:25 managed-node1 platform-python[38151]: ansible-systemd Invoked with name=podman-kube@-etc-containers-ansible\\x2dkubernetes.d-auth_test_1_kube.yml.service scope=system state=stopped enabled=False daemon_reload=False daemon_reexec=False no_block=False force=None masked=None\nJul 07 20:32:26 managed-node1 platform-python[38278]: ansible-stat Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:26 managed-node1 platform-python[38401]: ansible-file Invoked with path=/etc/containers/ansible-kubernetes.d/auth_test_1_kube.yml state=absent recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:27 managed-node1 platform-python[38524]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:29 managed-node1 platform-python[38649]: ansible-systemd Invoked with name=auth_test_1_quadlet.service scope=system state=stopped enabled=False force=True daemon_reload=False daemon_reexec=False no_block=False masked=None\nJul 07 20:32:29 managed-node1 systemd[1]: Reloading.\nJul 07 20:32:29 managed-node1 platform-python[38804]: ansible-stat Invoked with path=/etc/containers/systemd/auth_test_1_quadlet.container follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:30 managed-node1 platform-python[39052]: ansible-ansible.legacy.command Invoked with _raw_params=journalctl -ex _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:33 managed-node1 platform-python[39301]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:34 managed-node1 platform-python[39430]: ansible-getent Invoked with database=passwd key=auth_test_user1 fail_key=False service=None split=None\nJul 07 20:32:34 managed-node1 platform-python[39554]: ansible-ansible.legacy.command Invoked with _raw_params=journalctl -ex _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:35 managed-node1 platform-python[39678]: ansible-user Invoked with name=auth_test_user1 state=absent non_unique=False force=False remove=False create_home=True system=False move_home=False append=False ssh_key_bits=0 ssh_key_type=rsa ssh_key_comment=ansible-generated on managed-node1 update_password=always uid=None group=None groups=None comment=None home=None shell=None password=NOT_LOGGING_PARAMETER login_class=None password_expire_max=None password_expire_min=None password_expire_warn=None hidden=None seuser=None skeleton=None generate_ssh_key=None ssh_key_file=None ssh_key_passphrase=NOT_LOGGING_PARAMETER expires=None password_lock=None local=None profile=None authorization=None role=None umask=None\nJul 07 20:32:35 managed-node1 platform-python[39804]: ansible-file Invoked with path=/home/auth_test_user1 state=absent recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:36 managed-node1 platform-python[39927]: ansible-ansible.legacy.command Invoked with _raw_params=podman inspect podman_registry --format '{{range .}}{{range .Mounts}}{{if eq .Type \"volume\"}}{{.Name}}{{end}}{{end}}{{end}}' _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:36 managed-node1 platform-python[40058]: ansible-ansible.legacy.command Invoked with _raw_params=podman rm -f podman_registry _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:36 managed-node1 systemd[1]: libpod-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope has successfully entered the 'dead' state.\nJul 07 20:32:36 managed-node1 systemd[1]: libpod-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope: Consumed 290ms CPU time\n-- Subject: Resources consumed by unit runtime\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope completed and consumed the indicated resources.\nJul 07 20:32:36 managed-node1 kernel: cni-podman0: port 1(vethf474aada) entered disabled state\nJul 07 20:32:36 managed-node1 kernel: device vethf474aada left promiscuous mode\nJul 07 20:32:36 managed-node1 kernel: cni-podman0: port 1(vethf474aada) entered disabled state\nJul 07 20:32:36 managed-node1 systemd[1]: run-netns-netns\\x2d0f80910f\\x2d0f2a\\x2ddea6\\x2d8cd8\\x2dfd5fd57e9ef2.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit run-netns-netns\\x2d0f80910f\\x2d0f2a\\x2ddea6\\x2d8cd8\\x2dfd5fd57e9ef2.mount has successfully entered the 'dead' state.\nJul 07 20:32:36 managed-node1 systemd[1]: var-lib-containers-storage-overlay\\x2dcontainers-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7-userdata-shm.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay\\x2dcontainers-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7-userdata-shm.mount has successfully entered the 'dead' state.\nJul 07 20:32:36 managed-node1 systemd[1]: var-lib-containers-storage-overlay-7a1c676216f60cbaa5d9869b5875719d7ec38ff22a557a447c21b392281f894a-merged.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay-7a1c676216f60cbaa5d9869b5875719d7ec38ff22a557a447c21b392281f894a-merged.mount has successfully entered the 'dead' state.\nJul 07 20:32:36 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state.\nJul 07 20:32:37 managed-node1 systemd[1]: libpod-conmon-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit libpod-conmon-4e7c37a783f7ad708c69d05194e00bbaf6dd6c46a3e925cabbc17cbadbe533f7.scope has successfully entered the 'dead' state.\nJul 07 20:32:38 managed-node1 platform-python[40289]: ansible-ansible.legacy.command Invoked with _raw_params=podman volume rm b3c17191dae8c001c0511bbbe09617d4a57c3787f6e19f787f81800428f3f416 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:38 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state.\nJul 07 20:32:38 managed-node1 platform-python[40419]: ansible-file Invoked with path=/tmp/lsr_enzzya10_podman state=absent recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:40 managed-node1 platform-python[40581]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d\nJul 07 20:32:41 managed-node1 platform-python[40741]: ansible-stat Invoked with path=/run/ostree-booted follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:42 managed-node1 platform-python[40864]: ansible-stat Invoked with path=/sbin/transactional-update follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:44 managed-node1 platform-python[41112]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:45 managed-node1 platform-python[41241]: ansible-getent Invoked with database=passwd key=root fail_key=False service=None split=None\nJul 07 20:32:45 managed-node1 platform-python[41365]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:47 managed-node1 platform-python[41490]: ansible-tempfile Invoked with state=directory prefix=lsr_podman_config_ suffix= path=None\nJul 07 20:32:47 managed-node1 platform-python[41613]: ansible-ansible.legacy.command Invoked with _raw_params=tar --ignore-failed-read -c -P -v -p -f /tmp/lsr_podman_config_8qm8wgwl/backup.tar /etc/containers/containers.conf.d/50-systemroles.conf /etc/containers/registries.conf.d/50-systemroles.conf /etc/containers/storage.conf /etc/containers/policy.json _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:48 managed-node1 platform-python[41737]: ansible-user Invoked with name=user1 state=present non_unique=False force=False remove=False create_home=True system=False move_home=False append=False ssh_key_bits=0 ssh_key_type=rsa ssh_key_comment=ansible-generated on managed-node1 update_password=always uid=None group=None groups=None comment=None home=None shell=None password=NOT_LOGGING_PARAMETER login_class=None password_expire_max=None password_expire_min=None password_expire_warn=None hidden=None seuser=None skeleton=None generate_ssh_key=None ssh_key_file=None ssh_key_passphrase=NOT_LOGGING_PARAMETER expires=None password_lock=None local=None profile=None authorization=None role=None umask=None\nJul 07 20:32:48 managed-node1 useradd[41742]: new group: name=user1, GID=1000\nJul 07 20:32:48 managed-node1 useradd[41742]: new user: name=user1, UID=1000, GID=1000, home=/home/user1, shell=/bin/bash\nJul 07 20:32:50 managed-node1 platform-python[41995]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:51 managed-node1 platform-python[42124]: ansible-getent Invoked with database=passwd key=user1 fail_key=False service=None split=None\nJul 07 20:32:51 managed-node1 platform-python[42248]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:52 managed-node1 platform-python[42373]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:52 managed-node1 platform-python[42497]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:53 managed-node1 platform-python[42621]: ansible-file Invoked with path=/home/user1/.config/containers/containers.conf.d state=directory owner=user1 group=user1 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:53 managed-node1 platform-python[42744]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:32:54 managed-node1 platform-python[42843]: ansible-ansible.legacy.copy Invoked with dest=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf owner=user1 group=user1 mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934773.4083917-13555-16022273701041/source _original_basename=tmpo5idzwrq follow=False checksum=b1776092f2908d76e11fd6af87267469b2c17d5a backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:54 managed-node1 platform-python[42968]: ansible-file Invoked with path=/home/user1/.config/containers/registries.conf.d state=directory owner=user1 group=user1 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:54 managed-node1 platform-python[43091]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:32:55 managed-node1 platform-python[43190]: ansible-ansible.legacy.copy Invoked with dest=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf owner=user1 group=user1 mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934774.589606-13584-198443904655296/source _original_basename=tmpq9zidsm3 follow=False checksum=fde25488ce7040f1639af7bfc88ed125318cc0b0 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:55 managed-node1 platform-python[43315]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:56 managed-node1 platform-python[43438]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/storage.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:32:56 managed-node1 platform-python[43537]: ansible-ansible.legacy.copy Invoked with dest=/home/user1/.config/containers/storage.conf owner=user1 group=user1 mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934775.8582168-13631-148070678999800/source _original_basename=tmpltolsywp follow=False checksum=38f015f4780579bd388dd955b42916199fd7fe19 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:56 managed-node1 platform-python[43662]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:57 managed-node1 platform-python[43785]: ansible-stat Invoked with path=/home/user1/.config/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:57 managed-node1 platform-python[43908]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/policy.json follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:32:57 managed-node1 platform-python[44007]: ansible-ansible.legacy.copy Invoked with dest=/home/user1/.config/containers/policy.json owner=user1 group=user1 mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934777.330279-13702-122659933500562/source _original_basename=tmpkmgqgexc follow=False checksum=6746c079ad563b735fc39f73d4876654b80b0a0d backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:32:58 managed-node1 platform-python[44132]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:32:59 managed-node1 platform-python[44257]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:32:59 managed-node1 platform-python[44381]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:00 managed-node1 platform-python[44505]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:01 managed-node1 platform-python[44852]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:02 managed-node1 platform-python[44977]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:02 managed-node1 platform-python[45101]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:03 managed-node1 platform-python[45225]: ansible-stat Invoked with path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:03 managed-node1 platform-python[45350]: ansible-stat Invoked with path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:03 managed-node1 platform-python[45475]: ansible-stat Invoked with path=/home/user1/.config/containers/storage.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:04 managed-node1 platform-python[45600]: ansible-stat Invoked with path=/home/user1/.config/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:04 managed-node1 platform-python[45725]: ansible-ansible.legacy.command Invoked with _raw_params=grep 'container_name_as_hostname[ ]*=[ ]*true' /home/user1/.config/containers/containers.conf.d/50-systemroles.conf _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:07 managed-node1 platform-python[45974]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:08 managed-node1 platform-python[46103]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:08 managed-node1 platform-python[46228]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:08 managed-node1 platform-python[46352]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:09 managed-node1 platform-python[46476]: ansible-file Invoked with path=/home/user1/.config/containers/containers.conf.d state=directory owner=user1 group=user1 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:09 managed-node1 platform-python[46599]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:10 managed-node1 platform-python[46663]: ansible-ansible.legacy.file Invoked with owner=user1 group=user1 mode=0644 dest=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf _original_basename=tmpsld9zrjm recurse=False state=file path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:10 managed-node1 platform-python[46786]: ansible-file Invoked with path=/home/user1/.config/containers/registries.conf.d state=directory owner=user1 group=user1 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:11 managed-node1 platform-python[46909]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:11 managed-node1 platform-python[46973]: ansible-ansible.legacy.file Invoked with owner=user1 group=user1 mode=0644 dest=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf _original_basename=tmpk0q11pu7 recurse=False state=file path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:11 managed-node1 platform-python[47096]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:12 managed-node1 platform-python[47219]: ansible-ansible.legacy.stat Invoked with path=/home/user1/.config/containers/storage.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:12 managed-node1 platform-python[47283]: ansible-ansible.legacy.file Invoked with owner=user1 group=user1 mode=0644 dest=/home/user1/.config/containers/storage.conf _original_basename=tmpb7cut1r3 recurse=False state=file path=/home/user1/.config/containers/storage.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:12 managed-node1 platform-python[47406]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:13 managed-node1 platform-python[47529]: ansible-stat Invoked with path=/home/user1/.config/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:13 managed-node1 platform-python[47654]: ansible-slurp Invoked with path=/home/user1/.config/containers/policy.json src=/home/user1/.config/containers/policy.json\nJul 07 20:33:14 managed-node1 platform-python[47777]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:14 managed-node1 platform-python[47902]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:15 managed-node1 platform-python[48026]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:15 managed-node1 platform-python[48150]: ansible-file Invoked with path=/home/user1/.config/containers state=directory owner=user1 group=user1 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:17 managed-node1 platform-python[48460]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:18 managed-node1 platform-python[48585]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:18 managed-node1 platform-python[48709]: ansible-ansible.legacy.command Invoked with _raw_params=getsubids -g user1 _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:19 managed-node1 platform-python[48833]: ansible-stat Invoked with path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:19 managed-node1 platform-python[48958]: ansible-stat Invoked with path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:20 managed-node1 platform-python[49083]: ansible-stat Invoked with path=/home/user1/.config/containers/storage.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:20 managed-node1 platform-python[49208]: ansible-stat Invoked with path=/home/user1/.config/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:22 managed-node1 platform-python[49458]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:23 managed-node1 platform-python[49587]: ansible-getent Invoked with database=passwd key=root fail_key=False service=None split=None\nJul 07 20:33:24 managed-node1 platform-python[49711]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:24 managed-node1 platform-python[49836]: ansible-file Invoked with path=/etc/containers/containers.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:25 managed-node1 platform-python[49959]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:25 managed-node1 platform-python[50058]: ansible-ansible.legacy.copy Invoked with dest=/etc/containers/containers.conf.d/50-systemroles.conf owner=root mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934805.1493864-14753-170699386031760/source _original_basename=tmp5gsrdcbw follow=False checksum=b1776092f2908d76e11fd6af87267469b2c17d5a backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:26 managed-node1 platform-python[50183]: ansible-file Invoked with path=/etc/containers/registries.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:26 managed-node1 platform-python[50306]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:26 managed-node1 platform-python[50405]: ansible-ansible.legacy.copy Invoked with dest=/etc/containers/registries.conf.d/50-systemroles.conf owner=root mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934806.275409-14790-40277132360154/source _original_basename=tmpflqhaxry follow=False checksum=fde25488ce7040f1639af7bfc88ed125318cc0b0 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:27 managed-node1 platform-python[50530]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:27 managed-node1 platform-python[50653]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/storage.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:27 managed-node1 platform-python[50754]: ansible-ansible.legacy.copy Invoked with dest=/etc/containers/storage.conf owner=root mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934807.4339185-14833-193871550331891/source _original_basename=tmpsrbhn_xl follow=False checksum=38f015f4780579bd388dd955b42916199fd7fe19 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:28 managed-node1 platform-python[50879]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:28 managed-node1 platform-python[51002]: ansible-stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:29 managed-node1 platform-python[51127]: ansible-slurp Invoked with path=/etc/containers/policy.json src=/etc/containers/policy.json\nJul 07 20:33:29 managed-node1 platform-python[51250]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:29 managed-node1 platform-python[51351]: ansible-ansible.legacy.copy Invoked with dest=/etc/containers/policy.json owner=root mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934809.331465-14916-21787524891337/source _original_basename=tmpaykbdix_ follow=False checksum=6746c079ad563b735fc39f73d4876654b80b0a0d backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:30 managed-node1 platform-python[51476]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:31 managed-node1 platform-python[51601]: ansible-file Invoked with path=/root/.config/containers state=directory owner=root group=0 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:33 managed-node1 platform-python[51950]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:34 managed-node1 platform-python[52075]: ansible-stat Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:34 managed-node1 platform-python[52200]: ansible-stat Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:34 managed-node1 platform-python[52325]: ansible-stat Invoked with path=/etc/containers/storage.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:35 managed-node1 platform-python[52450]: ansible-stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:38 managed-node1 platform-python[52700]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:39 managed-node1 platform-python[52829]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:39 managed-node1 platform-python[52954]: ansible-file Invoked with path=/etc/containers/containers.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:40 managed-node1 platform-python[53077]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:40 managed-node1 platform-python[53141]: ansible-ansible.legacy.file Invoked with owner=root mode=0644 dest=/etc/containers/containers.conf.d/50-systemroles.conf _original_basename=tmpfcrntls4 recurse=False state=file path=/etc/containers/containers.conf.d/50-systemroles.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:40 managed-node1 platform-python[53264]: ansible-file Invoked with path=/etc/containers/registries.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:41 managed-node1 platform-python[53387]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:41 managed-node1 platform-python[53451]: ansible-ansible.legacy.file Invoked with owner=root mode=0644 dest=/etc/containers/registries.conf.d/50-systemroles.conf _original_basename=tmplmlkwsp6 recurse=False state=file path=/etc/containers/registries.conf.d/50-systemroles.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:42 managed-node1 platform-python[53574]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:42 managed-node1 platform-python[53697]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/storage.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:42 managed-node1 platform-python[53761]: ansible-ansible.legacy.file Invoked with owner=root mode=0644 dest=/etc/containers/storage.conf _original_basename=tmpgfldooqj recurse=False state=file path=/etc/containers/storage.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:43 managed-node1 platform-python[53884]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:43 managed-node1 platform-python[54007]: ansible-stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:44 managed-node1 platform-python[54132]: ansible-slurp Invoked with path=/etc/containers/policy.json src=/etc/containers/policy.json\nJul 07 20:33:45 managed-node1 platform-python[54255]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:45 managed-node1 platform-python[54380]: ansible-file Invoked with path=/root/.config/containers state=directory owner=root group=0 mode=0700 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:47 managed-node1 platform-python[54690]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:48 managed-node1 platform-python[54815]: ansible-stat Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:48 managed-node1 platform-python[54940]: ansible-stat Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:49 managed-node1 platform-python[55065]: ansible-stat Invoked with path=/etc/containers/storage.conf follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:49 managed-node1 platform-python[55190]: ansible-stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:50 managed-node1 platform-python[55315]: ansible-slurp Invoked with path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf src=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf\nJul 07 20:33:50 managed-node1 platform-python[55438]: ansible-slurp Invoked with path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf src=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf\nJul 07 20:33:51 managed-node1 platform-python[55561]: ansible-slurp Invoked with path=/home/user1/.config/containers/storage.conf src=/home/user1/.config/containers/storage.conf\nJul 07 20:33:51 managed-node1 platform-python[55684]: ansible-slurp Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf src=/etc/containers/containers.conf.d/50-systemroles.conf\nJul 07 20:33:51 managed-node1 platform-python[55807]: ansible-slurp Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf src=/etc/containers/registries.conf.d/50-systemroles.conf\nJul 07 20:33:52 managed-node1 platform-python[55930]: ansible-slurp Invoked with path=/etc/containers/storage.conf src=/etc/containers/storage.conf\nJul 07 20:33:55 managed-node1 platform-python[56178]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:33:56 managed-node1 platform-python[56307]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:33:56 managed-node1 platform-python[56432]: ansible-file Invoked with path=/etc/containers/containers.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:57 managed-node1 platform-python[56555]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:57 managed-node1 platform-python[56656]: ansible-ansible.legacy.copy Invoked with dest=/etc/containers/containers.conf.d/50-systemroles.conf owner=root mode=0644 src=/root/.ansible/tmp/ansible-tmp-1751934837.1165416-15806-11049734104554/source _original_basename=tmpkiwyq02_ follow=False checksum=9694c1d1c700a6435eecf4066b052584f4ee94c0 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:58 managed-node1 platform-python[56781]: ansible-file Invoked with path=/etc/containers/registries.conf.d state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:58 managed-node1 platform-python[56904]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/registries.conf.d/50-systemroles.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:58 managed-node1 platform-python[56968]: ansible-ansible.legacy.file Invoked with owner=root mode=0644 dest=/etc/containers/registries.conf.d/50-systemroles.conf _original_basename=tmpxg73mi7m recurse=False state=file path=/etc/containers/registries.conf.d/50-systemroles.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:59 managed-node1 platform-python[57091]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:33:59 managed-node1 platform-python[57214]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/storage.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:33:59 managed-node1 platform-python[57278]: ansible-ansible.legacy.file Invoked with owner=root mode=0644 dest=/etc/containers/storage.conf _original_basename=tmp8ws7ml82 recurse=False state=file path=/etc/containers/storage.conf force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:00 managed-node1 platform-python[57401]: ansible-file Invoked with path=/etc/containers state=directory owner=root mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:00 managed-node1 platform-python[57524]: ansible-stat Invoked with path=/etc/containers/policy.json follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:01 managed-node1 platform-python[57649]: ansible-slurp Invoked with path=/etc/containers/policy.json src=/etc/containers/policy.json\nJul 07 20:34:02 managed-node1 platform-python[57772]: ansible-slurp Invoked with path=/etc/containers/containers.conf.d/50-systemroles.conf src=/etc/containers/containers.conf.d/50-systemroles.conf\nJul 07 20:34:02 managed-node1 platform-python[57895]: ansible-file Invoked with state=absent path=/etc/containers/containers.conf.d/50-systemroles.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:02 managed-node1 platform-python[58018]: ansible-file Invoked with state=absent path=/etc/containers/registries.conf.d/50-systemroles.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:03 managed-node1 platform-python[58141]: ansible-file Invoked with state=absent path=/etc/containers/storage.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:03 managed-node1 platform-python[58264]: ansible-file Invoked with state=absent path=/etc/containers/policy.json recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:03 managed-node1 platform-python[58387]: ansible-file Invoked with state=absent path=/home/user1/.config/containers/containers.conf.d/50-systemroles.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:04 managed-node1 platform-python[58510]: ansible-file Invoked with state=absent path=/home/user1/.config/containers/registries.conf.d/50-systemroles.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:04 managed-node1 platform-python[58633]: ansible-file Invoked with state=absent path=/home/user1/.config/containers/storage.conf recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:04 managed-node1 platform-python[58756]: ansible-file Invoked with state=absent path=/home/user1/.config/containers/policy.json recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:05 managed-node1 platform-python[58879]: ansible-file Invoked with state=absent path=/root/.config/containers/auth.json recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:05 managed-node1 platform-python[59002]: ansible-file Invoked with state=absent path=/home/user1/.config/containers/auth.json recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:05 managed-node1 platform-python[59125]: ansible-ansible.legacy.command Invoked with _raw_params=tar xfvpP /tmp/lsr_podman_config_8qm8wgwl/backup.tar _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:34:06 managed-node1 platform-python[59249]: ansible-file Invoked with state=absent path=/tmp/lsr_podman_config_8qm8wgwl recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:08 managed-node1 platform-python[59411]: ansible-setup Invoked with gather_subset=['!all', '!min', 'distribution', 'distribution_major_version', 'distribution_version', 'os_family'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d\nJul 07 20:34:08 managed-node1 platform-python[59538]: ansible-stat Invoked with path=/run/ostree-booted follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:09 managed-node1 platform-python[59661]: ansible-stat Invoked with path=/sbin/transactional-update follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:12 managed-node1 platform-python[59909]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:34:12 managed-node1 platform-python[60038]: ansible-getent Invoked with database=passwd key=root fail_key=False service=None split=None\nJul 07 20:34:13 managed-node1 platform-python[60162]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:16 managed-node1 platform-python[60326]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d\nJul 07 20:34:19 managed-node1 platform-python[60486]: ansible-stat Invoked with path=/run/ostree-booted follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:20 managed-node1 platform-python[60609]: ansible-stat Invoked with path=/sbin/transactional-update follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:22 managed-node1 platform-python[60857]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:34:23 managed-node1 platform-python[60986]: ansible-getent Invoked with database=passwd key=root fail_key=False service=None split=None\nJul 07 20:34:24 managed-node1 platform-python[61110]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:27 managed-node1 platform-python[61274]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d\nJul 07 20:34:28 managed-node1 platform-python[61434]: ansible-stat Invoked with path=/run/ostree-booted follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:29 managed-node1 platform-python[61557]: ansible-stat Invoked with path=/sbin/transactional-update follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:31 managed-node1 platform-python[61805]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:34:32 managed-node1 platform-python[61934]: ansible-getent Invoked with database=passwd key=root fail_key=False service=None split=None\nJul 07 20:34:33 managed-node1 platform-python[62058]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:35 managed-node1 platform-python[62183]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:37 managed-node1 platform-python[62308]: ansible-file Invoked with path=/etc/containers/systemd state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:37 managed-node1 platform-python[62431]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/systemd/nopull.container follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:34:38 managed-node1 platform-python[62530]: ansible-ansible.legacy.copy Invoked with src=/root/.ansible/tmp/ansible-tmp-1751934877.5450642-17711-142143421897050/source dest=/etc/containers/systemd/nopull.container owner=root group=0 mode=0644 follow=False _original_basename=systemd.j2 checksum=670d64fc68a9768edb20cad26df2acc703542d85 backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:41 managed-node1 platform-python[62780]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:34:41 managed-node1 platform-python[62909]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:44 managed-node1 platform-python[63034]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:45 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state.\nJul 07 20:34:46 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state.\nJul 07 20:34:46 managed-node1 platform-python[63296]: ansible-file Invoked with path=/etc/containers/systemd state=directory owner=root group=0 mode=0755 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:47 managed-node1 platform-python[63419]: ansible-ansible.legacy.stat Invoked with path=/etc/containers/systemd/bogus.container follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True\nJul 07 20:34:47 managed-node1 platform-python[63518]: ansible-ansible.legacy.copy Invoked with src=/root/.ansible/tmp/ansible-tmp-1751934886.8113573-18040-140717157966343/source dest=/etc/containers/systemd/bogus.container owner=root group=0 mode=0644 follow=False _original_basename=systemd.j2 checksum=1d087e679d135214e8ac9ccaf33b2222916efb7f backup=False force=True unsafe_writes=False content=NOT_LOGGING_PARAMETER validate=None directory_mode=None remote_src=None local_follow=None seuser=None serole=None selevel=None setype=None attributes=None\nJul 07 20:34:50 managed-node1 platform-python[63768]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:34:51 managed-node1 platform-python[63897]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:53 managed-node1 platform-python[64022]: ansible-stat Invoked with path=/usr/bin/getsubids follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:55 managed-node1 platform-python[64147]: ansible-systemd Invoked with name=nopull.service scope=system state=stopped enabled=False force=True daemon_reload=False daemon_reexec=False no_block=False masked=None\nJul 07 20:34:55 managed-node1 platform-python[64273]: ansible-stat Invoked with path=/etc/containers/systemd/nopull.container follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nJul 07 20:34:56 managed-node1 platform-python[64521]: ansible-ansible.legacy.command Invoked with _raw_params=set -x\n set -o pipefail\n exec 1>&2\n #podman volume rm --all\n #podman network prune -f\n podman volume ls\n podman network ls\n podman secret ls\n podman container ls\n podman pod ls\n podman images\n systemctl list-units | grep quadlet\n _uses_shell=True expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:34:56 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state.\nJul 07 20:34:57 managed-node1 systemd[1]: var-lib-containers-storage-overlay.mount: Succeeded.\n-- Subject: Unit succeeded\n-- Defined-By: systemd\n-- Support: https://access.redhat.com/support\n-- \n-- The unit var-lib-containers-storage-overlay.mount has successfully entered the 'dead' state.\nJul 07 20:34:59 managed-node1 platform-python[64841]: ansible-ansible.legacy.command Invoked with _raw_params=podman --version _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None\nJul 07 20:35:00 managed-node1 platform-python[64970]: ansible-getent Invoked with database=passwd key=user_quadlet_basic fail_key=False service=None split=None\nJul 07 20:35:00 managed-node1 platform-python[65094]: ansible-ansible.legacy.command Invoked with _raw_params=journalctl -ex _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None", "task_name": "Dump journal", "task_path": "/tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:336" } ] SYSTEM ROLES ERRORS END v1 TASKS RECAP ******************************************************************** Monday 07 July 2025 20:35:00 -0400 (0:00:00.409) 0:00:33.793 *********** =============================================================================== fedora.linux_system_roles.podman : Gather the package facts ------------- 1.69s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 fedora.linux_system_roles.podman : Gather the package facts ------------- 1.54s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 fedora.linux_system_roles.podman : Gather the package facts ------------- 1.49s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 fedora.linux_system_roles.podman : Gather the package facts ------------- 1.44s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 Gathering Facts --------------------------------------------------------- 1.07s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:9 fedora.linux_system_roles.podman : Ensure container images are present --- 0.99s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:18 fedora.linux_system_roles.podman : Ensure quadlet file is present ------- 0.80s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:75 fedora.linux_system_roles.podman : Stop and disable service ------------- 0.75s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/cleanup_quadlet_spec.yml:12 fedora.linux_system_roles.podman : Ensure quadlet file is present ------- 0.72s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:75 Debug3 ------------------------------------------------------------------ 0.55s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:270 fedora.linux_system_roles.podman : Get user information ----------------- 0.53s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:2 fedora.linux_system_roles.podman : Ensure the quadlet directory is present --- 0.53s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:39 fedora.linux_system_roles.podman : Slurp quadlet file ------------------- 0.49s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/parse_quadlet_file.yml:6 fedora.linux_system_roles.podman : Get podman version ------------------- 0.48s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:46 fedora.linux_system_roles.podman : Check if system is ostree ------------ 0.44s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:11 Dump journal ------------------------------------------------------------ 0.41s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/tests/podman/tests_quadlet_basic.yml:336 fedora.linux_system_roles.podman : Ensure the quadlet directory is present --- 0.40s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/create_update_quadlet_spec.yml:39 fedora.linux_system_roles.podman : Get podman version ------------------- 0.40s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:46 fedora.linux_system_roles.podman : Get podman version ------------------- 0.39s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:46 fedora.linux_system_roles.podman : See if getsubids exists -------------- 0.39s /tmp/collections-Tk5/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/handle_user_group.yml:31