ansible-playbook [core 2.17.12] 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-PO3 executable location = /usr/local/bin/ansible-playbook python version = 3.12.10 (main, May 9 2025, 00:00:00) [GCC 11.5.0 20240719 (Red Hat 11.5.0-5)] (/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_basic.yml ****************************************************** 2 plays in /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml PLAY [all] ********************************************************************* TASK [Include vault variables] ************************************************* task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:5 Saturday 24 May 2025 12:31:11 -0400 (0:00:00.029) 0:00:00.029 ********** ok: [managed-node2] => { "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-Ogi/tests/vars/vault-variables.yml" ], "changed": false } PLAY [Ensure that the role runs with default parameters] *********************** TASK [Gathering Facts] ********************************************************* task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:9 Saturday 24 May 2025 12:31:11 -0400 (0:00:00.020) 0:00:00.050 ********** [WARNING]: Platform linux on host managed-node2 is using the discovered Python interpreter at /usr/bin/python3.9, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible- core/2.17/reference_appendices/interpreter_discovery.html for more information. ok: [managed-node2] TASK [Create tmpdir for testing] *********************************************** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:143 Saturday 24 May 2025 12:31:13 -0400 (0:00:02.353) 0:00:02.403 ********** changed: [managed-node2] => { "changed": true, "gid": 0, "group": "root", "mode": "0700", "owner": "root", "path": "/tmp/lsr_jq0x6_jl_podman", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 6, "state": "directory", "uid": 0 } TASK [Change tmpdir permissions] *********************************************** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:150 Saturday 24 May 2025 12:31:14 -0400 (0:00:00.471) 0:00:02.875 ********** changed: [managed-node2] => { "changed": true, "gid": 0, "group": "root", "mode": "0777", "owner": "root", "path": "/tmp/lsr_jq0x6_jl_podman", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 6, "state": "directory", "uid": 0 } TASK [Enable podman copr] ****************************************************** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:161 Saturday 24 May 2025 12:31:14 -0400 (0:00:00.433) 0:00:03.309 ********** skipping: [managed-node2] => { "changed": false, "false_condition": "podman_use_copr | d(false)", "skip_reason": "Conditional result was False" } TASK [Install podman from updates-testing] ************************************* task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:166 Saturday 24 May 2025 12:31:14 -0400 (0:00:00.033) 0:00:03.342 ********** skipping: [managed-node2] => { "changed": false, "false_condition": "podman_use_copr | d(false)", "skip_reason": "Conditional result was False" } TASK [Podman version] ********************************************************** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:171 Saturday 24 May 2025 12:31:14 -0400 (0:00:00.030) 0:00:03.373 ********** skipping: [managed-node2] => { "changed": false, "false_condition": "podman_use_copr | d(false)", "skip_reason": "Conditional result was False" } TASK [Create user] ************************************************************* task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:176 Saturday 24 May 2025 12:31:14 -0400 (0:00:00.032) 0:00:03.405 ********** changed: [managed-node2] => { "changed": true, "comment": "", "create_home": true, "group": 3001, "home": "/home/podman_basic_user", "name": "podman_basic_user", "shell": "/bin/bash", "state": "present", "system": false, "uid": 3001 } TASK [Create tempfile for kube_src] ******************************************** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:181 Saturday 24 May 2025 12:31:15 -0400 (0:00:00.576) 0:00:03.981 ********** changed: [managed-node2 -> localhost] => { "changed": true, "gid": 0, "group": "root", "mode": "0600", "owner": "root", "path": "/tmp/lsr_podman_86knjsnc.yml", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 0, "state": "file", "uid": 0 } TASK [Write kube_file_src] ***************************************************** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:189 Saturday 24 May 2025 12:31:15 -0400 (0:00:00.203) 0:00:04.185 ********** changed: [managed-node2 -> localhost] => { "changed": true, "checksum": "804089bb938d0e7671beefaa4815c4bf127fcf9c", "dest": "/tmp/lsr_podman_86knjsnc.yml", "gid": 0, "group": "root", "md5sum": "455842dafb69fda3fb3c1ed6c02134cc", "mode": "0600", "owner": "root", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 710, "src": "/root/.ansible/tmp/ansible-tmp-1748104275.568299-7594-15226657336164/.source.yml", "state": "file", "uid": 0 } TASK [Create host directories for data] **************************************** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:196 Saturday 24 May 2025 12:31:16 -0400 (0:00:00.577) 0:00:04.762 ********** changed: [managed-node2] => (item=['httpd1', 'podman_basic_user', 3001]) => { "ansible_loop_var": "item", "changed": true, "gid": 0, "group": "root", "item": [ "httpd1", "podman_basic_user", 3001 ], "mode": "0755", "owner": "podman_basic_user", "path": "/tmp/lsr_jq0x6_jl_podman/httpd1", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 6, "state": "directory", "uid": 3001 } changed: [managed-node2] => (item=['httpd2', 'root', 0]) => { "ansible_loop_var": "item", "changed": true, "gid": 0, "group": "root", "item": [ "httpd2", "root", 0 ], "mode": "0755", "owner": "root", "path": "/tmp/lsr_jq0x6_jl_podman/httpd2", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 6, "state": "directory", "uid": 0 } changed: [managed-node2] => (item=['httpd3', 'root', 0]) => { "ansible_loop_var": "item", "changed": true, "gid": 0, "group": "root", "item": [ "httpd3", "root", 0 ], "mode": "0755", "owner": "root", "path": "/tmp/lsr_jq0x6_jl_podman/httpd3", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 6, "state": "directory", "uid": 0 } TASK [Create data files] ******************************************************* task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:204 Saturday 24 May 2025 12:31:17 -0400 (0:00:01.005) 0:00:05.768 ********** changed: [managed-node2] => (item=['httpd1', 'podman_basic_user', 3001]) => { "ansible_loop_var": "item", "changed": true, "checksum": "40bd001563085fc35165329ea1ff5c5ecbdbbeef", "dest": "/tmp/lsr_jq0x6_jl_podman/httpd1/index.txt", "gid": 0, "group": "root", "item": [ "httpd1", "podman_basic_user", 3001 ], "md5sum": "202cb962ac59075b964b07152d234b70", "mode": "0644", "owner": "podman_basic_user", "secontext": "unconfined_u:object_r:admin_home_t:s0", "size": 3, "src": "/root/.ansible/tmp/ansible-tmp-1748104277.176319-7649-125572707805660/.source.txt", "state": "file", "uid": 3001 } changed: [managed-node2] => (item=['httpd2', 'root', 0]) => { "ansible_loop_var": "item", "changed": true, "checksum": "40bd001563085fc35165329ea1ff5c5ecbdbbeef", "dest": "/tmp/lsr_jq0x6_jl_podman/httpd2/index.txt", "gid": 0, "group": "root", "item": [ "httpd2", "root", 0 ], "md5sum": "202cb962ac59075b964b07152d234b70", "mode": "0644", "owner": "root", "secontext": "unconfined_u:object_r:admin_home_t:s0", "size": 3, "src": "/root/.ansible/tmp/ansible-tmp-1748104277.8073432-7649-214398782870186/.source.txt", "state": "file", "uid": 0 } changed: [managed-node2] => (item=['httpd3', 'root', 0]) => { "ansible_loop_var": "item", "changed": true, "checksum": "40bd001563085fc35165329ea1ff5c5ecbdbbeef", "dest": "/tmp/lsr_jq0x6_jl_podman/httpd3/index.txt", "gid": 0, "group": "root", "item": [ "httpd3", "root", 0 ], "md5sum": "202cb962ac59075b964b07152d234b70", "mode": "0644", "owner": "root", "secontext": "unconfined_u:object_r:admin_home_t:s0", "size": 3, "src": "/root/.ansible/tmp/ansible-tmp-1748104278.4192455-7649-81299099379633/.source.txt", "state": "file", "uid": 0 } TASK [Run role - do not pull images] ******************************************* task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:214 Saturday 24 May 2025 12:31:19 -0400 (0:00:01.874) 0:00:07.642 ********** included: fedora.linux_system_roles.podman for managed-node2 TASK [fedora.linux_system_roles.podman : Set platform/version specific variables] *** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:3 Saturday 24 May 2025 12:31:19 -0400 (0:00:00.057) 0:00:07.700 ********** included: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml for managed-node2 TASK [fedora.linux_system_roles.podman : Ensure ansible_facts used by role] **** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:3 Saturday 24 May 2025 12:31:19 -0400 (0:00:00.022) 0:00:07.723 ********** skipping: [managed-node2] => { "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-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:11 Saturday 24 May 2025 12:31:19 -0400 (0:00:00.033) 0:00:07.756 ********** ok: [managed-node2] => { "changed": false, "stat": { "exists": false } } TASK [fedora.linux_system_roles.podman : Set flag to indicate system is ostree] *** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:16 Saturday 24 May 2025 12:31:19 -0400 (0:00:00.337) 0:00:08.093 ********** ok: [managed-node2] => { "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-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:23 Saturday 24 May 2025 12:31:19 -0400 (0:00:00.022) 0:00:08.116 ********** ok: [managed-node2] => { "changed": false, "stat": { "exists": false } } TASK [fedora.linux_system_roles.podman : Set flag if transactional-update exists] *** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:28 Saturday 24 May 2025 12:31:19 -0400 (0:00:00.347) 0:00:08.463 ********** ok: [managed-node2] => { "ansible_facts": { "__podman_is_transactional": false }, "changed": false } TASK [fedora.linux_system_roles.podman : Set platform/version specific variables] *** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:32 Saturday 24 May 2025 12:31:19 -0400 (0:00:00.022) 0:00:08.485 ********** ok: [managed-node2] => (item=RedHat.yml) => { "ansible_facts": { "__podman_packages": [ "podman", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/vars/RedHat.yml" ], "ansible_loop_var": "item", "changed": false, "item": "RedHat.yml" } skipping: [managed-node2] => (item=CentOS.yml) => { "ansible_loop_var": "item", "changed": false, "false_condition": "__vars_file is file", "item": "CentOS.yml", "skip_reason": "Conditional result was False" } skipping: [managed-node2] => (item=CentOS_9.yml) => { "ansible_loop_var": "item", "changed": false, "false_condition": "__vars_file is file", "item": "CentOS_9.yml", "skip_reason": "Conditional result was False" } skipping: [managed-node2] => (item=CentOS_9.yml) => { "ansible_loop_var": "item", "changed": false, "false_condition": "__vars_file is file", "item": "CentOS_9.yml", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Gather the package facts] ************* task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 Saturday 24 May 2025 12:31:19 -0400 (0:00:00.035) 0:00:08.520 ********** ok: [managed-node2] => { "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-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:10 Saturday 24 May 2025 12:31:20 -0400 (0:00:01.089) 0:00:09.609 ********** skipping: [managed-node2] => { "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-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:14 Saturday 24 May 2025 12:31:21 -0400 (0:00:00.053) 0:00:09.663 ********** fatal: [managed-node2]: FAILED! => { "changed": false, "rc": 1, "results": [] } MSG: Failed to download metadata for repo 'highavailability': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried TASK [Verify image not pulled] ************************************************* task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:262 Saturday 24 May 2025 12:31:25 -0400 (0:00:04.820) 0:00:14.483 ********** fatal: [managed-node2]: FAILED! => {} MSG: The conditional check 'not __podman_image_updated.results[0] is changed' failed. The error was: The 'changed' test expects a dictionary TASK [Cleanup] ***************************************************************** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:269 Saturday 24 May 2025 12:31:25 -0400 (0:00:00.035) 0:00:14.518 ********** included: fedora.linux_system_roles.podman for managed-node2 => (item=nopull) included: fedora.linux_system_roles.podman for managed-node2 => (item=bogus) TASK [fedora.linux_system_roles.podman : Set platform/version specific variables] *** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:3 Saturday 24 May 2025 12:31:26 -0400 (0:00:00.134) 0:00:14.653 ********** included: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml for managed-node2 TASK [fedora.linux_system_roles.podman : Ensure ansible_facts used by role] **** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:3 Saturday 24 May 2025 12:31:26 -0400 (0:00:00.046) 0:00:14.700 ********** skipping: [managed-node2] => { "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-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:11 Saturday 24 May 2025 12:31:26 -0400 (0:00:00.049) 0:00:14.749 ********** skipping: [managed-node2] => { "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-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:16 Saturday 24 May 2025 12:31:26 -0400 (0:00:00.041) 0:00:14.790 ********** skipping: [managed-node2] => { "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-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:23 Saturday 24 May 2025 12:31:26 -0400 (0:00:00.030) 0:00:14.821 ********** skipping: [managed-node2] => { "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-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:28 Saturday 24 May 2025 12:31:26 -0400 (0:00:00.052) 0:00:14.874 ********** skipping: [managed-node2] => { "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-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:32 Saturday 24 May 2025 12:31:26 -0400 (0:00:00.032) 0:00:14.907 ********** [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-node2] => (item=RedHat.yml) => { "ansible_facts": { "__podman_packages": [ "podman", "shadow-utils-subid" ] }, "ansible_included_var_files": [ "/tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/vars/RedHat.yml" ], "ansible_loop_var": "item", "changed": false, "item": "RedHat.yml" } skipping: [managed-node2] => (item=CentOS.yml) => { "ansible_loop_var": "item", "changed": false, "false_condition": "__vars_file is file", "item": "CentOS.yml", "skip_reason": "Conditional result was False" } skipping: [managed-node2] => (item=CentOS_9.yml) => { "ansible_loop_var": "item", "changed": false, "false_condition": "__vars_file is file", "item": "CentOS_9.yml", "skip_reason": "Conditional result was False" } skipping: [managed-node2] => (item=CentOS_9.yml) => { "ansible_loop_var": "item", "changed": false, "false_condition": "__vars_file is file", "item": "CentOS_9.yml", "skip_reason": "Conditional result was False" } TASK [fedora.linux_system_roles.podman : Gather the package facts] ************* task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 Saturday 24 May 2025 12:31:26 -0400 (0:00:00.063) 0:00:14.970 ********** ok: [managed-node2] => { "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-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:10 Saturday 24 May 2025 12:31:27 -0400 (0:00:00.774) 0:00:15.745 ********** skipping: [managed-node2] => { "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-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:14 Saturday 24 May 2025 12:31:27 -0400 (0:00:00.045) 0:00:15.790 ********** fatal: [managed-node2]: FAILED! => { "changed": false, "rc": 1, "results": [] } MSG: Failed to download metadata for repo 'highavailability': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried TASK [Dump journal] ************************************************************ task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:447 Saturday 24 May 2025 12:31:31 -0400 (0:00:03.973) 0:00:19.764 ********** fatal: [managed-node2]: FAILED! => { "changed": false, "cmd": [ "journalctl", "-ex" ], "delta": "0:00:00.036026", "end": "2025-05-24 12:31:31.567478", "failed_when_result": true, "rc": 0, "start": "2025-05-24 12:31:31.531452" } STDOUT: May 24 12:27:49 localhost kernel: Cannot get hvm parameter CONSOLE_EVTCHN (18): -22! May 24 12:27:49 localhost kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled May 24 12:27:49 localhost kernel: 00:06: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A May 24 12:27:49 localhost kernel: Non-volatile memory driver v1.3 May 24 12:27:49 localhost kernel: rdac: device handler registered May 24 12:27:49 localhost kernel: hp_sw: device handler registered May 24 12:27:49 localhost kernel: emc: device handler registered May 24 12:27:49 localhost kernel: alua: device handler registered May 24 12:27:49 localhost kernel: usbcore: registered new interface driver usbserial_generic May 24 12:27:49 localhost kernel: usbserial: USB Serial support registered for generic May 24 12:27:49 localhost kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 May 24 12:27:49 localhost kernel: i8042: Warning: Keylock active May 24 12:27:49 localhost kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 May 24 12:27:49 localhost kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 May 24 12:27:49 localhost kernel: mousedev: PS/2 mouse device common for all mice May 24 12:27:49 localhost kernel: rtc_cmos 00:02: registered as rtc0 May 24 12:27:49 localhost kernel: rtc_cmos 00:02: setting system clock to 2025-05-24T16:27:48 UTC (1748104068) May 24 12:27:49 localhost kernel: rtc_cmos 00:02: alarms up to one day, 114 bytes nvram, hpet irqs May 24 12:27:49 localhost kernel: intel_pstate: CPU model not supported May 24 12:27:49 localhost kernel: hid: raw HID events driver (C) Jiri Kosina May 24 12:27:49 localhost kernel: usbcore: registered new interface driver usbhid May 24 12:27:49 localhost kernel: usbhid: USB HID core driver May 24 12:27:49 localhost kernel: drop_monitor: Initializing network drop monitor service May 24 12:27:49 localhost kernel: Initializing XFRM netlink socket May 24 12:27:49 localhost kernel: NET: Registered PF_INET6 protocol family May 24 12:27:49 localhost kernel: Freeing initrd memory: 37068K May 24 12:27:49 localhost kernel: Segment Routing with IPv6 May 24 12:27:49 localhost kernel: NET: Registered PF_PACKET protocol family May 24 12:27:49 localhost kernel: mpls_gso: MPLS GSO support May 24 12:27:49 localhost kernel: IPI shorthand broadcast: enabled May 24 12:27:49 localhost kernel: AVX2 version of gcm_enc/dec engaged. May 24 12:27:49 localhost kernel: AES CTR mode by8 optimization enabled May 24 12:27:49 localhost kernel: sched_clock: Marking stable (858125011, 248380944)->(1201973053, -95467098) May 24 12:27:49 localhost kernel: registered taskstats version 1 May 24 12:27:49 localhost kernel: Loading compiled-in X.509 certificates May 24 12:27:49 localhost kernel: Loaded X.509 cert 'The CentOS Project: CentOS Stream kernel signing key: f8c7f7d0e4c329fac8112926b4bb7228168649ea' May 24 12:27:49 localhost kernel: Loaded X.509 cert 'Red Hat Enterprise Linux Driver Update Program (key 3): bf57f3e87362bc7229d9f465321773dfd1f77a80' May 24 12:27:49 localhost kernel: Loaded X.509 cert 'Red Hat Enterprise Linux kpatch signing key: 4d38fd864ebe18c5f0b72e3852e2014c3a676fc8' May 24 12:27:49 localhost kernel: Loaded X.509 cert 'RH-IMA-CA: Red Hat IMA CA: fb31825dd0e073685b264e3038963673f753959a' May 24 12:27:49 localhost kernel: Loaded X.509 cert 'Nvidia GPU OOT signing 001: 55e1cef88193e60419f0b0ec379c49f77545acf0' May 24 12:27:49 localhost kernel: Demotion targets for Node 0: null May 24 12:27:49 localhost kernel: page_owner is disabled May 24 12:27:49 localhost kernel: Key type .fscrypt registered May 24 12:27:49 localhost kernel: Key type fscrypt-provisioning registered May 24 12:27:49 localhost kernel: Key type big_key registered May 24 12:27:49 localhost kernel: Key type encrypted registered May 24 12:27:49 localhost kernel: ima: No TPM chip found, activating TPM-bypass! May 24 12:27:49 localhost kernel: Loading compiled-in module X.509 certificates May 24 12:27:49 localhost kernel: Loaded X.509 cert 'The CentOS Project: CentOS Stream kernel signing key: f8c7f7d0e4c329fac8112926b4bb7228168649ea' May 24 12:27:49 localhost kernel: ima: Allocated hash algorithm: sha256 May 24 12:27:49 localhost kernel: ima: No architecture policies found May 24 12:27:49 localhost kernel: evm: Initialising EVM extended attributes: May 24 12:27:49 localhost kernel: evm: security.selinux May 24 12:27:49 localhost kernel: evm: security.SMACK64 (disabled) May 24 12:27:49 localhost kernel: evm: security.SMACK64EXEC (disabled) May 24 12:27:49 localhost kernel: evm: security.SMACK64TRANSMUTE (disabled) May 24 12:27:49 localhost kernel: evm: security.SMACK64MMAP (disabled) May 24 12:27:49 localhost kernel: evm: security.apparmor (disabled) May 24 12:27:49 localhost kernel: evm: security.ima May 24 12:27:49 localhost kernel: evm: security.capability May 24 12:27:49 localhost kernel: evm: HMAC attrs: 0x1 May 24 12:27:49 localhost kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2 May 24 12:27:49 localhost kernel: Running certificate verification RSA selftest May 24 12:27:49 localhost kernel: Loaded X.509 cert 'Certificate verification self-testing key: f58703bb33ce1b73ee02eccdee5b8817518fe3db' May 24 12:27:49 localhost kernel: Running certificate verification ECDSA selftest May 24 12:27:49 localhost kernel: Loaded X.509 cert 'Certificate verification ECDSA self-testing key: 2900bcea1deb7bc8479a84a23d758efdfdd2b2d3' May 24 12:27:49 localhost kernel: xenbus_probe_frontend: Device with no driver: device/vbd/768 May 24 12:27:49 localhost kernel: xenbus_probe_frontend: Device with no driver: device/vif/0 May 24 12:27:49 localhost kernel: clk: Disabling unused clocks May 24 12:27:49 localhost kernel: Freeing unused decrypted memory: 2028K May 24 12:27:49 localhost kernel: Freeing unused kernel image (initmem) memory: 4056K May 24 12:27:49 localhost kernel: Write protecting the kernel read-only data: 30720k May 24 12:27:49 localhost kernel: Freeing unused kernel image (rodata/data gap) memory: 684K May 24 12:27:49 localhost kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found. May 24 12:27:49 localhost kernel: x86/mm: Checking user space page tables May 24 12:27:49 localhost kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found. May 24 12:27:49 localhost kernel: Run /init as init process May 24 12:27:49 localhost kernel: with arguments: May 24 12:27:49 localhost kernel: /init May 24 12:27:49 localhost kernel: rhgb May 24 12:27:49 localhost kernel: with environment: May 24 12:27:49 localhost kernel: HOME=/ May 24 12:27:49 localhost kernel: TERM=linux May 24 12:27:49 localhost kernel: BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-5.14.0-583.el9.x86_64 May 24 12:27:49 localhost systemd[1]: systemd 252-53.el9 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) May 24 12:27:49 localhost systemd[1]: Detected virtualization xen. May 24 12:27:49 localhost systemd[1]: Detected architecture x86-64. May 24 12:27:49 localhost systemd[1]: Running in initrd. May 24 12:27:49 localhost systemd[1]: No hostname configured, using default hostname. May 24 12:27:49 localhost systemd[1]: Hostname set to . May 24 12:27:49 localhost systemd[1]: Queued start job for default target Initrd Default Target. May 24 12:27:49 localhost systemd[1]: Started Dispatch Password Requests to Console Directory Watch. May 24 12:27:49 localhost systemd[1]: Reached target Initrd /usr File System. May 24 12:27:49 localhost systemd[1]: Reached target Local File Systems. May 24 12:27:49 localhost systemd[1]: Reached target Path Units. May 24 12:27:49 localhost systemd[1]: Reached target Slice Units. May 24 12:27:49 localhost systemd[1]: Reached target Swaps. May 24 12:27:49 localhost systemd[1]: Reached target Timer Units. May 24 12:27:49 localhost systemd[1]: Listening on D-Bus System Message Bus Socket. May 24 12:27:49 localhost systemd[1]: Listening on Journal Socket (/dev/log). May 24 12:27:49 localhost systemd[1]: Listening on Journal Socket. May 24 12:27:49 localhost systemd[1]: Listening on udev Control Socket. May 24 12:27:49 localhost systemd[1]: Listening on udev Kernel Socket. May 24 12:27:49 localhost systemd[1]: Reached target Socket Units. May 24 12:27:49 localhost systemd[1]: Starting Create List of Static Device Nodes... May 24 12:27:49 localhost systemd[1]: Starting Journal Service... May 24 12:27:49 localhost systemd[1]: Load Kernel Modules was skipped because no trigger condition checks were met. May 24 12:27:49 localhost systemd[1]: Starting Apply Kernel Variables... May 24 12:27:49 localhost systemd[1]: Starting Create System Users... May 24 12:27:49 localhost systemd-journald[231]: Journal started ░░ Subject: The journal has been started ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The system journal process has started up, opened the journal ░░ files for writing and is now ready to process requests. May 24 12:27:49 localhost systemd-journald[231]: Runtime Journal (/run/log/journal/72dbb896bb5848cfa189670654d7ed83) is 8.0M, max 69.3M, 61.3M free. ░░ Subject: Disk space used by the journal ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ Runtime Journal (/run/log/journal/72dbb896bb5848cfa189670654d7ed83) is currently using 8.0M. ░░ Maximum allowed usage is set to 69.3M. ░░ Leaving at least 34.6M free (of currently available 685.0M of disk space). ░░ Enforced usage limit is thus 69.3M, of which 61.3M are still available. ░░ ░░ The limits controlling how much disk space is used by the journal may ░░ be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, ░░ RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in ░░ /etc/systemd/journald.conf. See journald.conf(5) for details. May 24 12:27:49 localhost systemd[1]: Starting Setup Virtual Console... May 24 12:27:49 localhost systemd[1]: Started Journal Service. May 24 12:27:49 localhost systemd[1]: Finished Create List of Static Device Nodes. ░░ Subject: A start job for unit kmod-static-nodes.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit kmod-static-nodes.service has finished successfully. ░░ ░░ The job identifier is 24. May 24 12:27:49 localhost systemd-sysusers[233]: Creating group 'nobody' with GID 65534. May 24 12:27:49 localhost systemd[1]: Finished Apply Kernel Variables. ░░ Subject: A start job for unit systemd-sysctl.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-sysctl.service has finished successfully. ░░ ░░ The job identifier is 8. May 24 12:27:49 localhost systemd-sysusers[233]: Creating group 'users' with GID 100. May 24 12:27:49 localhost systemd-sysusers[233]: Creating group 'dbus' with GID 81. May 24 12:27:49 localhost systemd-sysusers[233]: Creating user 'dbus' (System Message Bus) with UID 81 and GID 81. May 24 12:27:49 localhost systemd[1]: Finished Create System Users. ░░ Subject: A start job for unit systemd-sysusers.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-sysusers.service has finished successfully. ░░ ░░ The job identifier is 9. May 24 12:27:49 localhost systemd[1]: Starting Create Static Device Nodes in /dev... ░░ Subject: A start job for unit systemd-tmpfiles-setup-dev.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-tmpfiles-setup-dev.service has begun execution. ░░ ░░ The job identifier is 26. May 24 12:27:49 localhost systemd[1]: Starting Create Volatile Files and Directories... ░░ Subject: A start job for unit systemd-tmpfiles-setup.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-tmpfiles-setup.service has begun execution. ░░ ░░ The job identifier is 25. May 24 12:27:49 localhost systemd[1]: Finished Create Static Device Nodes in /dev. ░░ Subject: A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully. ░░ ░░ The job identifier is 26. May 24 12:27:49 localhost systemd[1]: Finished Create Volatile Files and Directories. ░░ Subject: A start job for unit systemd-tmpfiles-setup.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-tmpfiles-setup.service has finished successfully. ░░ ░░ The job identifier is 25. May 24 12:27:49 localhost systemd[1]: Finished Setup Virtual Console. ░░ Subject: A start job for unit systemd-vconsole-setup.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-vconsole-setup.service has finished successfully. ░░ ░░ The job identifier is 39. May 24 12:27:49 localhost systemd[1]: dracut ask for additional cmdline parameters was skipped because no trigger condition checks were met. ░░ Subject: A start job for unit dracut-cmdline-ask.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-cmdline-ask.service has finished successfully. ░░ ░░ The job identifier is 38. May 24 12:27:49 localhost systemd[1]: Starting dracut cmdline hook... ░░ Subject: A start job for unit dracut-cmdline.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-cmdline.service has begun execution. ░░ ░░ The job identifier is 49. May 24 12:27:49 localhost dracut-cmdline[248]: dracut-9 dracut-057-87.git20250311.el9 May 24 12:27:49 localhost dracut-cmdline[248]: Using kernel command line parameters: BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-5.14.0-583.el9.x86_64 root=UUID=5de771f1-9acb-4b75-bf56-ae0a7779ba73 ro rhgb crashkernel=2G-64G:256M,64G-:512M net.ifnames=0 console=tty0 console=ttyS0,115200n8 May 24 12:27:49 localhost kernel: input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4 May 24 12:27:49 localhost systemd[1]: Finished dracut cmdline hook. ░░ Subject: A start job for unit dracut-cmdline.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-cmdline.service has finished successfully. ░░ ░░ The job identifier is 49. May 24 12:27:49 localhost systemd[1]: Starting dracut pre-udev hook... ░░ Subject: A start job for unit dracut-pre-udev.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-pre-udev.service has begun execution. ░░ ░░ The job identifier is 52. May 24 12:27:49 localhost systemd[1]: Finished dracut pre-udev hook. ░░ Subject: A start job for unit dracut-pre-udev.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-pre-udev.service has finished successfully. ░░ ░░ The job identifier is 52. May 24 12:27:49 localhost systemd[1]: Starting Rule-based Manager for Device Events and Files... ░░ Subject: A start job for unit systemd-udevd.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-udevd.service has begun execution. ░░ ░░ The job identifier is 12. May 24 12:27:49 localhost systemd-udevd[329]: Using default interface naming scheme 'rhel-9.0'. May 24 12:27:49 localhost systemd[1]: Started Rule-based Manager for Device Events and Files. ░░ Subject: A start job for unit systemd-udevd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-udevd.service has finished successfully. ░░ ░░ The job identifier is 12. May 24 12:27:49 localhost systemd[1]: dracut pre-trigger hook was skipped because no trigger condition checks were met. ░░ Subject: A start job for unit dracut-pre-trigger.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-pre-trigger.service has finished successfully. ░░ ░░ The job identifier is 54. May 24 12:27:49 localhost systemd[1]: Starting Coldplug All udev Devices... ░░ Subject: A start job for unit systemd-udev-trigger.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-udev-trigger.service has begun execution. ░░ ░░ The job identifier is 11. May 24 12:27:49 localhost systemd[1]: Finished Coldplug All udev Devices. ░░ Subject: A start job for unit systemd-udev-trigger.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-udev-trigger.service has finished successfully. ░░ ░░ The job identifier is 11. May 24 12:27:49 localhost systemd[1]: Reached target System Initialization. ░░ Subject: A start job for unit sysinit.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sysinit.target has finished successfully. ░░ ░░ The job identifier is 3. May 24 12:27:49 localhost systemd[1]: Reached target Basic System. ░░ Subject: A start job for unit basic.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit basic.target has finished successfully. ░░ ░░ The job identifier is 2. May 24 12:27:49 localhost systemd[1]: nm-initrd.service was skipped because of an unmet condition check (ConditionPathExists=/run/NetworkManager/initrd/neednet). ░░ Subject: A start job for unit nm-initrd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit nm-initrd.service has finished successfully. ░░ ░░ The job identifier is 33. May 24 12:27:49 localhost systemd[1]: Reached target Network. ░░ Subject: A start job for unit network.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit network.target has finished successfully. ░░ ░░ The job identifier is 35. May 24 12:27:49 localhost systemd[1]: nm-wait-online-initrd.service was skipped because of an unmet condition check (ConditionPathExists=/run/NetworkManager/initrd/neednet). ░░ Subject: A start job for unit nm-wait-online-initrd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit nm-wait-online-initrd.service has finished successfully. ░░ ░░ The job identifier is 51. May 24 12:27:49 localhost systemd[1]: Starting dracut initqueue hook... ░░ Subject: A start job for unit dracut-initqueue.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-initqueue.service has begun execution. ░░ ░░ The job identifier is 45. May 24 12:27:49 localhost kernel: Invalid max_queues (4), will use default max: 2. May 24 12:27:49 localhost kernel: blkfront: xvda: barrier or flush: disabled; persistent grants: disabled; indirect descriptors: enabled; May 24 12:27:49 localhost kernel: xvda: xvda1 May 24 12:27:49 localhost kernel: xen_netfront: Initialising Xen virtual ethernet driver May 24 12:27:49 localhost kernel: libata version 3.00 loaded. May 24 12:27:49 localhost kernel: ata_piix 0000:00:01.1: version 2.13 May 24 12:27:49 localhost kernel: scsi host0: ata_piix May 24 12:27:49 localhost kernel: scsi host1: ata_piix May 24 12:27:49 localhost kernel: ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14 lpm-pol 0 May 24 12:27:49 localhost kernel: ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15 lpm-pol 0 May 24 12:27:50 localhost systemd-udevd[349]: Network interface NamePolicy= disabled on kernel command line. May 24 12:27:50 localhost systemd[1]: Found device /dev/disk/by-uuid/5de771f1-9acb-4b75-bf56-ae0a7779ba73. ░░ Subject: A start job for unit dev-disk-by\x2duuid-5de771f1\x2d9acb\x2d4b75\x2dbf56\x2dae0a7779ba73.device has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dev-disk-by\x2duuid-5de771f1\x2d9acb\x2d4b75\x2dbf56\x2dae0a7779ba73.device has finished successfully. ░░ ░░ The job identifier is 32. May 24 12:27:50 localhost systemd[1]: Reached target Initrd Root Device. ░░ Subject: A start job for unit initrd-root-device.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd-root-device.target has finished successfully. ░░ ░░ The job identifier is 31. May 24 12:27:50 localhost systemd[1]: Finished dracut initqueue hook. ░░ Subject: A start job for unit dracut-initqueue.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-initqueue.service has finished successfully. ░░ ░░ The job identifier is 45. May 24 12:27:50 localhost systemd[1]: Reached target Preparation for Remote File Systems. ░░ Subject: A start job for unit remote-fs-pre.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit remote-fs-pre.target has finished successfully. ░░ ░░ The job identifier is 46. May 24 12:27:50 localhost systemd[1]: Reached target Remote File Systems. ░░ Subject: A start job for unit remote-fs.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit remote-fs.target has finished successfully. ░░ ░░ The job identifier is 37. May 24 12:27:50 localhost systemd[1]: Starting dracut pre-mount hook... ░░ Subject: A start job for unit dracut-pre-mount.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-pre-mount.service has begun execution. ░░ ░░ The job identifier is 50. May 24 12:27:50 localhost systemd[1]: Finished dracut pre-mount hook. ░░ Subject: A start job for unit dracut-pre-mount.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-pre-mount.service has finished successfully. ░░ ░░ The job identifier is 50. May 24 12:27:50 localhost systemd[1]: Starting File System Check on /dev/disk/by-uuid/5de771f1-9acb-4b75-bf56-ae0a7779ba73... ░░ Subject: A start job for unit systemd-fsck-root.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-fsck-root.service has begun execution. ░░ ░░ The job identifier is 42. May 24 12:27:50 localhost systemd-fsck[392]: /usr/sbin/fsck.xfs: XFS file system. May 24 12:27:50 localhost systemd[1]: Finished File System Check on /dev/disk/by-uuid/5de771f1-9acb-4b75-bf56-ae0a7779ba73. ░░ Subject: A start job for unit systemd-fsck-root.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-fsck-root.service has finished successfully. ░░ ░░ The job identifier is 42. May 24 12:27:50 localhost systemd[1]: Mounting /sysroot... ░░ Subject: A start job for unit sysroot.mount has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sysroot.mount has begun execution. ░░ ░░ The job identifier is 41. May 24 12:27:50 localhost kernel: SGI XFS with ACLs, security attributes, scrub, quota, no debug enabled May 24 12:27:50 localhost kernel: XFS (xvda1): Mounting V5 Filesystem 5de771f1-9acb-4b75-bf56-ae0a7779ba73 May 24 12:27:51 localhost kernel: XFS (xvda1): Ending clean mount May 24 12:27:51 localhost systemd[1]: Mounted /sysroot. ░░ Subject: A start job for unit sysroot.mount has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sysroot.mount has finished successfully. ░░ ░░ The job identifier is 41. May 24 12:27:51 localhost systemd[1]: Reached target Initrd Root File System. ░░ Subject: A start job for unit initrd-root-fs.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd-root-fs.target has finished successfully. ░░ ░░ The job identifier is 40. May 24 12:27:51 localhost systemd[1]: Starting Mountpoints Configured in the Real Root... ░░ Subject: A start job for unit initrd-parse-etc.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd-parse-etc.service has begun execution. ░░ ░░ The job identifier is 47. May 24 12:27:51 localhost systemd[1]: initrd-parse-etc.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit initrd-parse-etc.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Finished Mountpoints Configured in the Real Root. ░░ Subject: A start job for unit initrd-parse-etc.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd-parse-etc.service has finished successfully. ░░ ░░ The job identifier is 47. May 24 12:27:51 localhost systemd[1]: Reached target Initrd File Systems. ░░ Subject: A start job for unit initrd-fs.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd-fs.target has finished successfully. ░░ ░░ The job identifier is 48. May 24 12:27:51 localhost systemd[1]: Reached target Initrd Default Target. ░░ Subject: A start job for unit initrd.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd.target has finished successfully. ░░ ░░ The job identifier is 1. May 24 12:27:51 localhost systemd[1]: dracut mount hook was skipped because no trigger condition checks were met. ░░ Subject: A start job for unit dracut-mount.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-mount.service has finished successfully. ░░ ░░ The job identifier is 53. May 24 12:27:51 localhost systemd[1]: Starting dracut pre-pivot and cleanup hook... ░░ Subject: A start job for unit dracut-pre-pivot.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-pre-pivot.service has begun execution. ░░ ░░ The job identifier is 36. May 24 12:27:51 localhost systemd[1]: Finished dracut pre-pivot and cleanup hook. ░░ Subject: A start job for unit dracut-pre-pivot.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-pre-pivot.service has finished successfully. ░░ ░░ The job identifier is 36. May 24 12:27:51 localhost systemd[1]: Starting Cleaning Up and Shutting Down Daemons... ░░ Subject: A start job for unit initrd-cleanup.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd-cleanup.service has begun execution. ░░ ░░ The job identifier is 57. May 24 12:27:51 localhost systemd[1]: Stopped target Network. ░░ Subject: A stop job for unit network.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit network.target has finished. ░░ ░░ The job identifier is 110 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Timer Units. ░░ Subject: A stop job for unit timers.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit timers.target has finished. ░░ ░░ The job identifier is 92 and the job result is done. May 24 12:27:51 localhost systemd[1]: dbus.socket: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit dbus.socket has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Closed D-Bus System Message Bus Socket. ░░ Subject: A stop job for unit dbus.socket has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit dbus.socket has finished. ░░ ░░ The job identifier is 93 and the job result is done. May 24 12:27:51 localhost systemd[1]: dracut-pre-pivot.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit dracut-pre-pivot.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped dracut pre-pivot and cleanup hook. ░░ Subject: A stop job for unit dracut-pre-pivot.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit dracut-pre-pivot.service has finished. ░░ ░░ The job identifier is 98 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Initrd Default Target. ░░ Subject: A stop job for unit initrd.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit initrd.target has finished. ░░ ░░ The job identifier is 89 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Basic System. ░░ Subject: A stop job for unit basic.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit basic.target has finished. ░░ ░░ The job identifier is 102 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Initrd Root Device. ░░ Subject: A stop job for unit initrd-root-device.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit initrd-root-device.target has finished. ░░ ░░ The job identifier is 107 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Initrd /usr File System. ░░ Subject: A stop job for unit initrd-usr-fs.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit initrd-usr-fs.target has finished. ░░ ░░ The job identifier is 90 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Path Units. ░░ Subject: A stop job for unit paths.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit paths.target has finished. ░░ ░░ The job identifier is 114 and the job result is done. May 24 12:27:51 localhost systemd[1]: systemd-ask-password-console.path: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-ask-password-console.path has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch. ░░ Subject: A stop job for unit systemd-ask-password-console.path has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit systemd-ask-password-console.path has finished. ░░ ░░ The job identifier is 91 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Remote File Systems. ░░ Subject: A stop job for unit remote-fs.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit remote-fs.target has finished. ░░ ░░ The job identifier is 115 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Preparation for Remote File Systems. ░░ Subject: A stop job for unit remote-fs-pre.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit remote-fs-pre.target has finished. ░░ ░░ The job identifier is 112 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Slice Units. ░░ Subject: A stop job for unit slices.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit slices.target has finished. ░░ ░░ The job identifier is 105 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Socket Units. ░░ Subject: A stop job for unit sockets.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit sockets.target has finished. ░░ ░░ The job identifier is 111 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target System Initialization. ░░ Subject: A stop job for unit sysinit.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit sysinit.target has finished. ░░ ░░ The job identifier is 101 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Local File Systems. ░░ Subject: A stop job for unit local-fs.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit local-fs.target has finished. ░░ ░░ The job identifier is 108 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopped target Swaps. ░░ Subject: A stop job for unit swap.target has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit swap.target has finished. ░░ ░░ The job identifier is 106 and the job result is done. May 24 12:27:51 localhost systemd[1]: dracut-pre-mount.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit dracut-pre-mount.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped dracut pre-mount hook. ░░ Subject: A stop job for unit dracut-pre-mount.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit dracut-pre-mount.service has finished. ░░ ░░ The job identifier is 113 and the job result is done. May 24 12:27:51 localhost systemd[1]: dracut-initqueue.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit dracut-initqueue.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped dracut initqueue hook. ░░ Subject: A stop job for unit dracut-initqueue.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit dracut-initqueue.service has finished. ░░ ░░ The job identifier is 88 and the job result is done. May 24 12:27:51 localhost systemd[1]: systemd-sysctl.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-sysctl.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped Apply Kernel Variables. ░░ Subject: A stop job for unit systemd-sysctl.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit systemd-sysctl.service has finished. ░░ ░░ The job identifier is 104 and the job result is done. May 24 12:27:51 localhost systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-tmpfiles-setup.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped Create Volatile Files and Directories. ░░ Subject: A stop job for unit systemd-tmpfiles-setup.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit systemd-tmpfiles-setup.service has finished. ░░ ░░ The job identifier is 84 and the job result is done. May 24 12:27:51 localhost systemd[1]: systemd-udev-trigger.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-udev-trigger.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped Coldplug All udev Devices. ░░ Subject: A stop job for unit systemd-udev-trigger.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit systemd-udev-trigger.service has finished. ░░ ░░ The job identifier is 69 and the job result is done. May 24 12:27:51 localhost systemd[1]: Stopping Rule-based Manager for Device Events and Files... ░░ Subject: A stop job for unit systemd-udevd.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit systemd-udevd.service has begun execution. ░░ ░░ The job identifier is 73. May 24 12:27:51 localhost systemd[1]: systemd-vconsole-setup.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-vconsole-setup.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped Setup Virtual Console. ░░ Subject: A stop job for unit systemd-vconsole-setup.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit systemd-vconsole-setup.service has finished. ░░ ░░ The job identifier is 99 and the job result is done. May 24 12:27:51 localhost systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: run-credentials-systemd\x2dsysctl.service.mount: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit run-credentials-systemd\x2dsysctl.service.mount has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: systemd-udevd.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-udevd.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped Rule-based Manager for Device Events and Files. ░░ Subject: A stop job for unit systemd-udevd.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit systemd-udevd.service has finished. ░░ ░░ The job identifier is 73 and the job result is done. May 24 12:27:51 localhost systemd[1]: systemd-udevd-control.socket: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-udevd-control.socket has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Closed udev Control Socket. ░░ Subject: A stop job for unit systemd-udevd-control.socket has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit systemd-udevd-control.socket has finished. ░░ ░░ The job identifier is 71 and the job result is done. May 24 12:27:51 localhost systemd[1]: systemd-udevd-kernel.socket: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-udevd-kernel.socket has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Closed udev Kernel Socket. ░░ Subject: A stop job for unit systemd-udevd-kernel.socket has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit systemd-udevd-kernel.socket has finished. ░░ ░░ The job identifier is 72 and the job result is done. May 24 12:27:51 localhost systemd[1]: dracut-pre-udev.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit dracut-pre-udev.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped dracut pre-udev hook. ░░ Subject: A stop job for unit dracut-pre-udev.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit dracut-pre-udev.service has finished. ░░ ░░ The job identifier is 109 and the job result is done. May 24 12:27:51 localhost systemd[1]: dracut-cmdline.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit dracut-cmdline.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped dracut cmdline hook. ░░ Subject: A stop job for unit dracut-cmdline.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit dracut-cmdline.service has finished. ░░ ░░ The job identifier is 100 and the job result is done. May 24 12:27:51 localhost systemd[1]: Starting Cleanup udev Database... ░░ Subject: A start job for unit initrd-udevadm-cleanup-db.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd-udevadm-cleanup-db.service has begun execution. ░░ ░░ The job identifier is 68. May 24 12:27:51 localhost systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-tmpfiles-setup-dev.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped Create Static Device Nodes in /dev. ░░ Subject: A stop job for unit systemd-tmpfiles-setup-dev.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit systemd-tmpfiles-setup-dev.service has finished. ░░ ░░ The job identifier is 85 and the job result is done. May 24 12:27:51 localhost systemd[1]: kmod-static-nodes.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit kmod-static-nodes.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped Create List of Static Device Nodes. ░░ Subject: A stop job for unit kmod-static-nodes.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit kmod-static-nodes.service has finished. ░░ ░░ The job identifier is 97 and the job result is done. May 24 12:27:51 localhost systemd[1]: systemd-sysusers.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-sysusers.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Stopped Create System Users. ░░ Subject: A stop job for unit systemd-sysusers.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit systemd-sysusers.service has finished. ░░ ░░ The job identifier is 87 and the job result is done. May 24 12:27:51 localhost systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup\x2ddev.service.mount: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit run-credentials-systemd\x2dtmpfiles\x2dsetup\x2ddev.service.mount has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: run-credentials-systemd\x2dsysusers.service.mount: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit run-credentials-systemd\x2dsysusers.service.mount has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: initrd-cleanup.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit initrd-cleanup.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Finished Cleaning Up and Shutting Down Daemons. ░░ Subject: A start job for unit initrd-cleanup.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd-cleanup.service has finished successfully. ░░ ░░ The job identifier is 57. May 24 12:27:51 localhost systemd[1]: initrd-udevadm-cleanup-db.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit initrd-udevadm-cleanup-db.service has successfully entered the 'dead' state. May 24 12:27:51 localhost systemd[1]: Finished Cleanup udev Database. ░░ Subject: A start job for unit initrd-udevadm-cleanup-db.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd-udevadm-cleanup-db.service has finished successfully. ░░ ░░ The job identifier is 68. May 24 12:27:51 localhost systemd[1]: Reached target Switch Root. ░░ Subject: A start job for unit initrd-switch-root.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd-switch-root.target has finished successfully. ░░ ░░ The job identifier is 60. May 24 12:27:51 localhost systemd[1]: Starting Switch Root... ░░ Subject: A start job for unit initrd-switch-root.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit initrd-switch-root.service has begun execution. ░░ ░░ The job identifier is 75. May 24 12:27:51 localhost systemd[1]: Switching root. May 24 12:27:51 localhost systemd-journald[231]: Journal stopped ░░ Subject: The journal has been stopped ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The system journal process has shut down and closed all currently ░░ active journal files. May 24 12:27:56 localhost systemd-journald[231]: Received SIGTERM from PID 1 (systemd). May 24 12:27:56 localhost kernel: audit: type=1404 audit(1748104073.166:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1 May 24 12:27:56 localhost kernel: SELinux: policy capability network_peer_controls=1 May 24 12:27:56 localhost kernel: SELinux: policy capability open_perms=1 May 24 12:27:56 localhost kernel: SELinux: policy capability extended_socket_class=1 May 24 12:27:56 localhost kernel: SELinux: policy capability always_check_network=0 May 24 12:27:56 localhost kernel: SELinux: policy capability cgroup_seclabel=1 May 24 12:27:56 localhost kernel: SELinux: policy capability nnp_nosuid_transition=1 May 24 12:27:56 localhost kernel: SELinux: policy capability genfs_seclabel_symlinks=1 May 24 12:27:56 localhost kernel: audit: type=1403 audit(1748104073.636:3): auid=4294967295 ses=4294967295 lsm=selinux res=1 May 24 12:27:56 localhost systemd[1]: Successfully loaded SELinux policy in 476.281ms. May 24 12:27:56 localhost systemd[1]: Relabelled /dev, /dev/shm, /run, /sys/fs/cgroup in 19.028ms. May 24 12:27:56 localhost systemd[1]: systemd 252-53.el9 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) May 24 12:27:56 localhost systemd[1]: Detected virtualization xen. May 24 12:27:56 localhost systemd[1]: Detected architecture x86-64. May 24 12:27:56 localhost systemd[1]: Initializing machine ID from random generator. May 24 12:27:56 localhost systemd[1]: Installed transient /etc/machine-id file. May 24 12:27:56 localhost systemd-rc-local-generator[457]: /etc/rc.d/rc.local is not marked executable, skipping. May 24 12:27:56 localhost systemd[1]: initrd-switch-root.service: Deactivated successfully. May 24 12:27:56 localhost systemd[1]: Stopped Switch Root. May 24 12:27:56 localhost systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1. May 24 12:27:56 localhost systemd[1]: Created slice Slice /system/getty. May 24 12:27:56 localhost systemd[1]: Created slice Slice /system/modprobe. May 24 12:27:56 localhost systemd[1]: Created slice Slice /system/serial-getty. May 24 12:27:56 localhost systemd[1]: Created slice Slice /system/sshd-keygen. May 24 12:27:56 localhost systemd[1]: Created slice User and Session Slice. May 24 12:27:56 localhost systemd[1]: Started Dispatch Password Requests to Console Directory Watch. May 24 12:27:56 localhost systemd[1]: Started Forward Password Requests to Wall Directory Watch. May 24 12:27:56 localhost systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. May 24 12:27:56 localhost systemd[1]: Reached target Local Encrypted Volumes. May 24 12:27:56 localhost systemd[1]: Stopped target Switch Root. May 24 12:27:56 localhost systemd[1]: Stopped target Initrd File Systems. May 24 12:27:56 localhost systemd[1]: Stopped target Initrd Root File System. May 24 12:27:56 localhost systemd[1]: Reached target Local Integrity Protected Volumes. May 24 12:27:56 localhost systemd[1]: Reached target Path Units. May 24 12:27:56 localhost systemd[1]: Reached target Slice Units. May 24 12:27:56 localhost systemd[1]: Reached target Swaps. May 24 12:27:56 localhost systemd[1]: Reached target Local Verity Protected Volumes. May 24 12:27:56 localhost systemd[1]: Listening on RPCbind Server Activation Socket. May 24 12:27:56 localhost systemd[1]: Reached target RPC Port Mapper. May 24 12:27:56 localhost systemd[1]: Listening on Process Core Dump Socket. May 24 12:27:56 localhost systemd[1]: Listening on initctl Compatibility Named Pipe. May 24 12:27:56 localhost systemd[1]: Listening on udev Control Socket. May 24 12:27:56 localhost systemd[1]: Listening on udev Kernel Socket. May 24 12:27:56 localhost systemd[1]: Mounting Huge Pages File System... May 24 12:27:56 localhost systemd[1]: Mounting POSIX Message Queue File System... May 24 12:27:56 localhost systemd[1]: Mounting Kernel Debug File System... May 24 12:27:56 localhost systemd[1]: Mounting Kernel Trace File System... May 24 12:27:56 localhost systemd[1]: Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab). May 24 12:27:56 localhost systemd[1]: Starting Create List of Static Device Nodes... May 24 12:27:56 localhost systemd[1]: Starting Load Kernel Module configfs... May 24 12:27:56 localhost systemd[1]: Starting Load Kernel Module drm... May 24 12:27:56 localhost systemd[1]: Starting Load Kernel Module efi_pstore... May 24 12:27:56 localhost systemd[1]: Starting Load Kernel Module fuse... May 24 12:27:56 localhost systemd[1]: Starting Read and set NIS domainname from /etc/sysconfig/network... May 24 12:27:56 localhost systemd[1]: systemd-fsck-root.service: Deactivated successfully. May 24 12:27:56 localhost systemd[1]: Stopped File System Check on Root Device. May 24 12:27:56 localhost systemd[1]: Stopped Journal Service. May 24 12:27:56 localhost systemd[1]: Starting Journal Service... May 24 12:27:56 localhost systemd[1]: Load Kernel Modules was skipped because no trigger condition checks were met. May 24 12:27:56 localhost kernel: fuse: init (API version 7.37) May 24 12:27:56 localhost systemd[1]: Starting Generate network units from Kernel command line... May 24 12:27:56 localhost systemd[1]: TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f). May 24 12:27:56 localhost systemd[1]: Starting Remount Root and Kernel File Systems... May 24 12:27:56 localhost systemd[1]: Repartition Root Disk was skipped because no trigger condition checks were met. May 24 12:27:56 localhost systemd[1]: Starting Apply Kernel Variables... May 24 12:27:56 localhost systemd[1]: Starting Coldplug All udev Devices... May 24 12:27:56 localhost systemd[1]: Mounted Huge Pages File System. May 24 12:27:56 localhost systemd[1]: Mounted POSIX Message Queue File System. May 24 12:27:56 localhost systemd[1]: Mounted Kernel Debug File System. May 24 12:27:56 localhost systemd[1]: Mounted Kernel Trace File System. May 24 12:27:56 localhost systemd[1]: Finished Create List of Static Device Nodes. May 24 12:27:56 localhost systemd[1]: modprobe@configfs.service: Deactivated successfully. May 24 12:27:56 localhost systemd[1]: Finished Load Kernel Module configfs. May 24 12:27:56 localhost kernel: ACPI: bus type drm_connector registered May 24 12:27:56 localhost systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. May 24 12:27:56 localhost systemd[1]: Finished Load Kernel Module efi_pstore. May 24 12:27:56 localhost systemd[1]: modprobe@drm.service: Deactivated successfully. May 24 12:27:56 localhost systemd[1]: Finished Load Kernel Module drm. May 24 12:27:56 localhost systemd-journald[496]: Journal started ░░ Subject: The journal has been started ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The system journal process has started up, opened the journal ░░ files for writing and is now ready to process requests. May 24 12:27:56 localhost systemd-journald[496]: Runtime Journal (/run/log/journal/724784a6a67f4a1596e8e04c82c2c1c9) is 8.0M, max 69.3M, 61.3M free. ░░ Subject: Disk space used by the journal ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ Runtime Journal (/run/log/journal/724784a6a67f4a1596e8e04c82c2c1c9) is currently using 8.0M. ░░ Maximum allowed usage is set to 69.3M. ░░ Leaving at least 34.6M free (of currently available 676.9M of disk space). ░░ Enforced usage limit is thus 69.3M, of which 61.3M are still available. ░░ ░░ The limits controlling how much disk space is used by the journal may ░░ be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, ░░ RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in ░░ /etc/systemd/journald.conf. See journald.conf(5) for details. May 24 12:27:56 localhost systemd[1]: Queued start job for default target Multi-User System. May 24 12:27:56 localhost systemd[1]: systemd-journald.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-journald.service has successfully entered the 'dead' state. May 24 12:27:56 localhost systemd[1]: Started Journal Service. May 24 12:27:56 localhost systemd[1]: modprobe@fuse.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit modprobe@fuse.service has successfully entered the 'dead' state. May 24 12:27:56 localhost systemd[1]: Finished Load Kernel Module fuse. ░░ Subject: A start job for unit modprobe@fuse.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit modprobe@fuse.service has finished successfully. ░░ ░░ The job identifier is 132. May 24 12:27:56 localhost systemd[1]: Finished Read and set NIS domainname from /etc/sysconfig/network. ░░ Subject: A start job for unit nis-domainname.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit nis-domainname.service has finished successfully. ░░ ░░ The job identifier is 171. May 24 12:27:56 localhost systemd[1]: Finished Generate network units from Kernel command line. ░░ Subject: A start job for unit systemd-network-generator.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-network-generator.service has finished successfully. ░░ ░░ The job identifier is 179. May 24 12:27:56 localhost systemd[1]: Finished Remount Root and Kernel File Systems. ░░ Subject: A start job for unit systemd-remount-fs.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-remount-fs.service has finished successfully. ░░ ░░ The job identifier is 139. May 24 12:27:56 localhost systemd[1]: Finished Apply Kernel Variables. ░░ Subject: A start job for unit systemd-sysctl.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-sysctl.service has finished successfully. ░░ ░░ The job identifier is 130. May 24 12:27:56 localhost systemd[1]: Mounting FUSE Control File System... ░░ Subject: A start job for unit sys-fs-fuse-connections.mount has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sys-fs-fuse-connections.mount has begun execution. ░░ ░░ The job identifier is 131. May 24 12:27:56 localhost systemd[1]: Mounting Kernel Configuration File System... ░░ Subject: A start job for unit sys-kernel-config.mount has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sys-kernel-config.mount has begun execution. ░░ ░░ The job identifier is 145. May 24 12:27:56 localhost systemd[1]: First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes). ░░ Subject: A start job for unit systemd-firstboot.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-firstboot.service has finished successfully. ░░ ░░ The job identifier is 135. May 24 12:27:56 localhost systemd[1]: Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc). ░░ Subject: A start job for unit systemd-hwdb-update.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-hwdb-update.service has finished successfully. ░░ ░░ The job identifier is 163. May 24 12:27:56 localhost systemd[1]: Starting Flush Journal to Persistent Storage... ░░ Subject: A start job for unit systemd-journal-flush.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-journal-flush.service has begun execution. ░░ ░░ The job identifier is 168. May 24 12:27:56 localhost systemd[1]: Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). ░░ Subject: A start job for unit systemd-pstore.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-pstore.service has finished successfully. ░░ ░░ The job identifier is 175. May 24 12:27:56 localhost systemd[1]: Starting Load/Save OS Random Seed... ░░ Subject: A start job for unit systemd-random-seed.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-random-seed.service has begun execution. ░░ ░░ The job identifier is 173. May 24 12:27:56 localhost systemd[1]: Create System Users was skipped because no trigger condition checks were met. ░░ Subject: A start job for unit systemd-sysusers.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-sysusers.service has finished successfully. ░░ ░░ The job identifier is 119. May 24 12:27:56 localhost systemd[1]: Starting Create Static Device Nodes in /dev... ░░ Subject: A start job for unit systemd-tmpfiles-setup-dev.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-tmpfiles-setup-dev.service has begun execution. ░░ ░░ The job identifier is 147. May 24 12:27:56 localhost systemd[1]: Mounted FUSE Control File System. ░░ Subject: A start job for unit sys-fs-fuse-connections.mount has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sys-fs-fuse-connections.mount has finished successfully. ░░ ░░ The job identifier is 131. May 24 12:27:56 localhost systemd[1]: Mounted Kernel Configuration File System. ░░ Subject: A start job for unit sys-kernel-config.mount has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sys-kernel-config.mount has finished successfully. ░░ ░░ The job identifier is 145. May 24 12:27:56 localhost systemd-journald[496]: Runtime Journal (/run/log/journal/724784a6a67f4a1596e8e04c82c2c1c9) is 8.0M, max 69.3M, 61.3M free. ░░ Subject: Disk space used by the journal ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ Runtime Journal (/run/log/journal/724784a6a67f4a1596e8e04c82c2c1c9) is currently using 8.0M. ░░ Maximum allowed usage is set to 69.3M. ░░ Leaving at least 34.6M free (of currently available 676.9M of disk space). ░░ Enforced usage limit is thus 69.3M, of which 61.3M are still available. ░░ ░░ The limits controlling how much disk space is used by the journal may ░░ be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, ░░ RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in ░░ /etc/systemd/journald.conf. See journald.conf(5) for details. May 24 12:27:56 localhost systemd-journald[496]: Received client request to flush runtime journal. May 24 12:27:56 localhost systemd[1]: Finished Load/Save OS Random Seed. ░░ Subject: A start job for unit systemd-random-seed.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-random-seed.service has finished successfully. ░░ ░░ The job identifier is 173. May 24 12:27:56 localhost systemd[1]: First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes). ░░ Subject: A start job for unit first-boot-complete.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit first-boot-complete.target has finished successfully. ░░ ░░ The job identifier is 136. May 24 12:27:56 localhost systemd[1]: Finished Flush Journal to Persistent Storage. ░░ Subject: A start job for unit systemd-journal-flush.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-journal-flush.service has finished successfully. ░░ ░░ The job identifier is 168. May 24 12:27:56 localhost systemd[1]: Finished Coldplug All udev Devices. ░░ Subject: A start job for unit systemd-udev-trigger.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-udev-trigger.service has finished successfully. ░░ ░░ The job identifier is 166. May 24 12:27:56 localhost systemd[1]: Finished Create Static Device Nodes in /dev. ░░ Subject: A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully. ░░ ░░ The job identifier is 147. May 24 12:27:56 localhost systemd[1]: Reached target Preparation for Local File Systems. ░░ Subject: A start job for unit local-fs-pre.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit local-fs-pre.target has finished successfully. ░░ ░░ The job identifier is 140. May 24 12:27:56 localhost systemd[1]: Reached target Local File Systems. ░░ Subject: A start job for unit local-fs.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit local-fs.target has finished successfully. ░░ ░░ The job identifier is 138. May 24 12:27:56 localhost systemd[1]: Rebuild Dynamic Linker Cache was skipped because no trigger condition checks were met. ░░ Subject: A start job for unit ldconfig.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit ldconfig.service has finished successfully. ░░ ░░ The job identifier is 134. May 24 12:27:56 localhost systemd[1]: Mark the need to relabel after reboot was skipped because of an unmet condition check (ConditionSecurity=!selinux). ░░ Subject: A start job for unit selinux-autorelabel-mark.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit selinux-autorelabel-mark.service has finished successfully. ░░ ░░ The job identifier is 137. May 24 12:27:56 localhost systemd[1]: Set Up Additional Binary Formats was skipped because no trigger condition checks were met. ░░ Subject: A start job for unit systemd-binfmt.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-binfmt.service has finished successfully. ░░ ░░ The job identifier is 164. May 24 12:27:56 localhost systemd[1]: Update Boot Loader Random Seed was skipped because no trigger condition checks were met. ░░ Subject: A start job for unit systemd-boot-random-seed.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-boot-random-seed.service has finished successfully. ░░ ░░ The job identifier is 158. May 24 12:27:56 localhost systemd[1]: Starting Automatic Boot Loader Update... ░░ Subject: A start job for unit systemd-boot-update.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-boot-update.service has begun execution. ░░ ░░ The job identifier is 161. May 24 12:27:56 localhost systemd[1]: Starting Commit a transient machine-id on disk... ░░ Subject: A start job for unit systemd-machine-id-commit.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-machine-id-commit.service has begun execution. ░░ ░░ The job identifier is 124. May 24 12:27:56 localhost systemd[1]: Starting Create Volatile Files and Directories... ░░ Subject: A start job for unit systemd-tmpfiles-setup.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-tmpfiles-setup.service has begun execution. ░░ ░░ The job identifier is 160. May 24 12:27:56 localhost systemd[1]: Starting Rule-based Manager for Device Events and Files... ░░ Subject: A start job for unit systemd-udevd.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-udevd.service has begun execution. ░░ ░░ The job identifier is 153. May 24 12:27:56 localhost bootctl[509]: Couldn't find EFI system partition, skipping. May 24 12:27:56 localhost systemd[1]: Finished Automatic Boot Loader Update. ░░ Subject: A start job for unit systemd-boot-update.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-boot-update.service has finished successfully. ░░ ░░ The job identifier is 161. May 24 12:27:56 localhost systemd[1]: Finished Commit a transient machine-id on disk. ░░ Subject: A start job for unit systemd-machine-id-commit.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-machine-id-commit.service has finished successfully. ░░ ░░ The job identifier is 124. May 24 12:27:56 localhost systemd-udevd[512]: Using default interface naming scheme 'rhel-9.0'. May 24 12:27:56 localhost systemd[1]: Finished Create Volatile Files and Directories. ░░ Subject: A start job for unit systemd-tmpfiles-setup.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-tmpfiles-setup.service has finished successfully. ░░ ░░ The job identifier is 160. May 24 12:27:56 localhost systemd[1]: Starting Security Auditing Service... ░░ Subject: A start job for unit auditd.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit auditd.service has begun execution. ░░ ░░ The job identifier is 236. May 24 12:27:56 localhost systemd[1]: Starting RPC Bind... ░░ Subject: A start job for unit rpcbind.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit rpcbind.service has begun execution. ░░ ░░ The job identifier is 247. May 24 12:27:56 localhost systemd[1]: Rebuild Journal Catalog was skipped because of an unmet condition check (ConditionNeedsUpdate=/var). ░░ Subject: A start job for unit systemd-journal-catalog-update.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-journal-catalog-update.service has finished successfully. ░░ ░░ The job identifier is 159. May 24 12:27:56 localhost systemd[1]: Update is Completed was skipped because no trigger condition checks were met. ░░ Subject: A start job for unit systemd-update-done.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-update-done.service has finished successfully. ░░ ░░ The job identifier is 167. May 24 12:27:57 localhost auditd[516]: No plugins found, not dispatching events May 24 12:27:57 localhost systemd[1]: Started Rule-based Manager for Device Events and Files. ░░ Subject: A start job for unit systemd-udevd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-udevd.service has finished successfully. ░░ ░░ The job identifier is 153. May 24 12:27:57 localhost systemd[1]: Starting Load Kernel Module configfs... ░░ Subject: A start job for unit modprobe@configfs.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit modprobe@configfs.service has begun execution. ░░ ░░ The job identifier is 265. May 24 12:27:57 localhost auditd[516]: Init complete, auditd 3.1.5 listening for events (startup state enable) May 24 12:27:57 localhost systemd[1]: modprobe@configfs.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit modprobe@configfs.service has successfully entered the 'dead' state. May 24 12:27:57 localhost systemd[1]: Finished Load Kernel Module configfs. ░░ Subject: A start job for unit modprobe@configfs.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit modprobe@configfs.service has finished successfully. ░░ ░░ The job identifier is 265. May 24 12:27:57 localhost systemd[1]: Condition check resulted in /dev/ttyS0 being skipped. ░░ Subject: A start job for unit dev-ttyS0.device has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dev-ttyS0.device has finished successfully. ░░ ░░ The job identifier is 208. May 24 12:27:57 localhost kernel: input: PC Speaker as /devices/platform/pcspkr/input/input5 May 24 12:27:57 localhost augenrules[537]: /sbin/augenrules: No change May 24 12:27:57 localhost systemd[1]: Started RPC Bind. ░░ Subject: A start job for unit rpcbind.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit rpcbind.service has finished successfully. ░░ ░░ The job identifier is 247. May 24 12:27:57 localhost augenrules[561]: No rules May 24 12:27:57 localhost augenrules[561]: enabled 1 May 24 12:27:57 localhost augenrules[561]: failure 1 May 24 12:27:57 localhost augenrules[561]: pid 516 May 24 12:27:57 localhost augenrules[561]: rate_limit 0 May 24 12:27:57 localhost augenrules[561]: backlog_limit 8192 May 24 12:27:57 localhost augenrules[561]: lost 0 May 24 12:27:57 localhost augenrules[561]: backlog 4 May 24 12:27:57 localhost augenrules[561]: backlog_wait_time 60000 May 24 12:27:57 localhost augenrules[561]: backlog_wait_time_actual 0 May 24 12:27:57 localhost augenrules[561]: enabled 1 May 24 12:27:57 localhost augenrules[561]: failure 1 May 24 12:27:57 localhost augenrules[561]: pid 516 May 24 12:27:57 localhost augenrules[561]: rate_limit 0 May 24 12:27:57 localhost augenrules[561]: backlog_limit 8192 May 24 12:27:57 localhost augenrules[561]: lost 0 May 24 12:27:57 localhost augenrules[561]: backlog 4 May 24 12:27:57 localhost augenrules[561]: backlog_wait_time 60000 May 24 12:27:57 localhost augenrules[561]: backlog_wait_time_actual 0 May 24 12:27:57 localhost augenrules[561]: enabled 1 May 24 12:27:57 localhost augenrules[561]: failure 1 May 24 12:27:57 localhost augenrules[561]: pid 516 May 24 12:27:57 localhost augenrules[561]: rate_limit 0 May 24 12:27:57 localhost augenrules[561]: backlog_limit 8192 May 24 12:27:57 localhost augenrules[561]: lost 0 May 24 12:27:57 localhost augenrules[561]: backlog 4 May 24 12:27:57 localhost augenrules[561]: backlog_wait_time 60000 May 24 12:27:57 localhost augenrules[561]: backlog_wait_time_actual 0 May 24 12:27:57 localhost systemd[1]: Started Security Auditing Service. ░░ Subject: A start job for unit auditd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit auditd.service has finished successfully. ░░ ░░ The job identifier is 236. May 24 12:27:57 localhost systemd[1]: Starting Record System Boot/Shutdown in UTMP... ░░ Subject: A start job for unit systemd-update-utmp.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-update-utmp.service has begun execution. ░░ ░░ The job identifier is 245. May 24 12:27:57 localhost systemd[1]: Finished Record System Boot/Shutdown in UTMP. ░░ Subject: A start job for unit systemd-update-utmp.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-update-utmp.service has finished successfully. ░░ ░░ The job identifier is 245. May 24 12:27:57 localhost kernel: piix4_smbus 0000:00:01.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr May 24 12:27:57 localhost systemd-udevd[532]: Network interface NamePolicy= disabled on kernel command line. May 24 12:27:57 localhost kernel: RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 655360 ms ovfl timer May 24 12:27:57 localhost kernel: cirrus 0000:00:02.0: vgaarb: deactivate vga console May 24 12:27:57 localhost kernel: Console: switching to colour dummy device 80x25 May 24 12:27:57 localhost kernel: [drm] Initialized cirrus 2.0.0 for 0000:00:02.0 on minor 0 May 24 12:27:57 localhost kernel: fbcon: cirrusdrmfb (fb0) is primary device May 24 12:27:57 localhost kernel: Console: switching to colour frame buffer device 128x48 May 24 12:27:57 localhost kernel: cirrus 0000:00:02.0: [drm] fb0: cirrusdrmfb frame buffer device May 24 12:27:57 localhost systemd[1]: etc-machine\x2did.mount: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit etc-machine\x2did.mount has successfully entered the 'dead' state. May 24 12:27:57 localhost systemd[1]: Reached target System Initialization. ░░ Subject: A start job for unit sysinit.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sysinit.target has finished successfully. ░░ ░░ The job identifier is 118. May 24 12:27:57 localhost systemd[1]: Started dnf makecache --timer. ░░ Subject: A start job for unit dnf-makecache.timer has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dnf-makecache.timer has finished successfully. ░░ ░░ The job identifier is 184. May 24 12:27:57 localhost systemd[1]: Started Daily rotation of log files. ░░ Subject: A start job for unit logrotate.timer has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit logrotate.timer has finished successfully. ░░ ░░ The job identifier is 183. May 24 12:27:57 localhost systemd[1]: Started Daily Cleanup of Temporary Directories. ░░ Subject: A start job for unit systemd-tmpfiles-clean.timer has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-tmpfiles-clean.timer has finished successfully. ░░ ░░ The job identifier is 191. May 24 12:27:57 localhost systemd[1]: Reached target Timer Units. ░░ Subject: A start job for unit timers.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit timers.target has finished successfully. ░░ ░░ The job identifier is 182. May 24 12:27:57 localhost systemd[1]: Listening on D-Bus System Message Bus Socket. ░░ Subject: A start job for unit dbus.socket has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dbus.socket has finished successfully. ░░ ░░ The job identifier is 188. May 24 12:27:57 localhost systemd[1]: Listening on SSSD Kerberos Cache Manager responder socket. ░░ Subject: A start job for unit sssd-kcm.socket has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sssd-kcm.socket has finished successfully. ░░ ░░ The job identifier is 198. May 24 12:27:57 localhost systemd[1]: Reached target Socket Units. ░░ Subject: A start job for unit sockets.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sockets.target has finished successfully. ░░ ░░ The job identifier is 194. May 24 12:27:57 localhost systemd[1]: Mounting RPC Pipe File System... ░░ Subject: A start job for unit var-lib-nfs-rpc_pipefs.mount has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit var-lib-nfs-rpc_pipefs.mount has begun execution. ░░ ░░ The job identifier is 219. May 24 12:27:57 localhost systemd[1]: Starting D-Bus System Message Bus... ░░ Subject: A start job for unit dbus-broker.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dbus-broker.service has begun execution. ░░ ░░ The job identifier is 189. May 24 12:27:57 localhost systemd[1]: TPM2 PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f). ░░ Subject: A start job for unit systemd-pcrphase-sysinit.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-pcrphase-sysinit.service has finished successfully. ░░ ░░ The job identifier is 170. May 24 12:27:57 localhost kernel: RPC: Registered named UNIX socket transport module. May 24 12:27:57 localhost kernel: RPC: Registered udp transport module. May 24 12:27:57 localhost kernel: RPC: Registered tcp transport module. May 24 12:27:57 localhost kernel: RPC: Registered tcp-with-tls transport module. May 24 12:27:57 localhost kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. May 24 12:27:57 localhost systemd[1]: Mounted RPC Pipe File System. ░░ Subject: A start job for unit var-lib-nfs-rpc_pipefs.mount has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit var-lib-nfs-rpc_pipefs.mount has finished successfully. ░░ ░░ The job identifier is 219. May 24 12:27:57 localhost systemd[1]: Reached target rpc_pipefs.target. ░░ Subject: A start job for unit rpc_pipefs.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit rpc_pipefs.target has finished successfully. ░░ ░░ The job identifier is 218. May 24 12:27:57 localhost systemd[1]: Started D-Bus System Message Bus. ░░ Subject: A start job for unit dbus-broker.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dbus-broker.service has finished successfully. ░░ ░░ The job identifier is 189. May 24 12:27:57 localhost systemd[1]: Reached target Basic System. ░░ Subject: A start job for unit basic.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit basic.target has finished successfully. ░░ ░░ The job identifier is 117. May 24 12:27:57 localhost dbus-broker-lau[592]: Ready May 24 12:27:57 localhost systemd[1]: Starting NTP client/server... ░░ Subject: A start job for unit chronyd.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit chronyd.service has begun execution. ░░ ░░ The job identifier is 221. May 24 12:27:57 localhost systemd[1]: Starting Cloud-init: Local Stage (pre-network)... ░░ Subject: A start job for unit cloud-init-local.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit cloud-init-local.service has begun execution. ░░ ░░ The job identifier is 235. May 24 12:27:57 localhost systemd[1]: Starting Restore /run/initramfs on shutdown... ░░ Subject: A start job for unit dracut-shutdown.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-shutdown.service has begun execution. ░░ ░░ The job identifier is 151. May 24 12:27:57 localhost systemd[1]: Started irqbalance daemon. ░░ Subject: A start job for unit irqbalance.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit irqbalance.service has finished successfully. ░░ ░░ The job identifier is 246. May 24 12:27:57 localhost systemd[1]: Load CPU microcode update was skipped because of an unmet condition check (ConditionPathExists=/sys/devices/system/cpu/microcode/reload). ░░ Subject: A start job for unit microcode.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit microcode.service has finished successfully. ░░ ░░ The job identifier is 193. May 24 12:27:57 localhost systemd[1]: Started Hardware RNG Entropy Gatherer Daemon. ░░ Subject: A start job for unit rngd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit rngd.service has finished successfully. ░░ ░░ The job identifier is 243. May 24 12:27:57 localhost systemd[1]: OpenSSH ecdsa Server Key Generation was skipped because of an unmet condition check (ConditionPathExists=!/run/systemd/generator.early/multi-user.target.wants/cloud-init.target). ░░ Subject: A start job for unit sshd-keygen@ecdsa.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sshd-keygen@ecdsa.service has finished successfully. ░░ ░░ The job identifier is 234. May 24 12:27:57 localhost systemd[1]: OpenSSH ed25519 Server Key Generation was skipped because of an unmet condition check (ConditionPathExists=!/run/systemd/generator.early/multi-user.target.wants/cloud-init.target). ░░ Subject: A start job for unit sshd-keygen@ed25519.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sshd-keygen@ed25519.service has finished successfully. ░░ ░░ The job identifier is 233. May 24 12:27:57 localhost systemd[1]: OpenSSH rsa Server Key Generation was skipped because of an unmet condition check (ConditionPathExists=!/run/systemd/generator.early/multi-user.target.wants/cloud-init.target). ░░ Subject: A start job for unit sshd-keygen@rsa.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sshd-keygen@rsa.service has finished successfully. ░░ ░░ The job identifier is 231. May 24 12:27:57 localhost systemd[1]: Reached target sshd-keygen.target. ░░ Subject: A start job for unit sshd-keygen.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sshd-keygen.target has finished successfully. ░░ ░░ The job identifier is 230. May 24 12:27:57 localhost systemd[1]: System Security Services Daemon was skipped because no trigger condition checks were met. ░░ Subject: A start job for unit sssd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sssd.service has finished successfully. ░░ ░░ The job identifier is 249. May 24 12:27:57 localhost systemd[1]: Reached target User and Group Name Lookups. ░░ Subject: A start job for unit nss-user-lookup.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit nss-user-lookup.target has finished successfully. ░░ ░░ The job identifier is 250. May 24 12:27:57 localhost systemd[1]: Starting User Login Management... ░░ Subject: A start job for unit systemd-logind.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-logind.service has begun execution. ░░ ░░ The job identifier is 237. May 24 12:27:57 localhost systemd[1]: Starting Rotate log files... ░░ Subject: A start job for unit logrotate.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit logrotate.service has begun execution. ░░ ░░ The job identifier is 269. May 24 12:27:57 localhost systemd[1]: Finished Restore /run/initramfs on shutdown. ░░ Subject: A start job for unit dracut-shutdown.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dracut-shutdown.service has finished successfully. ░░ ░░ The job identifier is 151. May 24 12:27:57 localhost systemd-logind[601]: New seat seat0. ░░ Subject: A new seat seat0 is now available ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A new seat seat0 has been configured and is now available. May 24 12:27:57 localhost systemd-logind[601]: Watching system buttons on /dev/input/event0 (Power Button) May 24 12:27:57 localhost systemd-logind[601]: Watching system buttons on /dev/input/event1 (Sleep Button) May 24 12:27:57 localhost systemd-logind[601]: Watching system buttons on /dev/input/event2 (AT Translated Set 2 keyboard) May 24 12:27:57 localhost systemd[1]: Started User Login Management. ░░ Subject: A start job for unit systemd-logind.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-logind.service has finished successfully. ░░ ░░ The job identifier is 237. May 24 12:27:58 localhost systemd[1]: logrotate.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit logrotate.service has successfully entered the 'dead' state. May 24 12:27:58 localhost systemd[1]: Finished Rotate log files. ░░ Subject: A start job for unit logrotate.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit logrotate.service has finished successfully. ░░ ░░ The job identifier is 269. May 24 12:27:58 localhost rngd[600]: Disabling 7: PKCS11 Entropy generator (pkcs11) May 24 12:27:58 localhost rngd[600]: Disabling 5: NIST Network Entropy Beacon (nist) May 24 12:27:58 localhost rngd[600]: Disabling 9: Qrypt quantum entropy beacon (qrypt) May 24 12:27:58 localhost rngd[600]: Disabling 10: Named pipe entropy input (namedpipe) May 24 12:27:58 localhost rngd[600]: Initializing available sources May 24 12:27:58 localhost rngd[600]: [hwrng ]: Initialization Failed May 24 12:27:58 localhost rngd[600]: [rdrand]: Enabling RDRAND rng support May 24 12:27:58 localhost rngd[600]: [rdrand]: Initialized May 24 12:27:58 localhost rngd[600]: [jitter]: JITTER timeout set to 5 sec May 24 12:27:58 localhost chronyd[609]: chronyd version 4.6.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 +DEBUG) May 24 12:27:58 localhost chronyd[609]: Loaded 0 symmetric keys May 24 12:27:58 localhost chronyd[609]: Using right/UTC timezone to obtain leap second data May 24 12:27:58 localhost chronyd[609]: Frequency 0.000 +/- 1000000.000 ppm read from /var/lib/chrony/drift May 24 12:27:58 localhost rngd[600]: [jitter]: Initializing AES buffer May 24 12:27:58 localhost chronyd[609]: Loaded seccomp filter (level 2) May 24 12:27:58 localhost systemd[1]: Started NTP client/server. ░░ Subject: A start job for unit chronyd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit chronyd.service has finished successfully. ░░ ░░ The job identifier is 221. May 24 12:28:00 localhost cloud-init[614]: Cloud-init v. 24.4-5.el9 running 'init-local' at Sat, 24 May 2025 16:28:00 +0000. Up 12.42 seconds. May 24 12:28:00 localhost dhclient[618]: Internet Systems Consortium DHCP Client 4.4.2b1 May 24 12:28:00 localhost dhclient[618]: Copyright 2004-2019 Internet Systems Consortium. May 24 12:28:00 localhost dhclient[618]: All rights reserved. May 24 12:28:00 localhost dhclient[618]: For info, please visit https://www.isc.org/software/dhcp/ May 24 12:28:00 localhost dhclient[618]: May 24 12:28:00 localhost dhclient[618]: Listening on LPF/eth0/0e:e0:c8:c6:ff:03 May 24 12:28:00 localhost dhclient[618]: Sending on LPF/eth0/0e:e0:c8:c6:ff:03 May 24 12:28:00 localhost dhclient[618]: Sending on Socket/fallback May 24 12:28:00 localhost dhclient[618]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0xa2c38250) May 24 12:28:00 localhost dhclient[618]: DHCPOFFER of 10.31.42.9 from 10.31.40.1 May 24 12:28:00 localhost dhclient[618]: DHCPREQUEST for 10.31.42.9 on eth0 to 255.255.255.255 port 67 (xid=0xa2c38250) May 24 12:28:00 localhost dhclient[618]: DHCPACK of 10.31.42.9 from 10.31.40.1 (xid=0xa2c38250) May 24 12:28:00 localhost dhclient[618]: bound to 10.31.42.9 -- renewal in 1631 seconds. May 24 12:28:01 localhost systemd[1]: Starting Hostname Service... ░░ Subject: A start job for unit systemd-hostnamed.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-hostnamed.service has begun execution. ░░ ░░ The job identifier is 334. May 24 12:28:01 localhost systemd[1]: Started Hostname Service. ░░ Subject: A start job for unit systemd-hostnamed.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-hostnamed.service has finished successfully. ░░ ░░ The job identifier is 334. May 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-hostnamed[633]: Hostname set to (static) May 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Cloud-init: Local Stage (pre-network). ░░ Subject: A start job for unit cloud-init-local.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit cloud-init-local.service has finished successfully. ░░ ░░ The job identifier is 235. May 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Preparation for Network. ░░ Subject: A start job for unit network-pre.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit network-pre.target has finished successfully. ░░ ░░ The job identifier is 180. May 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Network Manager... ░░ Subject: A start job for unit NetworkManager.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit NetworkManager.service has begun execution. ░░ ░░ The job identifier is 187. May 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104081.9492] NetworkManager (version 1.53.4-1.el9) is starting... (boot:4051ef22-96d3-40cd-ac57-0cd4501136da) May 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104081.9496] Read config: /etc/NetworkManager/NetworkManager.conf, /run/NetworkManager/conf.d/15-carrier-timeout.conf May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0086] manager[0x561ab5ff4080]: monitoring kernel firmware directory '/lib/firmware'. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0123] hostname: hostname: using hostnamed May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0124] hostname: static hostname changed from (none) to "ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com" May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0136] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto) May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0696] manager[0x561ab5ff4080]: rfkill: Wi-Fi hardware radio set enabled May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0697] manager[0x561ab5ff4080]: rfkill: WWAN hardware radio set enabled May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0830] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.53.4-1.el9/libnm-device-plugin-team.so) May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0831] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0832] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0833] manager: Networking is enabled by state file May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0844] settings: Loaded settings plugin: keyfile (internal) May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Network Manager Script Dispatcher Service... ░░ Subject: A start job for unit NetworkManager-dispatcher.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit NetworkManager-dispatcher.service has begun execution. ░░ ░░ The job identifier is 401. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0929] settings: Loaded settings plugin: ifcfg-rh ("/usr/lib64/NetworkManager/1.53.4-1.el9/libnm-settings-plugin-ifcfg-rh.so") May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0970] Warning: the ifcfg-rh plugin is deprecated, please migrate connections to the keyfile format using "nmcli connection migrate" May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1000] dhcp: init: Using DHCP client 'internal' May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1005] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1) May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1025] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1054] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1096] device (lo): Activation: starting connection 'lo' (4f273044-8c71-499f-9adb-4acbd5e3d99d) May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. ░░ Subject: A start job for unit systemd-rfkill.socket has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-rfkill.socket has finished successfully. ░░ ░░ The job identifier is 467. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1168] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1177] device (eth0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Network Manager. ░░ Subject: A start job for unit NetworkManager.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit NetworkManager.service has finished successfully. ░░ ░░ The job identifier is 187. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Network. ░░ Subject: A start job for unit network.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit network.target has finished successfully. ░░ ░░ The job identifier is 190. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1255] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1298] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1305] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1310] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1315] device (eth0): carrier: link connected May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1319] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1345] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1359] policy: auto-activating connection 'System eth0' (5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03) May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1380] device (eth0): Activation: starting connection 'System eth0' (5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03) May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1383] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1389] manager: NetworkManager state is now CONNECTING May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1393] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1401] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1406] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Network Manager Wait Online... ░░ Subject: A start job for unit NetworkManager-wait-online.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit NetworkManager-wait-online.service has begun execution. ░░ ░░ The job identifier is 186. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1449] dhcp4 (eth0): state changed new lease, address=10.31.42.9 May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting GSSAPI Proxy Daemon... ░░ Subject: A start job for unit gssproxy.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit gssproxy.service has begun execution. ░░ ░░ The job identifier is 216. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1486] policy: set 'System eth0' (eth0) as default for IPv4 routing and DNS May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1559] device (eth0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Network Manager Script Dispatcher Service. ░░ Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit NetworkManager-dispatcher.service has finished successfully. ░░ ░░ The job identifier is 401. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2167] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2171] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2187] device (lo): Activation: successful, device activated. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2283] device (eth0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2286] device (eth0): state change: secondaries -> activated (reason 'none', managed-type: 'full') May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2295] manager: NetworkManager state is now CONNECTED_SITE May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2304] device (eth0): Activation: successful, device activated. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started GSSAPI Proxy Daemon. ░░ Subject: A start job for unit gssproxy.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit gssproxy.service has finished successfully. ░░ ░░ The job identifier is 216. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: RPC security service for NFS client and server was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab). ░░ Subject: A start job for unit rpc-gssd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit rpc-gssd.service has finished successfully. ░░ ░░ The job identifier is 217. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target NFS client services. ░░ Subject: A start job for unit nfs-client.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit nfs-client.target has finished successfully. ░░ ░░ The job identifier is 212. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Preparation for Remote File Systems. ░░ Subject: A start job for unit remote-fs-pre.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit remote-fs-pre.target has finished successfully. ░░ ░░ The job identifier is 213. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Remote File Systems. ░░ Subject: A start job for unit remote-fs.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit remote-fs.target has finished successfully. ░░ ░░ The job identifier is 211. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: TPM2 PCR Barrier (User) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f). ░░ Subject: A start job for unit systemd-pcrphase.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-pcrphase.service has finished successfully. ░░ ░░ The job identifier is 149. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2404] manager: NetworkManager state is now CONNECTED_GLOBAL May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2410] manager: startup complete May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Network Manager Wait Online. ░░ Subject: A start job for unit NetworkManager-wait-online.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit NetworkManager-wait-online.service has finished successfully. ░░ ░░ The job identifier is 186. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Cloud-init: Network Stage... ░░ Subject: A start job for unit cloud-init.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit cloud-init.service has begun execution. ░░ ░░ The job identifier is 228. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: Added source 10.11.160.238 May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: Added source 10.18.100.10 May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: Added source 10.2.32.37 May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: Added source 10.2.32.38 May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Cloud-init v. 24.4-5.el9 running 'init' at Sat, 24 May 2025 16:28:02 +0000. Up 14.79 seconds. May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: ++++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++++ May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+ May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address | May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+ May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | eth0 | True | 10.31.42.9 | 255.255.252.0 | global | 0e:e0:c8:c6:ff:03 | May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | eth0 | True | fe80::ce0:c8ff:fec6:ff03/64 | . | link | 0e:e0:c8:c6:ff:03 | May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . | May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | lo | True | ::1/128 | . | host | . | May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+ May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: ++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++ May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+------------+---------------+-----------+-------+ May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags | May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+------------+---------------+-----------+-------+ May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | 0 | 0.0.0.0 | 10.31.40.1 | 0.0.0.0 | eth0 | UG | May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | 1 | 10.31.40.0 | 0.0.0.0 | 255.255.252.0 | eth0 | U | May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+------------+---------------+-----------+-------+ May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++ May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+---------+-----------+-------+ May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | Route | Destination | Gateway | Interface | Flags | May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+---------+-----------+-------+ May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | 1 | fe80::/64 | :: | eth0 | U | May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | 3 | multicast | :: | eth0 | U | May 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+---------+-----------+-------+ May 24 12:28:03 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com rngd[600]: [jitter]: Unable to obtain AES key, disabling JITTER source May 24 12:28:03 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com rngd[600]: [jitter]: Initialization Failed May 24 12:28:03 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com rngd[600]: Process privileges have been dropped to 2:2 May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Generating public/private rsa key pair. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your identification has been saved in /etc/ssh/ssh_host_rsa_key May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key fingerprint is: May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: SHA256:zbzEJxtZ81eIa8MSjZogZupURfW2VkGaXxOvfDi7aR4 root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key's randomart image is: May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +---[RSA 3072]----+ May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | .o.. .o . | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . . = o + | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | = . B * + o| May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | = . . O O * +.| May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | o S & B * o| May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | o o O . = | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . o E | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | .+ | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | o+ | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +----[SHA256]-----+ May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Generating public/private ecdsa key pair. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key fingerprint is: May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: SHA256:cnwNg8gO+/X6khbK89rbxSM9Dj+tVBs7zcxFswcHQY8 root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key's randomart image is: May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +---[ECDSA 256]---+ May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | .+. | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . . . + | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . o . o E.+| May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | + . + +o| May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . o S . . o.o| May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . +.o o . Oo| May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | ... o+ B.+ =| May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | +.+o B.o.. | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | .==+o +o | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +----[SHA256]-----+ May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Generating public/private ed25519 key pair. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your identification has been saved in /etc/ssh/ssh_host_ed25519_key May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key fingerprint is: May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: SHA256:Pr+CPxgsSWJR6Y0VoUk6hgb2RVdf3EsGHWNqFkg1I5Y root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key's randomart image is: May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +--[ED25519 256]--+ May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: |.. .++o+...+=B++.| May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: |o.ooooo oEo.*=.| May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: |..++o+ . +o .| May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: |..o.+ . o . | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . o o S | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | o o. | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . +o | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | o oo | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | ..oo. | May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +----[SHA256]-----+ May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Cloud-init: Network Stage. ░░ Subject: A start job for unit cloud-init.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit cloud-init.service has finished successfully. ░░ ░░ The job identifier is 228. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Cloud-config availability. ░░ Subject: A start job for unit cloud-config.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit cloud-config.target has finished successfully. ░░ ░░ The job identifier is 227. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Network is Online. ░░ Subject: A start job for unit network-online.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit network-online.target has finished successfully. ░░ ░░ The job identifier is 185. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Cloud-init: Config Stage... ░░ Subject: A start job for unit cloud-config.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit cloud-config.service has begun execution. ░░ ░░ The job identifier is 226. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Crash recovery kernel arming... ░░ Subject: A start job for unit kdump.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit kdump.service has begun execution. ░░ ░░ The job identifier is 242. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting The restraint harness.... ░░ Subject: A start job for unit restraintd.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit restraintd.service has begun execution. ░░ ░░ The job identifier is 210. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Notify NFS peers of a restart... ░░ Subject: A start job for unit rpc-statd-notify.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit rpc-statd-notify.service has begun execution. ░░ ░░ The job identifier is 214. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting System Logging Service... ░░ Subject: A start job for unit rsyslog.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit rsyslog.service has begun execution. ░░ ░░ The job identifier is 209. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting OpenSSH server daemon... ░░ Subject: A start job for unit sshd.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sshd.service has begun execution. ░░ ░░ The job identifier is 229. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Permit User Sessions... ░░ Subject: A start job for unit systemd-user-sessions.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-user-sessions.service has begun execution. ░░ ░░ The job identifier is 248. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sm-notify[804]: Version 2.5.4 starting May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started The restraint harness.. ░░ Subject: A start job for unit restraintd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit restraintd.service has finished successfully. ░░ ░░ The job identifier is 210. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Notify NFS peers of a restart. ░░ Subject: A start job for unit rpc-statd-notify.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit rpc-statd-notify.service has finished successfully. ░░ ░░ The job identifier is 214. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Permit User Sessions. ░░ Subject: A start job for unit systemd-user-sessions.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-user-sessions.service has finished successfully. ░░ ░░ The job identifier is 248. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Command Scheduler. ░░ Subject: A start job for unit crond.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit crond.service has finished successfully. ░░ ░░ The job identifier is 240. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) STARTUP (1.5.7) May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (Syslog will be used instead of sendmail.) May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 55% if used.) May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (running with inotify support) May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Getty on tty1. ░░ Subject: A start job for unit getty@tty1.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit getty@tty1.service has finished successfully. ░░ ░░ The job identifier is 202. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com restraintd[810]: Listening on http://localhost:8081 May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Serial Getty on ttyS0. ░░ Subject: A start job for unit serial-getty@ttyS0.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit serial-getty@ttyS0.service has finished successfully. ░░ ░░ The job identifier is 206. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Login Prompts. ░░ Subject: A start job for unit getty.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit getty.target has finished successfully. ░░ ░░ The job identifier is 201. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[806]: Server listening on 0.0.0.0 port 22. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[806]: Server listening on :: port 22. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started OpenSSH server daemon. ░░ Subject: A start job for unit sshd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sshd.service has finished successfully. ░░ ░░ The job identifier is 229. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com rsyslogd[805]: [origin software="rsyslogd" swVersion="8.2412.0-2.el9" x-pid="805" x-info="https://www.rsyslog.com"] start May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started System Logging Service. ░░ Subject: A start job for unit rsyslog.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit rsyslog.service has finished successfully. ░░ ░░ The job identifier is 209. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Multi-User System. ░░ Subject: A start job for unit multi-user.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit multi-user.target has finished successfully. ░░ ░░ The job identifier is 116. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Record Runlevel Change in UTMP... ░░ Subject: A start job for unit systemd-update-utmp-runlevel.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-update-utmp-runlevel.service has begun execution. ░░ ░░ The job identifier is 244. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-update-utmp-runlevel.service has successfully entered the 'dead' state. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Record Runlevel Change in UTMP. ░░ Subject: A start job for unit systemd-update-utmp-runlevel.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-update-utmp-runlevel.service has finished successfully. ░░ ░░ The job identifier is 244. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com rsyslogd[805]: imjournal: journal files changed, reloading... [v8.2412.0-2.el9 try https://www.rsyslog.com/e/0 ] May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[867]: Cloud-init v. 24.4-5.el9 running 'modules:config' at Sat, 24 May 2025 16:28:04 +0000. Up 16.56 seconds. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopping OpenSSH server daemon... ░░ Subject: A stop job for unit sshd.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit sshd.service has begun execution. ░░ ░░ The job identifier is 488. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[806]: Received signal 15; terminating. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: sshd.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit sshd.service has successfully entered the 'dead' state. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopped OpenSSH server daemon. ░░ Subject: A stop job for unit sshd.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit sshd.service has finished. ░░ ░░ The job identifier is 488 and the job result is done. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting OpenSSH server daemon... ░░ Subject: A start job for unit sshd.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sshd.service has begun execution. ░░ ░░ The job identifier is 488. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[883]: Server listening on 0.0.0.0 port 22. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[883]: Server listening on :: port 22. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started OpenSSH server daemon. ░░ Subject: A start job for unit sshd.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sshd.service has finished successfully. ░░ ░░ The job identifier is 488. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Detected change(s) in the following file(s): /etc/fstab May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Cloud-init: Config Stage. ░░ Subject: A start job for unit cloud-config.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit cloud-config.service has finished successfully. ░░ ░░ The job identifier is 226. May 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Cloud-init: Final Stage... ░░ Subject: A start job for unit cloud-final.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit cloud-final.service has begun execution. ░░ ░░ The job identifier is 225. May 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1101]: Cloud-init v. 24.4-5.el9 running 'modules:final' at Sat, 24 May 2025 16:28:05 +0000. Up 17.12 seconds. May 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1103]: ############################################################# May 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1104]: -----BEGIN SSH HOST KEY FINGERPRINTS----- May 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1106]: 256 SHA256:cnwNg8gO+/X6khbK89rbxSM9Dj+tVBs7zcxFswcHQY8 root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com (ECDSA) May 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1108]: 256 SHA256:Pr+CPxgsSWJR6Y0VoUk6hgb2RVdf3EsGHWNqFkg1I5Y root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com (ED25519) May 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1110]: 3072 SHA256:zbzEJxtZ81eIa8MSjZogZupURfW2VkGaXxOvfDi7aR4 root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com (RSA) May 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1111]: -----END SSH HOST KEY FINGERPRINTS----- May 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1112]: ############################################################# May 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1101]: Cloud-init v. 24.4-5.el9 finished at Sat, 24 May 2025 16:28:05 +0000. Datasource DataSourceEc2Local. Up 17.23 seconds May 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Cloud-init: Final Stage. ░░ Subject: A start job for unit cloud-final.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit cloud-final.service has finished successfully. ░░ ░░ The job identifier is 225. May 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Cloud-init target. ░░ Subject: A start job for unit cloud-init.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit cloud-init.target has finished successfully. ░░ ░░ The job identifier is 224. May 24 12:28:06 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com kernel: block xvda: the capability attribute has been deprecated. May 24 12:28:06 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Rebuilding /boot/initramfs-5.14.0-583.el9.x86_64kdump.img May 24 12:28:07 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1448]: dracut-057-87.git20250311.el9 May 24 12:28:07 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Executing: /usr/bin/dracut --quiet --hostonly --hostonly-cmdline --hostonly-i18n --hostonly-mode strict --hostonly-nics --mount "/dev/disk/by-uuid/5de771f1-9acb-4b75-bf56-ae0a7779ba73 /sysroot xfs rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota" --squash-compressor zstd --no-hostonly-default-device --add-confdir /lib/kdump/dracut.conf.d -f /boot/initramfs-5.14.0-583.el9.x86_64kdump.img 5.14.0-583.el9.x86_64 May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 0 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 0 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 48 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 48 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 49 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 49 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 50 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 50 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 51 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 51 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 52 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 52 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 53 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 53 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 54 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 54 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 55 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 55 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 56 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 56 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 57 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 57 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 58 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 58 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 59 affinity: Operation not permitted May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 59 affinity is now unmanaged May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-timesyncd' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-time-wait-sync' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'busybox' will not be installed, because command 'busybox' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'dbus-daemon' will not be installed, because command 'dbus-daemon' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmand' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Module 'ifcfg' will not be installed, because it's in the list to be omitted! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Module 'plymouth' will not be installed, because it's in the list to be omitted! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: 62bluetooth: Could not find any command of '/usr/lib/bluetooth/bluetoothd /usr/libexec/bluetooth/bluetoothd'! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvmthinpool-monitor' will not be installed, because command 'lvm' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvm' will not be installed, because command 'lvm' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'pcsc' will not be installed, because command 'pcscd' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Module 'resume' will not be installed, because it's in the list to be omitted! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Module 'earlykdump' will not be installed, because it's in the list to be omitted! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: Selected source 10.2.32.38 May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: System clock TAI offset set to 37 seconds May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: memstrack is not available May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-timesyncd' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-time-wait-sync' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'busybox' will not be installed, because command 'busybox' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'dbus-daemon' will not be installed, because command 'dbus-daemon' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmand' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: 62bluetooth: Could not find any command of '/usr/lib/bluetooth/bluetoothd /usr/libexec/bluetooth/bluetoothd'! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvmthinpool-monitor' will not be installed, because command 'lvm' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvm' will not be installed, because command 'lvm' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'pcsc' will not be installed, because command 'pcscd' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found! May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: memstrack is not available May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: systemd *** May 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: fips *** May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: systemd-initrd *** May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: rngd *** May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: i18n *** May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: drm *** May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: prefixdevname *** May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: kernel-modules *** May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: kernel-modules-extra *** May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: kernel-modules-extra: configuration source "/run/depmod.d" does not exist May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: kernel-modules-extra: configuration source "/lib/depmod.d" does not exist May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: kernel-modules-extra: parsing configuration file "/etc/depmod.d/dist.conf" May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: kernel-modules-extra: /etc/depmod.d/dist.conf: added "updates extra built-in weak-updates" to the list of search directories May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: fstab-sys *** May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: rootfs-block *** May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: terminfo *** May 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: udev-rules *** May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Skipping udev rule: 91-permissions.rules May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Skipping udev rule: 80-drivers-modprobe.rules May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: dracut-systemd *** May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: usrmount *** May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: base *** May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: fs-lib *** May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: kdumpbase *** May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: microcode_ctl-fw_dir_override *** May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl module: mangling fw_dir May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: reset fw_dir to "/lib/firmware/updates /lib/firmware" May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel"... May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: intel: caveats check for kernel version "5.14.0-583.el9.x86_64" passed, adding "/usr/share/microcode_ctl/ucode_with_caveats/intel" to fw_dir variable May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-2d-07"... May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration "intel-06-2d-07" is ignored May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-4e-03"... May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration "intel-06-4e-03" is ignored May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-4f-01"... May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration "intel-06-4f-01" is ignored May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-55-04"... May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration "intel-06-55-04" is ignored May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-5e-03"... May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration "intel-06-5e-03" is ignored May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8c-01"... May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration "intel-06-8c-01" is ignored May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8e-9e-0x-0xca"... May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration "intel-06-8e-9e-0x-0xca" is ignored May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8e-9e-0x-dell"... May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration "intel-06-8e-9e-0x-dell" is ignored May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: final fw_dir: "/usr/share/microcode_ctl/ucode_with_caveats/intel /lib/firmware/updates /lib/firmware" May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: openssl *** May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: shutdown *** May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: squash *** May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including modules done *** May 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Installing kernel module dependencies *** May 24 12:28:11 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Installing kernel module dependencies done *** May 24 12:28:11 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Resolving executable dependencies *** May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state. May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Resolving executable dependencies done *** May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Hardlinking files *** May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Mode: real May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Files: 449 May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Linked: 2 files May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Compared: 0 xattrs May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Compared: 12 files May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Saved: 56.21 KiB May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Duration: 0.008749 seconds May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Hardlinking files done *** May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Generating early-microcode cpio image *** May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Constructing GenuineIntel.bin *** May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Constructing GenuineIntel.bin *** May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Store current command line parameters *** May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Stored kernel commandline: May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: No dracut internal kernel commandline stored in the initramfs May 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Install squash loader *** May 24 12:28:13 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Squashing the files inside the initramfs *** May 24 12:28:19 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Squashing the files inside the initramfs done *** May 24 12:28:19 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Creating image file '/boot/initramfs-5.14.0-583.el9.x86_64kdump.img' *** May 24 12:28:19 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Creating initramfs image file '/boot/initramfs-5.14.0-583.el9.x86_64kdump.img' done *** May 24 12:28:20 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: kexec: loaded kdump kernel May 24 12:28:20 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Starting kdump: [OK] May 24 12:28:20 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Crash recovery kernel arming. ░░ Subject: A start job for unit kdump.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit kdump.service has finished successfully. ░░ ░░ The job identifier is 242. May 24 12:28:20 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Startup finished in 1.148s (kernel) + 3.808s (initrd) + 27.564s (userspace) = 32.521s. ░░ Subject: System start-up is now complete ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ All system services necessary queued for starting at boot have been ░░ started. Note that this does not mean that the machine is now idle as services ░░ might still be busy with completing start-up. ░░ ░░ Kernel start-up required 1148938 microseconds. ░░ ░░ Initrd start-up required 3808129 microseconds. ░░ ░░ Userspace start-up required 27564245 microseconds. May 24 12:28:32 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: systemd-hostnamed.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-hostnamed.service has successfully entered the 'dead' state. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4245]: Accepted publickey for root from 10.30.33.24 port 56132 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Created slice User Slice of UID 0. ░░ Subject: A start job for unit user-0.slice has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit user-0.slice has finished successfully. ░░ ░░ The job identifier is 490. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting User Runtime Directory /run/user/0... ░░ Subject: A start job for unit user-runtime-dir@0.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit user-runtime-dir@0.service has begun execution. ░░ ░░ The job identifier is 556. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: New session 1 of user root. ░░ Subject: A new session 1 has been created for user root ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A new session with the ID 1 has been created for the user root. ░░ ░░ The leading process of the session is 4245. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished User Runtime Directory /run/user/0. ░░ Subject: A start job for unit user-runtime-dir@0.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit user-runtime-dir@0.service has finished successfully. ░░ ░░ The job identifier is 556. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting User Manager for UID 0... ░░ Subject: A start job for unit user@0.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit user@0.service has begun execution. ░░ ░░ The job identifier is 489. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0) May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Queued start job for default target Main User Target. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Created slice User Application Slice. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 5. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Mark boot as successful after the user session has run 2 minutes was skipped because of an unmet condition check (ConditionUser=!@system). ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 10. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Started Daily Cleanup of User's Temporary Directories. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 11. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Paths. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 8. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Timers. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 9. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Starting D-Bus User Message Bus Socket... ░░ Subject: A start job for unit UNIT has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has begun execution. ░░ ░░ The job identifier is 4. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Starting Create User's Volatile Files and Directories... ░░ Subject: A start job for unit UNIT has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has begun execution. ░░ ░░ The job identifier is 12. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Listening on D-Bus User Message Bus Socket. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 4. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Finished Create User's Volatile Files and Directories. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 12. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Sockets. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 3. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Basic System. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 2. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Main User Target. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 1. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Startup finished in 73ms. ░░ Subject: User manager start-up is now complete ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The user manager instance for user 0 has been started. All services queued ░░ for starting have been started. Note that other services might still be starting ░░ up or be started at any later time. ░░ ░░ Startup of the manager took 73418 microseconds. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started User Manager for UID 0. ░░ Subject: A start job for unit user@0.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit user@0.service has finished successfully. ░░ ░░ The job identifier is 489. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Session 1 of User root. ░░ Subject: A start job for unit session-1.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-1.scope has finished successfully. ░░ ░░ The job identifier is 557. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4245]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4258]: Received disconnect from 10.30.33.24 port 56132:11: disconnected by user May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4258]: Disconnected from user root 10.30.33.24 port 56132 May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4245]: pam_unix(sshd:session): session closed for user root May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: session-1.scope: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit session-1.scope has successfully entered the 'dead' state. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: Session 1 logged out. Waiting for processes to exit. May 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: Removed session 1. ░░ Subject: Session 1 has been terminated ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A session with the ID 1 has been terminated. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopping User Manager for UID 0... ░░ Subject: A stop job for unit user@0.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit user@0.service has begun execution. ░░ ░░ The job identifier is 626. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Activating special unit Exit the Session... May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped target Main User Target. ░░ Subject: A stop job for unit UNIT has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit UNIT has finished. ░░ ░░ The job identifier is 20 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped target Basic System. ░░ Subject: A stop job for unit UNIT has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit UNIT has finished. ░░ ░░ The job identifier is 18 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped target Paths. ░░ Subject: A stop job for unit UNIT has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit UNIT has finished. ░░ ░░ The job identifier is 23 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped target Sockets. ░░ Subject: A stop job for unit UNIT has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit UNIT has finished. ░░ ░░ The job identifier is 22 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped target Timers. ░░ Subject: A stop job for unit UNIT has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit UNIT has finished. ░░ ░░ The job identifier is 21 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped Daily Cleanup of User's Temporary Directories. ░░ Subject: A stop job for unit UNIT has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit UNIT has finished. ░░ ░░ The job identifier is 27 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Closed D-Bus User Message Bus Socket. ░░ Subject: A stop job for unit UNIT has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit UNIT has finished. ░░ ░░ The job identifier is 26 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped Create User's Volatile Files and Directories. ░░ Subject: A stop job for unit UNIT has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit UNIT has finished. ░░ ░░ The job identifier is 28 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Removed slice User Application Slice. ░░ Subject: A stop job for unit UNIT has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit UNIT has finished. ░░ ░░ The job identifier is 29 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Shutdown. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 15. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Finished Exit the Session. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 14. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Exit the Session. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 13. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: user@0.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit user@0.service has successfully entered the 'dead' state. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopped User Manager for UID 0. ░░ Subject: A stop job for unit user@0.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit user@0.service has finished. ░░ ░░ The job identifier is 626 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopping User Runtime Directory /run/user/0... ░░ Subject: A stop job for unit user-runtime-dir@0.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit user-runtime-dir@0.service has begun execution. ░░ ░░ The job identifier is 627. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: run-user-0.mount: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit run-user-0.mount has successfully entered the 'dead' state. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: user-runtime-dir@0.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit user-runtime-dir@0.service has successfully entered the 'dead' state. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopped User Runtime Directory /run/user/0. ░░ Subject: A stop job for unit user-runtime-dir@0.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit user-runtime-dir@0.service has finished. ░░ ░░ The job identifier is 627 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Removed slice User Slice of UID 0. ░░ Subject: A stop job for unit user-0.slice has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit user-0.slice has finished. ░░ ░░ The job identifier is 629 and the job result is done. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4295]: Accepted publickey for root from 10.31.9.54 port 34804 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4294]: Accepted publickey for root from 10.31.9.54 port 34794 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: New session 3 of user root. ░░ Subject: A new session 3 has been created for user root ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A new session with the ID 3 has been created for the user root. ░░ ░░ The leading process of the session is 4295. May 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Created slice User Slice of UID 0. ░░ Subject: A start job for unit user-0.slice has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit user-0.slice has finished successfully. ░░ ░░ The job identifier is 632. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting User Runtime Directory /run/user/0... ░░ Subject: A start job for unit user-runtime-dir@0.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit user-runtime-dir@0.service has begun execution. ░░ ░░ The job identifier is 698. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: New session 4 of user root. ░░ Subject: A new session 4 has been created for user root ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A new session with the ID 4 has been created for the user root. ░░ ░░ The leading process of the session is 4294. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished User Runtime Directory /run/user/0. ░░ Subject: A start job for unit user-runtime-dir@0.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit user-runtime-dir@0.service has finished successfully. ░░ ░░ The job identifier is 698. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting User Manager for UID 0... ░░ Subject: A start job for unit user@0.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit user@0.service has begun execution. ░░ ░░ The job identifier is 631. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0) May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Queued start job for default target Main User Target. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Created slice User Application Slice. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 5. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Mark boot as successful after the user session has run 2 minutes was skipped because of an unmet condition check (ConditionUser=!@system). ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 12. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Started Daily Cleanup of User's Temporary Directories. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 11. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Reached target Paths. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 9. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Reached target Timers. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 10. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Starting D-Bus User Message Bus Socket... ░░ Subject: A start job for unit UNIT has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has begun execution. ░░ ░░ The job identifier is 4. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Starting Create User's Volatile Files and Directories... ░░ Subject: A start job for unit UNIT has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has begun execution. ░░ ░░ The job identifier is 8. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Finished Create User's Volatile Files and Directories. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 8. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Listening on D-Bus User Message Bus Socket. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 4. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Reached target Sockets. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 3. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Reached target Basic System. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 2. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Reached target Main User Target. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 1. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Startup finished in 54ms. ░░ Subject: User manager start-up is now complete ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The user manager instance for user 0 has been started. All services queued ░░ for starting have been started. Note that other services might still be starting ░░ up or be started at any later time. ░░ ░░ Startup of the manager took 54357 microseconds. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started User Manager for UID 0. ░░ Subject: A start job for unit user@0.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit user@0.service has finished successfully. ░░ ░░ The job identifier is 631. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Session 3 of User root. ░░ Subject: A start job for unit session-3.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-3.scope has finished successfully. ░░ ░░ The job identifier is 699. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Session 4 of User root. ░░ Subject: A start job for unit session-4.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-4.scope has finished successfully. ░░ ░░ The job identifier is 768. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4295]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4294]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4311]: Received disconnect from 10.31.9.54 port 34804:11: disconnected by user May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4311]: Disconnected from user root 10.31.9.54 port 34804 May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4295]: pam_unix(sshd:session): session closed for user root May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: Session 3 logged out. Waiting for processes to exit. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: session-3.scope: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit session-3.scope has successfully entered the 'dead' state. May 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: Removed session 3. ░░ Subject: Session 3 has been terminated ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A session with the ID 3 has been terminated. May 24 12:30:16 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com unknown: Running test '/Prepare-managed-node/tests/prep_managed_node' (serial number 1) with reboot count 0 and test restart count 0. (Be aware the test name is sanitized!) May 24 12:30:16 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Hostname Service... ░░ Subject: A start job for unit systemd-hostnamed.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-hostnamed.service has begun execution. ░░ ░░ The job identifier is 838. May 24 12:30:16 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Hostname Service. ░░ Subject: A start job for unit systemd-hostnamed.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit systemd-hostnamed.service has finished successfully. ░░ ░░ The job identifier is 838. May 24 12:30:16 managed-node2 systemd-hostnamed[6146]: Hostname set to (static) May 24 12:30:16 managed-node2 NetworkManager[637]: [1748104216.7782] hostname: static hostname changed from "ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com" to "managed-node2" May 24 12:30:16 managed-node2 systemd[1]: Starting Network Manager Script Dispatcher Service... ░░ Subject: A start job for unit NetworkManager-dispatcher.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit NetworkManager-dispatcher.service has begun execution. ░░ ░░ The job identifier is 904. May 24 12:30:16 managed-node2 systemd[1]: Started Network Manager Script Dispatcher Service. ░░ Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit NetworkManager-dispatcher.service has finished successfully. ░░ ░░ The job identifier is 904. May 24 12:30:17 managed-node2 unknown: Leaving test '/Prepare-managed-node/tests/prep_managed_node' (serial number 1). (Be aware the test name is sanitized!) May 24 12:30:26 managed-node2 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state. May 24 12:30:46 managed-node2 systemd[1]: systemd-hostnamed.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-hostnamed.service has successfully entered the 'dead' state. May 24 12:31:11 managed-node2 sshd[6814]: Accepted publickey for root from 10.31.43.10 port 51940 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE May 24 12:31:11 managed-node2 systemd-logind[601]: New session 6 of user root. ░░ Subject: A new session 6 has been created for user root ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A new session with the ID 6 has been created for the user root. ░░ ░░ The leading process of the session is 6814. May 24 12:31:11 managed-node2 systemd[1]: Started Session 6 of User root. ░░ Subject: A start job for unit session-6.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-6.scope has finished successfully. ░░ ░░ The job identifier is 970. May 24 12:31:11 managed-node2 sshd[6814]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) May 24 12:31:13 managed-node2 python3.9[6991]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d May 24 12:31:14 managed-node2 python3.9[7166]: ansible-tempfile Invoked with state=directory prefix=lsr_ suffix=_podman path=None May 24 12:31:14 managed-node2 python3.9[7315]: ansible-file Invoked with path=/tmp/lsr_jq0x6_jl_podman mode=0777 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 state=None _original_basename=None _diff_peek=None src=None modification_time=None access_time=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None May 24 12:31:15 managed-node2 python3.9[7464]: ansible-user Invoked with name=podman_basic_user uid=3001 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-node2 update_password=always 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 May 24 12:31:15 managed-node2 useradd[7466]: new group: name=podman_basic_user, GID=3001 May 24 12:31:15 managed-node2 useradd[7466]: new user: name=podman_basic_user, UID=3001, GID=3001, home=/home/podman_basic_user, shell=/bin/bash, from=/dev/pts/0 May 24 12:31:16 managed-node2 python3.9[7621]: ansible-file Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd1 state=directory mode=0755 owner=podman_basic_user 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 May 24 12:31:16 managed-node2 python3.9[7770]: ansible-file Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd2 state=directory mode=0755 owner=root 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 May 24 12:31:17 managed-node2 python3.9[7919]: ansible-file Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd3 state=directory mode=0755 owner=root 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 May 24 12:31:17 managed-node2 python3.9[8068]: ansible-ansible.legacy.stat Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd1/index.txt follow=False get_checksum=True get_size=False checksum_algorithm=sha1 get_mime=True get_attributes=True May 24 12:31:17 managed-node2 python3.9[8188]: ansible-ansible.legacy.copy Invoked with dest=/tmp/lsr_jq0x6_jl_podman/httpd1/index.txt mode=0644 owner=podman_basic_user src=/root/.ansible/tmp/ansible-tmp-1748104277.176319-7649-125572707805660/.source.txt _original_basename=.ggm_5xw4 follow=False checksum=40bd001563085fc35165329ea1ff5c5ecbdbbeef 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 May 24 12:31:18 managed-node2 python3.9[8337]: ansible-ansible.legacy.stat Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd2/index.txt follow=False get_checksum=True get_size=False checksum_algorithm=sha1 get_mime=True get_attributes=True May 24 12:31:18 managed-node2 python3.9[8457]: ansible-ansible.legacy.copy Invoked with dest=/tmp/lsr_jq0x6_jl_podman/httpd2/index.txt mode=0644 owner=root src=/root/.ansible/tmp/ansible-tmp-1748104277.8073432-7649-214398782870186/.source.txt _original_basename=.ljv9qyi5 follow=False checksum=40bd001563085fc35165329ea1ff5c5ecbdbbeef 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 May 24 12:31:18 managed-node2 python3.9[8606]: ansible-ansible.legacy.stat Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd3/index.txt follow=False get_checksum=True get_size=False checksum_algorithm=sha1 get_mime=True get_attributes=True May 24 12:31:18 managed-node2 python3.9[8726]: ansible-ansible.legacy.copy Invoked with dest=/tmp/lsr_jq0x6_jl_podman/httpd3/index.txt mode=0644 owner=root src=/root/.ansible/tmp/ansible-tmp-1748104278.4192455-7649-81299099379633/.source.txt _original_basename=.th0c4dzz follow=False checksum=40bd001563085fc35165329ea1ff5c5ecbdbbeef 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 May 24 12:31:19 managed-node2 python3.9[8875]: ansible-stat Invoked with path=/run/ostree-booted follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 May 24 12:31:19 managed-node2 python3.9[9024]: ansible-stat Invoked with path=/sbin/transactional-update follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 May 24 12:31:21 managed-node2 sudo[9322]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/sh -c 'echo BECOME-SUCCESS-ugssexxltsvsexmisrhtbwqbqyvehuqq ; /usr/bin/python3.9 /root/.ansible/tmp/ansible-tmp-1748104281.1114032-7844-48172268806028/AnsiballZ_dnf.py' May 24 12:31:21 managed-node2 sudo[9322]: pam_unix(sudo:session): session opened for user root(uid=0) by root(uid=0) May 24 12:31:21 managed-node2 python3.9[9324]: ansible-ansible.legacy.dnf Invoked with name=['podman', 'shadow-utils-subid'] state=present allow_downgrade=False allowerasing=False autoremove=False bugfix=False cacheonly=False disable_gpg_check=False disable_plugin=[] disablerepo=[] download_only=False enable_plugin=[] enablerepo=[] exclude=[] installroot=/ install_repoquery=True install_weak_deps=True security=False skip_broken=False update_cache=False update_only=False validate_certs=True sslverify=True lock_timeout=30 use_backend=auto best=None conf_file=None disable_excludes=None download_dir=None list=None nobest=None releasever=None May 24 12:31:25 managed-node2 sudo[9322]: pam_unix(sudo:session): session closed for user root May 24 12:31:27 managed-node2 sudo[9655]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/sh -c 'echo BECOME-SUCCESS-bbdaiqmbavtalwmnfrvwodvaazdobaqp ; /usr/bin/python3.9 /root/.ansible/tmp/ansible-tmp-1748104287.2291317-7989-229816896276788/AnsiballZ_dnf.py' May 24 12:31:27 managed-node2 sudo[9655]: pam_unix(sudo:session): session opened for user root(uid=0) by root(uid=0) May 24 12:31:27 managed-node2 python3.9[9657]: ansible-ansible.legacy.dnf Invoked with name=['podman', 'shadow-utils-subid'] state=present allow_downgrade=False allowerasing=False autoremove=False bugfix=False cacheonly=False disable_gpg_check=False disable_plugin=[] disablerepo=[] download_only=False enable_plugin=[] enablerepo=[] exclude=[] installroot=/ install_repoquery=True install_weak_deps=True security=False skip_broken=False update_cache=False update_only=False validate_certs=True sslverify=True lock_timeout=30 use_backend=auto best=None conf_file=None disable_excludes=None download_dir=None list=None nobest=None releasever=None May 24 12:31:31 managed-node2 sudo[9655]: pam_unix(sudo:session): session closed for user root May 24 12:31:31 managed-node2 python3.9[9834]: 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 [Clean up storage.conf] *************************************************** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:456 Saturday 24 May 2025 12:31:31 -0400 (0:00:00.549) 0:00:20.313 ********** ok: [managed-node2] => { "changed": false, "path": "/etc/containers/storage.conf", "state": "absent" } TASK [Clean up host directories] *********************************************** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:463 Saturday 24 May 2025 12:31:32 -0400 (0:00:00.357) 0:00:20.671 ********** changed: [managed-node2] => { "changed": true, "path": "/tmp/lsr_jq0x6_jl_podman", "state": "absent" } TASK [Remove kube file src] **************************************************** task path: /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:470 Saturday 24 May 2025 12:31:32 -0400 (0:00:00.381) 0:00:21.053 ********** changed: [managed-node2 -> localhost] => { "changed": true, "path": "/tmp/lsr_podman_86knjsnc.yml", "state": "absent" } PLAY RECAP ********************************************************************* managed-node2 : ok=25 changed=9 unreachable=0 failed=1 skipped=11 rescued=3 ignored=0 SYSTEM ROLES ERRORS BEGIN v1 [ { "ansible_version": "2.17.12", "end_time": "2025-05-24T16:31:25.832237+00:00Z", "host": "managed-node2", "message": "Failed to download metadata for repo 'highavailability': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried", "rc": 1, "start_time": "2025-05-24T16:31:21.029751+00:00Z", "task_name": "Ensure required packages are installed", "task_path": "/tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:14" }, { "ansible_version": "2.17.12", "end_time": "2025-05-24T16:31:25.867181+00:00Z", "host": "managed-node2", "message": "The conditional check 'not __podman_image_updated.results[0] is changed' failed. The error was: The 'changed' test expects a dictionary", "start_time": "2025-05-24T16:31:25.849935+00:00Z", "task_name": "Verify image not pulled", "task_path": "/tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:262" }, { "ansible_version": "2.17.12", "end_time": "2025-05-24T16:31:31.097515+00:00Z", "host": "managed-node2", "message": "Failed to download metadata for repo 'highavailability': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried", "rc": 1, "start_time": "2025-05-24T16:31:27.157129+00:00Z", "task_name": "Ensure required packages are installed", "task_path": "/tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:14" }, { "ansible_version": "2.17.12", "delta": "0:00:00.036026", "end_time": "2025-05-24 12:31:31.567478", "host": "managed-node2", "message": "", "rc": 0, "start_time": "2025-05-24 12:31:31.531452", "stdout": "May 24 12:27:49 localhost kernel: Cannot get hvm parameter CONSOLE_EVTCHN (18): -22!\nMay 24 12:27:49 localhost kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled\nMay 24 12:27:49 localhost kernel: 00:06: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A\nMay 24 12:27:49 localhost kernel: Non-volatile memory driver v1.3\nMay 24 12:27:49 localhost kernel: rdac: device handler registered\nMay 24 12:27:49 localhost kernel: hp_sw: device handler registered\nMay 24 12:27:49 localhost kernel: emc: device handler registered\nMay 24 12:27:49 localhost kernel: alua: device handler registered\nMay 24 12:27:49 localhost kernel: usbcore: registered new interface driver usbserial_generic\nMay 24 12:27:49 localhost kernel: usbserial: USB Serial support registered for generic\nMay 24 12:27:49 localhost kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12\nMay 24 12:27:49 localhost kernel: i8042: Warning: Keylock active\nMay 24 12:27:49 localhost kernel: serio: i8042 KBD port at 0x60,0x64 irq 1\nMay 24 12:27:49 localhost kernel: serio: i8042 AUX port at 0x60,0x64 irq 12\nMay 24 12:27:49 localhost kernel: mousedev: PS/2 mouse device common for all mice\nMay 24 12:27:49 localhost kernel: rtc_cmos 00:02: registered as rtc0\nMay 24 12:27:49 localhost kernel: rtc_cmos 00:02: setting system clock to 2025-05-24T16:27:48 UTC (1748104068)\nMay 24 12:27:49 localhost kernel: rtc_cmos 00:02: alarms up to one day, 114 bytes nvram, hpet irqs\nMay 24 12:27:49 localhost kernel: intel_pstate: CPU model not supported\nMay 24 12:27:49 localhost kernel: hid: raw HID events driver (C) Jiri Kosina\nMay 24 12:27:49 localhost kernel: usbcore: registered new interface driver usbhid\nMay 24 12:27:49 localhost kernel: usbhid: USB HID core driver\nMay 24 12:27:49 localhost kernel: drop_monitor: Initializing network drop monitor service\nMay 24 12:27:49 localhost kernel: Initializing XFRM netlink socket\nMay 24 12:27:49 localhost kernel: NET: Registered PF_INET6 protocol family\nMay 24 12:27:49 localhost kernel: Freeing initrd memory: 37068K\nMay 24 12:27:49 localhost kernel: Segment Routing with IPv6\nMay 24 12:27:49 localhost kernel: NET: Registered PF_PACKET protocol family\nMay 24 12:27:49 localhost kernel: mpls_gso: MPLS GSO support\nMay 24 12:27:49 localhost kernel: IPI shorthand broadcast: enabled\nMay 24 12:27:49 localhost kernel: AVX2 version of gcm_enc/dec engaged.\nMay 24 12:27:49 localhost kernel: AES CTR mode by8 optimization enabled\nMay 24 12:27:49 localhost kernel: sched_clock: Marking stable (858125011, 248380944)->(1201973053, -95467098)\nMay 24 12:27:49 localhost kernel: registered taskstats version 1\nMay 24 12:27:49 localhost kernel: Loading compiled-in X.509 certificates\nMay 24 12:27:49 localhost kernel: Loaded X.509 cert 'The CentOS Project: CentOS Stream kernel signing key: f8c7f7d0e4c329fac8112926b4bb7228168649ea'\nMay 24 12:27:49 localhost kernel: Loaded X.509 cert 'Red Hat Enterprise Linux Driver Update Program (key 3): bf57f3e87362bc7229d9f465321773dfd1f77a80'\nMay 24 12:27:49 localhost kernel: Loaded X.509 cert 'Red Hat Enterprise Linux kpatch signing key: 4d38fd864ebe18c5f0b72e3852e2014c3a676fc8'\nMay 24 12:27:49 localhost kernel: Loaded X.509 cert 'RH-IMA-CA: Red Hat IMA CA: fb31825dd0e073685b264e3038963673f753959a'\nMay 24 12:27:49 localhost kernel: Loaded X.509 cert 'Nvidia GPU OOT signing 001: 55e1cef88193e60419f0b0ec379c49f77545acf0'\nMay 24 12:27:49 localhost kernel: Demotion targets for Node 0: null\nMay 24 12:27:49 localhost kernel: page_owner is disabled\nMay 24 12:27:49 localhost kernel: Key type .fscrypt registered\nMay 24 12:27:49 localhost kernel: Key type fscrypt-provisioning registered\nMay 24 12:27:49 localhost kernel: Key type big_key registered\nMay 24 12:27:49 localhost kernel: Key type encrypted registered\nMay 24 12:27:49 localhost kernel: ima: No TPM chip found, activating TPM-bypass!\nMay 24 12:27:49 localhost kernel: Loading compiled-in module X.509 certificates\nMay 24 12:27:49 localhost kernel: Loaded X.509 cert 'The CentOS Project: CentOS Stream kernel signing key: f8c7f7d0e4c329fac8112926b4bb7228168649ea'\nMay 24 12:27:49 localhost kernel: ima: Allocated hash algorithm: sha256\nMay 24 12:27:49 localhost kernel: ima: No architecture policies found\nMay 24 12:27:49 localhost kernel: evm: Initialising EVM extended attributes:\nMay 24 12:27:49 localhost kernel: evm: security.selinux\nMay 24 12:27:49 localhost kernel: evm: security.SMACK64 (disabled)\nMay 24 12:27:49 localhost kernel: evm: security.SMACK64EXEC (disabled)\nMay 24 12:27:49 localhost kernel: evm: security.SMACK64TRANSMUTE (disabled)\nMay 24 12:27:49 localhost kernel: evm: security.SMACK64MMAP (disabled)\nMay 24 12:27:49 localhost kernel: evm: security.apparmor (disabled)\nMay 24 12:27:49 localhost kernel: evm: security.ima\nMay 24 12:27:49 localhost kernel: evm: security.capability\nMay 24 12:27:49 localhost kernel: evm: HMAC attrs: 0x1\nMay 24 12:27:49 localhost kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2\nMay 24 12:27:49 localhost kernel: Running certificate verification RSA selftest\nMay 24 12:27:49 localhost kernel: Loaded X.509 cert 'Certificate verification self-testing key: f58703bb33ce1b73ee02eccdee5b8817518fe3db'\nMay 24 12:27:49 localhost kernel: Running certificate verification ECDSA selftest\nMay 24 12:27:49 localhost kernel: Loaded X.509 cert 'Certificate verification ECDSA self-testing key: 2900bcea1deb7bc8479a84a23d758efdfdd2b2d3'\nMay 24 12:27:49 localhost kernel: xenbus_probe_frontend: Device with no driver: device/vbd/768\nMay 24 12:27:49 localhost kernel: xenbus_probe_frontend: Device with no driver: device/vif/0\nMay 24 12:27:49 localhost kernel: clk: Disabling unused clocks\nMay 24 12:27:49 localhost kernel: Freeing unused decrypted memory: 2028K\nMay 24 12:27:49 localhost kernel: Freeing unused kernel image (initmem) memory: 4056K\nMay 24 12:27:49 localhost kernel: Write protecting the kernel read-only data: 30720k\nMay 24 12:27:49 localhost kernel: Freeing unused kernel image (rodata/data gap) memory: 684K\nMay 24 12:27:49 localhost kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.\nMay 24 12:27:49 localhost kernel: x86/mm: Checking user space page tables\nMay 24 12:27:49 localhost kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.\nMay 24 12:27:49 localhost kernel: Run /init as init process\nMay 24 12:27:49 localhost kernel: with arguments:\nMay 24 12:27:49 localhost kernel: /init\nMay 24 12:27:49 localhost kernel: rhgb\nMay 24 12:27:49 localhost kernel: with environment:\nMay 24 12:27:49 localhost kernel: HOME=/\nMay 24 12:27:49 localhost kernel: TERM=linux\nMay 24 12:27:49 localhost kernel: BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-5.14.0-583.el9.x86_64\nMay 24 12:27:49 localhost systemd[1]: systemd 252-53.el9 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)\nMay 24 12:27:49 localhost systemd[1]: Detected virtualization xen.\nMay 24 12:27:49 localhost systemd[1]: Detected architecture x86-64.\nMay 24 12:27:49 localhost systemd[1]: Running in initrd.\nMay 24 12:27:49 localhost systemd[1]: No hostname configured, using default hostname.\nMay 24 12:27:49 localhost systemd[1]: Hostname set to .\nMay 24 12:27:49 localhost systemd[1]: Queued start job for default target Initrd Default Target.\nMay 24 12:27:49 localhost systemd[1]: Started Dispatch Password Requests to Console Directory Watch.\nMay 24 12:27:49 localhost systemd[1]: Reached target Initrd /usr File System.\nMay 24 12:27:49 localhost systemd[1]: Reached target Local File Systems.\nMay 24 12:27:49 localhost systemd[1]: Reached target Path Units.\nMay 24 12:27:49 localhost systemd[1]: Reached target Slice Units.\nMay 24 12:27:49 localhost systemd[1]: Reached target Swaps.\nMay 24 12:27:49 localhost systemd[1]: Reached target Timer Units.\nMay 24 12:27:49 localhost systemd[1]: Listening on D-Bus System Message Bus Socket.\nMay 24 12:27:49 localhost systemd[1]: Listening on Journal Socket (/dev/log).\nMay 24 12:27:49 localhost systemd[1]: Listening on Journal Socket.\nMay 24 12:27:49 localhost systemd[1]: Listening on udev Control Socket.\nMay 24 12:27:49 localhost systemd[1]: Listening on udev Kernel Socket.\nMay 24 12:27:49 localhost systemd[1]: Reached target Socket Units.\nMay 24 12:27:49 localhost systemd[1]: Starting Create List of Static Device Nodes...\nMay 24 12:27:49 localhost systemd[1]: Starting Journal Service...\nMay 24 12:27:49 localhost systemd[1]: Load Kernel Modules was skipped because no trigger condition checks were met.\nMay 24 12:27:49 localhost systemd[1]: Starting Apply Kernel Variables...\nMay 24 12:27:49 localhost systemd[1]: Starting Create System Users...\nMay 24 12:27:49 localhost systemd-journald[231]: Journal started\n\u2591\u2591 Subject: The journal has been started\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The system journal process has started up, opened the journal\n\u2591\u2591 files for writing and is now ready to process requests.\nMay 24 12:27:49 localhost systemd-journald[231]: Runtime Journal (/run/log/journal/72dbb896bb5848cfa189670654d7ed83) is 8.0M, max 69.3M, 61.3M free.\n\u2591\u2591 Subject: Disk space used by the journal\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 Runtime Journal (/run/log/journal/72dbb896bb5848cfa189670654d7ed83) is currently using 8.0M.\n\u2591\u2591 Maximum allowed usage is set to 69.3M.\n\u2591\u2591 Leaving at least 34.6M free (of currently available 685.0M of disk space).\n\u2591\u2591 Enforced usage limit is thus 69.3M, of which 61.3M are still available.\n\u2591\u2591 \n\u2591\u2591 The limits controlling how much disk space is used by the journal may\n\u2591\u2591 be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,\n\u2591\u2591 RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in\n\u2591\u2591 /etc/systemd/journald.conf. See journald.conf(5) for details.\nMay 24 12:27:49 localhost systemd[1]: Starting Setup Virtual Console...\nMay 24 12:27:49 localhost systemd[1]: Started Journal Service.\nMay 24 12:27:49 localhost systemd[1]: Finished Create List of Static Device Nodes.\n\u2591\u2591 Subject: A start job for unit kmod-static-nodes.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit kmod-static-nodes.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 24.\nMay 24 12:27:49 localhost systemd-sysusers[233]: Creating group 'nobody' with GID 65534.\nMay 24 12:27:49 localhost systemd[1]: Finished Apply Kernel Variables.\n\u2591\u2591 Subject: A start job for unit systemd-sysctl.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-sysctl.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 8.\nMay 24 12:27:49 localhost systemd-sysusers[233]: Creating group 'users' with GID 100.\nMay 24 12:27:49 localhost systemd-sysusers[233]: Creating group 'dbus' with GID 81.\nMay 24 12:27:49 localhost systemd-sysusers[233]: Creating user 'dbus' (System Message Bus) with UID 81 and GID 81.\nMay 24 12:27:49 localhost systemd[1]: Finished Create System Users.\n\u2591\u2591 Subject: A start job for unit systemd-sysusers.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-sysusers.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 9.\nMay 24 12:27:49 localhost systemd[1]: Starting Create Static Device Nodes in /dev...\n\u2591\u2591 Subject: A start job for unit systemd-tmpfiles-setup-dev.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-tmpfiles-setup-dev.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 26.\nMay 24 12:27:49 localhost systemd[1]: Starting Create Volatile Files and Directories...\n\u2591\u2591 Subject: A start job for unit systemd-tmpfiles-setup.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-tmpfiles-setup.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 25.\nMay 24 12:27:49 localhost systemd[1]: Finished Create Static Device Nodes in /dev.\n\u2591\u2591 Subject: A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 26.\nMay 24 12:27:49 localhost systemd[1]: Finished Create Volatile Files and Directories.\n\u2591\u2591 Subject: A start job for unit systemd-tmpfiles-setup.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-tmpfiles-setup.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 25.\nMay 24 12:27:49 localhost systemd[1]: Finished Setup Virtual Console.\n\u2591\u2591 Subject: A start job for unit systemd-vconsole-setup.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-vconsole-setup.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 39.\nMay 24 12:27:49 localhost systemd[1]: dracut ask for additional cmdline parameters was skipped because no trigger condition checks were met.\n\u2591\u2591 Subject: A start job for unit dracut-cmdline-ask.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-cmdline-ask.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 38.\nMay 24 12:27:49 localhost systemd[1]: Starting dracut cmdline hook...\n\u2591\u2591 Subject: A start job for unit dracut-cmdline.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-cmdline.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 49.\nMay 24 12:27:49 localhost dracut-cmdline[248]: dracut-9 dracut-057-87.git20250311.el9\nMay 24 12:27:49 localhost dracut-cmdline[248]: Using kernel command line parameters: BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-5.14.0-583.el9.x86_64 root=UUID=5de771f1-9acb-4b75-bf56-ae0a7779ba73 ro rhgb crashkernel=2G-64G:256M,64G-:512M net.ifnames=0 console=tty0 console=ttyS0,115200n8\nMay 24 12:27:49 localhost kernel: input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4\nMay 24 12:27:49 localhost systemd[1]: Finished dracut cmdline hook.\n\u2591\u2591 Subject: A start job for unit dracut-cmdline.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-cmdline.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 49.\nMay 24 12:27:49 localhost systemd[1]: Starting dracut pre-udev hook...\n\u2591\u2591 Subject: A start job for unit dracut-pre-udev.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-pre-udev.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 52.\nMay 24 12:27:49 localhost systemd[1]: Finished dracut pre-udev hook.\n\u2591\u2591 Subject: A start job for unit dracut-pre-udev.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-pre-udev.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 52.\nMay 24 12:27:49 localhost systemd[1]: Starting Rule-based Manager for Device Events and Files...\n\u2591\u2591 Subject: A start job for unit systemd-udevd.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-udevd.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 12.\nMay 24 12:27:49 localhost systemd-udevd[329]: Using default interface naming scheme 'rhel-9.0'.\nMay 24 12:27:49 localhost systemd[1]: Started Rule-based Manager for Device Events and Files.\n\u2591\u2591 Subject: A start job for unit systemd-udevd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-udevd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 12.\nMay 24 12:27:49 localhost systemd[1]: dracut pre-trigger hook was skipped because no trigger condition checks were met.\n\u2591\u2591 Subject: A start job for unit dracut-pre-trigger.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-pre-trigger.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 54.\nMay 24 12:27:49 localhost systemd[1]: Starting Coldplug All udev Devices...\n\u2591\u2591 Subject: A start job for unit systemd-udev-trigger.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-udev-trigger.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 11.\nMay 24 12:27:49 localhost systemd[1]: Finished Coldplug All udev Devices.\n\u2591\u2591 Subject: A start job for unit systemd-udev-trigger.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-udev-trigger.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 11.\nMay 24 12:27:49 localhost systemd[1]: Reached target System Initialization.\n\u2591\u2591 Subject: A start job for unit sysinit.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sysinit.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 3.\nMay 24 12:27:49 localhost systemd[1]: Reached target Basic System.\n\u2591\u2591 Subject: A start job for unit basic.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit basic.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 2.\nMay 24 12:27:49 localhost systemd[1]: nm-initrd.service was skipped because of an unmet condition check (ConditionPathExists=/run/NetworkManager/initrd/neednet).\n\u2591\u2591 Subject: A start job for unit nm-initrd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit nm-initrd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 33.\nMay 24 12:27:49 localhost systemd[1]: Reached target Network.\n\u2591\u2591 Subject: A start job for unit network.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit network.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 35.\nMay 24 12:27:49 localhost systemd[1]: nm-wait-online-initrd.service was skipped because of an unmet condition check (ConditionPathExists=/run/NetworkManager/initrd/neednet).\n\u2591\u2591 Subject: A start job for unit nm-wait-online-initrd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit nm-wait-online-initrd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 51.\nMay 24 12:27:49 localhost systemd[1]: Starting dracut initqueue hook...\n\u2591\u2591 Subject: A start job for unit dracut-initqueue.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-initqueue.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 45.\nMay 24 12:27:49 localhost kernel: Invalid max_queues (4), will use default max: 2.\nMay 24 12:27:49 localhost kernel: blkfront: xvda: barrier or flush: disabled; persistent grants: disabled; indirect descriptors: enabled;\nMay 24 12:27:49 localhost kernel: xvda: xvda1\nMay 24 12:27:49 localhost kernel: xen_netfront: Initialising Xen virtual ethernet driver\nMay 24 12:27:49 localhost kernel: libata version 3.00 loaded.\nMay 24 12:27:49 localhost kernel: ata_piix 0000:00:01.1: version 2.13\nMay 24 12:27:49 localhost kernel: scsi host0: ata_piix\nMay 24 12:27:49 localhost kernel: scsi host1: ata_piix\nMay 24 12:27:49 localhost kernel: ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14 lpm-pol 0\nMay 24 12:27:49 localhost kernel: ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15 lpm-pol 0\nMay 24 12:27:50 localhost systemd-udevd[349]: Network interface NamePolicy= disabled on kernel command line.\nMay 24 12:27:50 localhost systemd[1]: Found device /dev/disk/by-uuid/5de771f1-9acb-4b75-bf56-ae0a7779ba73.\n\u2591\u2591 Subject: A start job for unit dev-disk-by\\x2duuid-5de771f1\\x2d9acb\\x2d4b75\\x2dbf56\\x2dae0a7779ba73.device has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dev-disk-by\\x2duuid-5de771f1\\x2d9acb\\x2d4b75\\x2dbf56\\x2dae0a7779ba73.device has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 32.\nMay 24 12:27:50 localhost systemd[1]: Reached target Initrd Root Device.\n\u2591\u2591 Subject: A start job for unit initrd-root-device.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd-root-device.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 31.\nMay 24 12:27:50 localhost systemd[1]: Finished dracut initqueue hook.\n\u2591\u2591 Subject: A start job for unit dracut-initqueue.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-initqueue.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 45.\nMay 24 12:27:50 localhost systemd[1]: Reached target Preparation for Remote File Systems.\n\u2591\u2591 Subject: A start job for unit remote-fs-pre.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit remote-fs-pre.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 46.\nMay 24 12:27:50 localhost systemd[1]: Reached target Remote File Systems.\n\u2591\u2591 Subject: A start job for unit remote-fs.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit remote-fs.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 37.\nMay 24 12:27:50 localhost systemd[1]: Starting dracut pre-mount hook...\n\u2591\u2591 Subject: A start job for unit dracut-pre-mount.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-pre-mount.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 50.\nMay 24 12:27:50 localhost systemd[1]: Finished dracut pre-mount hook.\n\u2591\u2591 Subject: A start job for unit dracut-pre-mount.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-pre-mount.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 50.\nMay 24 12:27:50 localhost systemd[1]: Starting File System Check on /dev/disk/by-uuid/5de771f1-9acb-4b75-bf56-ae0a7779ba73...\n\u2591\u2591 Subject: A start job for unit systemd-fsck-root.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-fsck-root.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 42.\nMay 24 12:27:50 localhost systemd-fsck[392]: /usr/sbin/fsck.xfs: XFS file system.\nMay 24 12:27:50 localhost systemd[1]: Finished File System Check on /dev/disk/by-uuid/5de771f1-9acb-4b75-bf56-ae0a7779ba73.\n\u2591\u2591 Subject: A start job for unit systemd-fsck-root.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-fsck-root.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 42.\nMay 24 12:27:50 localhost systemd[1]: Mounting /sysroot...\n\u2591\u2591 Subject: A start job for unit sysroot.mount has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sysroot.mount has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 41.\nMay 24 12:27:50 localhost kernel: SGI XFS with ACLs, security attributes, scrub, quota, no debug enabled\nMay 24 12:27:50 localhost kernel: XFS (xvda1): Mounting V5 Filesystem 5de771f1-9acb-4b75-bf56-ae0a7779ba73\nMay 24 12:27:51 localhost kernel: XFS (xvda1): Ending clean mount\nMay 24 12:27:51 localhost systemd[1]: Mounted /sysroot.\n\u2591\u2591 Subject: A start job for unit sysroot.mount has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sysroot.mount has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 41.\nMay 24 12:27:51 localhost systemd[1]: Reached target Initrd Root File System.\n\u2591\u2591 Subject: A start job for unit initrd-root-fs.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd-root-fs.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 40.\nMay 24 12:27:51 localhost systemd[1]: Starting Mountpoints Configured in the Real Root...\n\u2591\u2591 Subject: A start job for unit initrd-parse-etc.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd-parse-etc.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 47.\nMay 24 12:27:51 localhost systemd[1]: initrd-parse-etc.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit initrd-parse-etc.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Finished Mountpoints Configured in the Real Root.\n\u2591\u2591 Subject: A start job for unit initrd-parse-etc.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd-parse-etc.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 47.\nMay 24 12:27:51 localhost systemd[1]: Reached target Initrd File Systems.\n\u2591\u2591 Subject: A start job for unit initrd-fs.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd-fs.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 48.\nMay 24 12:27:51 localhost systemd[1]: Reached target Initrd Default Target.\n\u2591\u2591 Subject: A start job for unit initrd.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 1.\nMay 24 12:27:51 localhost systemd[1]: dracut mount hook was skipped because no trigger condition checks were met.\n\u2591\u2591 Subject: A start job for unit dracut-mount.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-mount.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 53.\nMay 24 12:27:51 localhost systemd[1]: Starting dracut pre-pivot and cleanup hook...\n\u2591\u2591 Subject: A start job for unit dracut-pre-pivot.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-pre-pivot.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 36.\nMay 24 12:27:51 localhost systemd[1]: Finished dracut pre-pivot and cleanup hook.\n\u2591\u2591 Subject: A start job for unit dracut-pre-pivot.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-pre-pivot.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 36.\nMay 24 12:27:51 localhost systemd[1]: Starting Cleaning Up and Shutting Down Daemons...\n\u2591\u2591 Subject: A start job for unit initrd-cleanup.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd-cleanup.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 57.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Network.\n\u2591\u2591 Subject: A stop job for unit network.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit network.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 110 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Timer Units.\n\u2591\u2591 Subject: A stop job for unit timers.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit timers.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 92 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: dbus.socket: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit dbus.socket has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Closed D-Bus System Message Bus Socket.\n\u2591\u2591 Subject: A stop job for unit dbus.socket has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit dbus.socket has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 93 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: dracut-pre-pivot.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit dracut-pre-pivot.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped dracut pre-pivot and cleanup hook.\n\u2591\u2591 Subject: A stop job for unit dracut-pre-pivot.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit dracut-pre-pivot.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 98 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Initrd Default Target.\n\u2591\u2591 Subject: A stop job for unit initrd.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit initrd.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 89 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Basic System.\n\u2591\u2591 Subject: A stop job for unit basic.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit basic.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 102 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Initrd Root Device.\n\u2591\u2591 Subject: A stop job for unit initrd-root-device.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit initrd-root-device.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 107 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Initrd /usr File System.\n\u2591\u2591 Subject: A stop job for unit initrd-usr-fs.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit initrd-usr-fs.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 90 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Path Units.\n\u2591\u2591 Subject: A stop job for unit paths.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit paths.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 114 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: systemd-ask-password-console.path: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-ask-password-console.path has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.\n\u2591\u2591 Subject: A stop job for unit systemd-ask-password-console.path has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit systemd-ask-password-console.path has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 91 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Remote File Systems.\n\u2591\u2591 Subject: A stop job for unit remote-fs.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit remote-fs.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 115 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Preparation for Remote File Systems.\n\u2591\u2591 Subject: A stop job for unit remote-fs-pre.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit remote-fs-pre.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 112 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Slice Units.\n\u2591\u2591 Subject: A stop job for unit slices.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit slices.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 105 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Socket Units.\n\u2591\u2591 Subject: A stop job for unit sockets.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit sockets.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 111 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target System Initialization.\n\u2591\u2591 Subject: A stop job for unit sysinit.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit sysinit.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 101 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Local File Systems.\n\u2591\u2591 Subject: A stop job for unit local-fs.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit local-fs.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 108 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopped target Swaps.\n\u2591\u2591 Subject: A stop job for unit swap.target has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit swap.target has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 106 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: dracut-pre-mount.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit dracut-pre-mount.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped dracut pre-mount hook.\n\u2591\u2591 Subject: A stop job for unit dracut-pre-mount.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit dracut-pre-mount.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 113 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: dracut-initqueue.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit dracut-initqueue.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped dracut initqueue hook.\n\u2591\u2591 Subject: A stop job for unit dracut-initqueue.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit dracut-initqueue.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 88 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: systemd-sysctl.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-sysctl.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped Apply Kernel Variables.\n\u2591\u2591 Subject: A stop job for unit systemd-sysctl.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit systemd-sysctl.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 104 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-tmpfiles-setup.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped Create Volatile Files and Directories.\n\u2591\u2591 Subject: A stop job for unit systemd-tmpfiles-setup.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit systemd-tmpfiles-setup.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 84 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: systemd-udev-trigger.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-udev-trigger.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped Coldplug All udev Devices.\n\u2591\u2591 Subject: A stop job for unit systemd-udev-trigger.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit systemd-udev-trigger.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 69 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Stopping Rule-based Manager for Device Events and Files...\n\u2591\u2591 Subject: A stop job for unit systemd-udevd.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit systemd-udevd.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 73.\nMay 24 12:27:51 localhost systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-vconsole-setup.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped Setup Virtual Console.\n\u2591\u2591 Subject: A stop job for unit systemd-vconsole-setup.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit systemd-vconsole-setup.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 99 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: run-credentials-systemd\\x2dtmpfiles\\x2dsetup.service.mount: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit run-credentials-systemd\\x2dtmpfiles\\x2dsetup.service.mount has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: run-credentials-systemd\\x2dsysctl.service.mount: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit run-credentials-systemd\\x2dsysctl.service.mount has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: systemd-udevd.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-udevd.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped Rule-based Manager for Device Events and Files.\n\u2591\u2591 Subject: A stop job for unit systemd-udevd.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit systemd-udevd.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 73 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: systemd-udevd-control.socket: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-udevd-control.socket has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Closed udev Control Socket.\n\u2591\u2591 Subject: A stop job for unit systemd-udevd-control.socket has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit systemd-udevd-control.socket has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 71 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: systemd-udevd-kernel.socket: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-udevd-kernel.socket has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Closed udev Kernel Socket.\n\u2591\u2591 Subject: A stop job for unit systemd-udevd-kernel.socket has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit systemd-udevd-kernel.socket has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 72 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: dracut-pre-udev.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit dracut-pre-udev.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped dracut pre-udev hook.\n\u2591\u2591 Subject: A stop job for unit dracut-pre-udev.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit dracut-pre-udev.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 109 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: dracut-cmdline.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit dracut-cmdline.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped dracut cmdline hook.\n\u2591\u2591 Subject: A stop job for unit dracut-cmdline.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit dracut-cmdline.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 100 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: Starting Cleanup udev Database...\n\u2591\u2591 Subject: A start job for unit initrd-udevadm-cleanup-db.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd-udevadm-cleanup-db.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 68.\nMay 24 12:27:51 localhost systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-tmpfiles-setup-dev.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped Create Static Device Nodes in /dev.\n\u2591\u2591 Subject: A stop job for unit systemd-tmpfiles-setup-dev.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit systemd-tmpfiles-setup-dev.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 85 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: kmod-static-nodes.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit kmod-static-nodes.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped Create List of Static Device Nodes.\n\u2591\u2591 Subject: A stop job for unit kmod-static-nodes.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit kmod-static-nodes.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 97 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: systemd-sysusers.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-sysusers.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Stopped Create System Users.\n\u2591\u2591 Subject: A stop job for unit systemd-sysusers.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit systemd-sysusers.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 87 and the job result is done.\nMay 24 12:27:51 localhost systemd[1]: run-credentials-systemd\\x2dtmpfiles\\x2dsetup\\x2ddev.service.mount: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit run-credentials-systemd\\x2dtmpfiles\\x2dsetup\\x2ddev.service.mount has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: run-credentials-systemd\\x2dsysusers.service.mount: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit run-credentials-systemd\\x2dsysusers.service.mount has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: initrd-cleanup.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit initrd-cleanup.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Finished Cleaning Up and Shutting Down Daemons.\n\u2591\u2591 Subject: A start job for unit initrd-cleanup.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd-cleanup.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 57.\nMay 24 12:27:51 localhost systemd[1]: initrd-udevadm-cleanup-db.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit initrd-udevadm-cleanup-db.service has successfully entered the 'dead' state.\nMay 24 12:27:51 localhost systemd[1]: Finished Cleanup udev Database.\n\u2591\u2591 Subject: A start job for unit initrd-udevadm-cleanup-db.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd-udevadm-cleanup-db.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 68.\nMay 24 12:27:51 localhost systemd[1]: Reached target Switch Root.\n\u2591\u2591 Subject: A start job for unit initrd-switch-root.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd-switch-root.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 60.\nMay 24 12:27:51 localhost systemd[1]: Starting Switch Root...\n\u2591\u2591 Subject: A start job for unit initrd-switch-root.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit initrd-switch-root.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 75.\nMay 24 12:27:51 localhost systemd[1]: Switching root.\nMay 24 12:27:51 localhost systemd-journald[231]: Journal stopped\n\u2591\u2591 Subject: The journal has been stopped\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The system journal process has shut down and closed all currently\n\u2591\u2591 active journal files.\nMay 24 12:27:56 localhost systemd-journald[231]: Received SIGTERM from PID 1 (systemd).\nMay 24 12:27:56 localhost kernel: audit: type=1404 audit(1748104073.166:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1\nMay 24 12:27:56 localhost kernel: SELinux: policy capability network_peer_controls=1\nMay 24 12:27:56 localhost kernel: SELinux: policy capability open_perms=1\nMay 24 12:27:56 localhost kernel: SELinux: policy capability extended_socket_class=1\nMay 24 12:27:56 localhost kernel: SELinux: policy capability always_check_network=0\nMay 24 12:27:56 localhost kernel: SELinux: policy capability cgroup_seclabel=1\nMay 24 12:27:56 localhost kernel: SELinux: policy capability nnp_nosuid_transition=1\nMay 24 12:27:56 localhost kernel: SELinux: policy capability genfs_seclabel_symlinks=1\nMay 24 12:27:56 localhost kernel: audit: type=1403 audit(1748104073.636:3): auid=4294967295 ses=4294967295 lsm=selinux res=1\nMay 24 12:27:56 localhost systemd[1]: Successfully loaded SELinux policy in 476.281ms.\nMay 24 12:27:56 localhost systemd[1]: Relabelled /dev, /dev/shm, /run, /sys/fs/cgroup in 19.028ms.\nMay 24 12:27:56 localhost systemd[1]: systemd 252-53.el9 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)\nMay 24 12:27:56 localhost systemd[1]: Detected virtualization xen.\nMay 24 12:27:56 localhost systemd[1]: Detected architecture x86-64.\nMay 24 12:27:56 localhost systemd[1]: Initializing machine ID from random generator.\nMay 24 12:27:56 localhost systemd[1]: Installed transient /etc/machine-id file.\nMay 24 12:27:56 localhost systemd-rc-local-generator[457]: /etc/rc.d/rc.local is not marked executable, skipping.\nMay 24 12:27:56 localhost systemd[1]: initrd-switch-root.service: Deactivated successfully.\nMay 24 12:27:56 localhost systemd[1]: Stopped Switch Root.\nMay 24 12:27:56 localhost systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.\nMay 24 12:27:56 localhost systemd[1]: Created slice Slice /system/getty.\nMay 24 12:27:56 localhost systemd[1]: Created slice Slice /system/modprobe.\nMay 24 12:27:56 localhost systemd[1]: Created slice Slice /system/serial-getty.\nMay 24 12:27:56 localhost systemd[1]: Created slice Slice /system/sshd-keygen.\nMay 24 12:27:56 localhost systemd[1]: Created slice User and Session Slice.\nMay 24 12:27:56 localhost systemd[1]: Started Dispatch Password Requests to Console Directory Watch.\nMay 24 12:27:56 localhost systemd[1]: Started Forward Password Requests to Wall Directory Watch.\nMay 24 12:27:56 localhost systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.\nMay 24 12:27:56 localhost systemd[1]: Reached target Local Encrypted Volumes.\nMay 24 12:27:56 localhost systemd[1]: Stopped target Switch Root.\nMay 24 12:27:56 localhost systemd[1]: Stopped target Initrd File Systems.\nMay 24 12:27:56 localhost systemd[1]: Stopped target Initrd Root File System.\nMay 24 12:27:56 localhost systemd[1]: Reached target Local Integrity Protected Volumes.\nMay 24 12:27:56 localhost systemd[1]: Reached target Path Units.\nMay 24 12:27:56 localhost systemd[1]: Reached target Slice Units.\nMay 24 12:27:56 localhost systemd[1]: Reached target Swaps.\nMay 24 12:27:56 localhost systemd[1]: Reached target Local Verity Protected Volumes.\nMay 24 12:27:56 localhost systemd[1]: Listening on RPCbind Server Activation Socket.\nMay 24 12:27:56 localhost systemd[1]: Reached target RPC Port Mapper.\nMay 24 12:27:56 localhost systemd[1]: Listening on Process Core Dump Socket.\nMay 24 12:27:56 localhost systemd[1]: Listening on initctl Compatibility Named Pipe.\nMay 24 12:27:56 localhost systemd[1]: Listening on udev Control Socket.\nMay 24 12:27:56 localhost systemd[1]: Listening on udev Kernel Socket.\nMay 24 12:27:56 localhost systemd[1]: Mounting Huge Pages File System...\nMay 24 12:27:56 localhost systemd[1]: Mounting POSIX Message Queue File System...\nMay 24 12:27:56 localhost systemd[1]: Mounting Kernel Debug File System...\nMay 24 12:27:56 localhost systemd[1]: Mounting Kernel Trace File System...\nMay 24 12:27:56 localhost systemd[1]: Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab).\nMay 24 12:27:56 localhost systemd[1]: Starting Create List of Static Device Nodes...\nMay 24 12:27:56 localhost systemd[1]: Starting Load Kernel Module configfs...\nMay 24 12:27:56 localhost systemd[1]: Starting Load Kernel Module drm...\nMay 24 12:27:56 localhost systemd[1]: Starting Load Kernel Module efi_pstore...\nMay 24 12:27:56 localhost systemd[1]: Starting Load Kernel Module fuse...\nMay 24 12:27:56 localhost systemd[1]: Starting Read and set NIS domainname from /etc/sysconfig/network...\nMay 24 12:27:56 localhost systemd[1]: systemd-fsck-root.service: Deactivated successfully.\nMay 24 12:27:56 localhost systemd[1]: Stopped File System Check on Root Device.\nMay 24 12:27:56 localhost systemd[1]: Stopped Journal Service.\nMay 24 12:27:56 localhost systemd[1]: Starting Journal Service...\nMay 24 12:27:56 localhost systemd[1]: Load Kernel Modules was skipped because no trigger condition checks were met.\nMay 24 12:27:56 localhost kernel: fuse: init (API version 7.37)\nMay 24 12:27:56 localhost systemd[1]: Starting Generate network units from Kernel command line...\nMay 24 12:27:56 localhost systemd[1]: TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).\nMay 24 12:27:56 localhost systemd[1]: Starting Remount Root and Kernel File Systems...\nMay 24 12:27:56 localhost systemd[1]: Repartition Root Disk was skipped because no trigger condition checks were met.\nMay 24 12:27:56 localhost systemd[1]: Starting Apply Kernel Variables...\nMay 24 12:27:56 localhost systemd[1]: Starting Coldplug All udev Devices...\nMay 24 12:27:56 localhost systemd[1]: Mounted Huge Pages File System.\nMay 24 12:27:56 localhost systemd[1]: Mounted POSIX Message Queue File System.\nMay 24 12:27:56 localhost systemd[1]: Mounted Kernel Debug File System.\nMay 24 12:27:56 localhost systemd[1]: Mounted Kernel Trace File System.\nMay 24 12:27:56 localhost systemd[1]: Finished Create List of Static Device Nodes.\nMay 24 12:27:56 localhost systemd[1]: modprobe@configfs.service: Deactivated successfully.\nMay 24 12:27:56 localhost systemd[1]: Finished Load Kernel Module configfs.\nMay 24 12:27:56 localhost kernel: ACPI: bus type drm_connector registered\nMay 24 12:27:56 localhost systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.\nMay 24 12:27:56 localhost systemd[1]: Finished Load Kernel Module efi_pstore.\nMay 24 12:27:56 localhost systemd[1]: modprobe@drm.service: Deactivated successfully.\nMay 24 12:27:56 localhost systemd[1]: Finished Load Kernel Module drm.\nMay 24 12:27:56 localhost systemd-journald[496]: Journal started\n\u2591\u2591 Subject: The journal has been started\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The system journal process has started up, opened the journal\n\u2591\u2591 files for writing and is now ready to process requests.\nMay 24 12:27:56 localhost systemd-journald[496]: Runtime Journal (/run/log/journal/724784a6a67f4a1596e8e04c82c2c1c9) is 8.0M, max 69.3M, 61.3M free.\n\u2591\u2591 Subject: Disk space used by the journal\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 Runtime Journal (/run/log/journal/724784a6a67f4a1596e8e04c82c2c1c9) is currently using 8.0M.\n\u2591\u2591 Maximum allowed usage is set to 69.3M.\n\u2591\u2591 Leaving at least 34.6M free (of currently available 676.9M of disk space).\n\u2591\u2591 Enforced usage limit is thus 69.3M, of which 61.3M are still available.\n\u2591\u2591 \n\u2591\u2591 The limits controlling how much disk space is used by the journal may\n\u2591\u2591 be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,\n\u2591\u2591 RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in\n\u2591\u2591 /etc/systemd/journald.conf. See journald.conf(5) for details.\nMay 24 12:27:56 localhost systemd[1]: Queued start job for default target Multi-User System.\nMay 24 12:27:56 localhost systemd[1]: systemd-journald.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-journald.service has successfully entered the 'dead' state.\nMay 24 12:27:56 localhost systemd[1]: Started Journal Service.\nMay 24 12:27:56 localhost systemd[1]: modprobe@fuse.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit modprobe@fuse.service has successfully entered the 'dead' state.\nMay 24 12:27:56 localhost systemd[1]: Finished Load Kernel Module fuse.\n\u2591\u2591 Subject: A start job for unit modprobe@fuse.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit modprobe@fuse.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 132.\nMay 24 12:27:56 localhost systemd[1]: Finished Read and set NIS domainname from /etc/sysconfig/network.\n\u2591\u2591 Subject: A start job for unit nis-domainname.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit nis-domainname.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 171.\nMay 24 12:27:56 localhost systemd[1]: Finished Generate network units from Kernel command line.\n\u2591\u2591 Subject: A start job for unit systemd-network-generator.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-network-generator.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 179.\nMay 24 12:27:56 localhost systemd[1]: Finished Remount Root and Kernel File Systems.\n\u2591\u2591 Subject: A start job for unit systemd-remount-fs.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-remount-fs.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 139.\nMay 24 12:27:56 localhost systemd[1]: Finished Apply Kernel Variables.\n\u2591\u2591 Subject: A start job for unit systemd-sysctl.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-sysctl.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 130.\nMay 24 12:27:56 localhost systemd[1]: Mounting FUSE Control File System...\n\u2591\u2591 Subject: A start job for unit sys-fs-fuse-connections.mount has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sys-fs-fuse-connections.mount has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 131.\nMay 24 12:27:56 localhost systemd[1]: Mounting Kernel Configuration File System...\n\u2591\u2591 Subject: A start job for unit sys-kernel-config.mount has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sys-kernel-config.mount has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 145.\nMay 24 12:27:56 localhost systemd[1]: First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).\n\u2591\u2591 Subject: A start job for unit systemd-firstboot.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-firstboot.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 135.\nMay 24 12:27:56 localhost systemd[1]: Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc).\n\u2591\u2591 Subject: A start job for unit systemd-hwdb-update.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-hwdb-update.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 163.\nMay 24 12:27:56 localhost systemd[1]: Starting Flush Journal to Persistent Storage...\n\u2591\u2591 Subject: A start job for unit systemd-journal-flush.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-journal-flush.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 168.\nMay 24 12:27:56 localhost systemd[1]: Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore).\n\u2591\u2591 Subject: A start job for unit systemd-pstore.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-pstore.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 175.\nMay 24 12:27:56 localhost systemd[1]: Starting Load/Save OS Random Seed...\n\u2591\u2591 Subject: A start job for unit systemd-random-seed.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-random-seed.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 173.\nMay 24 12:27:56 localhost systemd[1]: Create System Users was skipped because no trigger condition checks were met.\n\u2591\u2591 Subject: A start job for unit systemd-sysusers.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-sysusers.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 119.\nMay 24 12:27:56 localhost systemd[1]: Starting Create Static Device Nodes in /dev...\n\u2591\u2591 Subject: A start job for unit systemd-tmpfiles-setup-dev.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-tmpfiles-setup-dev.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 147.\nMay 24 12:27:56 localhost systemd[1]: Mounted FUSE Control File System.\n\u2591\u2591 Subject: A start job for unit sys-fs-fuse-connections.mount has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sys-fs-fuse-connections.mount has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 131.\nMay 24 12:27:56 localhost systemd[1]: Mounted Kernel Configuration File System.\n\u2591\u2591 Subject: A start job for unit sys-kernel-config.mount has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sys-kernel-config.mount has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 145.\nMay 24 12:27:56 localhost systemd-journald[496]: Runtime Journal (/run/log/journal/724784a6a67f4a1596e8e04c82c2c1c9) is 8.0M, max 69.3M, 61.3M free.\n\u2591\u2591 Subject: Disk space used by the journal\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 Runtime Journal (/run/log/journal/724784a6a67f4a1596e8e04c82c2c1c9) is currently using 8.0M.\n\u2591\u2591 Maximum allowed usage is set to 69.3M.\n\u2591\u2591 Leaving at least 34.6M free (of currently available 676.9M of disk space).\n\u2591\u2591 Enforced usage limit is thus 69.3M, of which 61.3M are still available.\n\u2591\u2591 \n\u2591\u2591 The limits controlling how much disk space is used by the journal may\n\u2591\u2591 be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,\n\u2591\u2591 RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in\n\u2591\u2591 /etc/systemd/journald.conf. See journald.conf(5) for details.\nMay 24 12:27:56 localhost systemd-journald[496]: Received client request to flush runtime journal.\nMay 24 12:27:56 localhost systemd[1]: Finished Load/Save OS Random Seed.\n\u2591\u2591 Subject: A start job for unit systemd-random-seed.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-random-seed.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 173.\nMay 24 12:27:56 localhost systemd[1]: First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).\n\u2591\u2591 Subject: A start job for unit first-boot-complete.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit first-boot-complete.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 136.\nMay 24 12:27:56 localhost systemd[1]: Finished Flush Journal to Persistent Storage.\n\u2591\u2591 Subject: A start job for unit systemd-journal-flush.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-journal-flush.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 168.\nMay 24 12:27:56 localhost systemd[1]: Finished Coldplug All udev Devices.\n\u2591\u2591 Subject: A start job for unit systemd-udev-trigger.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-udev-trigger.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 166.\nMay 24 12:27:56 localhost systemd[1]: Finished Create Static Device Nodes in /dev.\n\u2591\u2591 Subject: A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 147.\nMay 24 12:27:56 localhost systemd[1]: Reached target Preparation for Local File Systems.\n\u2591\u2591 Subject: A start job for unit local-fs-pre.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit local-fs-pre.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 140.\nMay 24 12:27:56 localhost systemd[1]: Reached target Local File Systems.\n\u2591\u2591 Subject: A start job for unit local-fs.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit local-fs.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 138.\nMay 24 12:27:56 localhost systemd[1]: Rebuild Dynamic Linker Cache was skipped because no trigger condition checks were met.\n\u2591\u2591 Subject: A start job for unit ldconfig.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit ldconfig.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 134.\nMay 24 12:27:56 localhost systemd[1]: Mark the need to relabel after reboot was skipped because of an unmet condition check (ConditionSecurity=!selinux).\n\u2591\u2591 Subject: A start job for unit selinux-autorelabel-mark.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit selinux-autorelabel-mark.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 137.\nMay 24 12:27:56 localhost systemd[1]: Set Up Additional Binary Formats was skipped because no trigger condition checks were met.\n\u2591\u2591 Subject: A start job for unit systemd-binfmt.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-binfmt.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 164.\nMay 24 12:27:56 localhost systemd[1]: Update Boot Loader Random Seed was skipped because no trigger condition checks were met.\n\u2591\u2591 Subject: A start job for unit systemd-boot-random-seed.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-boot-random-seed.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 158.\nMay 24 12:27:56 localhost systemd[1]: Starting Automatic Boot Loader Update...\n\u2591\u2591 Subject: A start job for unit systemd-boot-update.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-boot-update.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 161.\nMay 24 12:27:56 localhost systemd[1]: Starting Commit a transient machine-id on disk...\n\u2591\u2591 Subject: A start job for unit systemd-machine-id-commit.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-machine-id-commit.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 124.\nMay 24 12:27:56 localhost systemd[1]: Starting Create Volatile Files and Directories...\n\u2591\u2591 Subject: A start job for unit systemd-tmpfiles-setup.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-tmpfiles-setup.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 160.\nMay 24 12:27:56 localhost systemd[1]: Starting Rule-based Manager for Device Events and Files...\n\u2591\u2591 Subject: A start job for unit systemd-udevd.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-udevd.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 153.\nMay 24 12:27:56 localhost bootctl[509]: Couldn't find EFI system partition, skipping.\nMay 24 12:27:56 localhost systemd[1]: Finished Automatic Boot Loader Update.\n\u2591\u2591 Subject: A start job for unit systemd-boot-update.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-boot-update.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 161.\nMay 24 12:27:56 localhost systemd[1]: Finished Commit a transient machine-id on disk.\n\u2591\u2591 Subject: A start job for unit systemd-machine-id-commit.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-machine-id-commit.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 124.\nMay 24 12:27:56 localhost systemd-udevd[512]: Using default interface naming scheme 'rhel-9.0'.\nMay 24 12:27:56 localhost systemd[1]: Finished Create Volatile Files and Directories.\n\u2591\u2591 Subject: A start job for unit systemd-tmpfiles-setup.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-tmpfiles-setup.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 160.\nMay 24 12:27:56 localhost systemd[1]: Starting Security Auditing Service...\n\u2591\u2591 Subject: A start job for unit auditd.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit auditd.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 236.\nMay 24 12:27:56 localhost systemd[1]: Starting RPC Bind...\n\u2591\u2591 Subject: A start job for unit rpcbind.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit rpcbind.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 247.\nMay 24 12:27:56 localhost systemd[1]: Rebuild Journal Catalog was skipped because of an unmet condition check (ConditionNeedsUpdate=/var).\n\u2591\u2591 Subject: A start job for unit systemd-journal-catalog-update.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-journal-catalog-update.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 159.\nMay 24 12:27:56 localhost systemd[1]: Update is Completed was skipped because no trigger condition checks were met.\n\u2591\u2591 Subject: A start job for unit systemd-update-done.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-update-done.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 167.\nMay 24 12:27:57 localhost auditd[516]: No plugins found, not dispatching events\nMay 24 12:27:57 localhost systemd[1]: Started Rule-based Manager for Device Events and Files.\n\u2591\u2591 Subject: A start job for unit systemd-udevd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-udevd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 153.\nMay 24 12:27:57 localhost systemd[1]: Starting Load Kernel Module configfs...\n\u2591\u2591 Subject: A start job for unit modprobe@configfs.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit modprobe@configfs.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 265.\nMay 24 12:27:57 localhost auditd[516]: Init complete, auditd 3.1.5 listening for events (startup state enable)\nMay 24 12:27:57 localhost systemd[1]: modprobe@configfs.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit modprobe@configfs.service has successfully entered the 'dead' state.\nMay 24 12:27:57 localhost systemd[1]: Finished Load Kernel Module configfs.\n\u2591\u2591 Subject: A start job for unit modprobe@configfs.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit modprobe@configfs.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 265.\nMay 24 12:27:57 localhost systemd[1]: Condition check resulted in /dev/ttyS0 being skipped.\n\u2591\u2591 Subject: A start job for unit dev-ttyS0.device has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dev-ttyS0.device has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 208.\nMay 24 12:27:57 localhost kernel: input: PC Speaker as /devices/platform/pcspkr/input/input5\nMay 24 12:27:57 localhost augenrules[537]: /sbin/augenrules: No change\nMay 24 12:27:57 localhost systemd[1]: Started RPC Bind.\n\u2591\u2591 Subject: A start job for unit rpcbind.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit rpcbind.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 247.\nMay 24 12:27:57 localhost augenrules[561]: No rules\nMay 24 12:27:57 localhost augenrules[561]: enabled 1\nMay 24 12:27:57 localhost augenrules[561]: failure 1\nMay 24 12:27:57 localhost augenrules[561]: pid 516\nMay 24 12:27:57 localhost augenrules[561]: rate_limit 0\nMay 24 12:27:57 localhost augenrules[561]: backlog_limit 8192\nMay 24 12:27:57 localhost augenrules[561]: lost 0\nMay 24 12:27:57 localhost augenrules[561]: backlog 4\nMay 24 12:27:57 localhost augenrules[561]: backlog_wait_time 60000\nMay 24 12:27:57 localhost augenrules[561]: backlog_wait_time_actual 0\nMay 24 12:27:57 localhost augenrules[561]: enabled 1\nMay 24 12:27:57 localhost augenrules[561]: failure 1\nMay 24 12:27:57 localhost augenrules[561]: pid 516\nMay 24 12:27:57 localhost augenrules[561]: rate_limit 0\nMay 24 12:27:57 localhost augenrules[561]: backlog_limit 8192\nMay 24 12:27:57 localhost augenrules[561]: lost 0\nMay 24 12:27:57 localhost augenrules[561]: backlog 4\nMay 24 12:27:57 localhost augenrules[561]: backlog_wait_time 60000\nMay 24 12:27:57 localhost augenrules[561]: backlog_wait_time_actual 0\nMay 24 12:27:57 localhost augenrules[561]: enabled 1\nMay 24 12:27:57 localhost augenrules[561]: failure 1\nMay 24 12:27:57 localhost augenrules[561]: pid 516\nMay 24 12:27:57 localhost augenrules[561]: rate_limit 0\nMay 24 12:27:57 localhost augenrules[561]: backlog_limit 8192\nMay 24 12:27:57 localhost augenrules[561]: lost 0\nMay 24 12:27:57 localhost augenrules[561]: backlog 4\nMay 24 12:27:57 localhost augenrules[561]: backlog_wait_time 60000\nMay 24 12:27:57 localhost augenrules[561]: backlog_wait_time_actual 0\nMay 24 12:27:57 localhost systemd[1]: Started Security Auditing Service.\n\u2591\u2591 Subject: A start job for unit auditd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit auditd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 236.\nMay 24 12:27:57 localhost systemd[1]: Starting Record System Boot/Shutdown in UTMP...\n\u2591\u2591 Subject: A start job for unit systemd-update-utmp.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-update-utmp.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 245.\nMay 24 12:27:57 localhost systemd[1]: Finished Record System Boot/Shutdown in UTMP.\n\u2591\u2591 Subject: A start job for unit systemd-update-utmp.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-update-utmp.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 245.\nMay 24 12:27:57 localhost kernel: piix4_smbus 0000:00:01.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr\nMay 24 12:27:57 localhost systemd-udevd[532]: Network interface NamePolicy= disabled on kernel command line.\nMay 24 12:27:57 localhost kernel: RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 655360 ms ovfl timer\nMay 24 12:27:57 localhost kernel: cirrus 0000:00:02.0: vgaarb: deactivate vga console\nMay 24 12:27:57 localhost kernel: Console: switching to colour dummy device 80x25\nMay 24 12:27:57 localhost kernel: [drm] Initialized cirrus 2.0.0 for 0000:00:02.0 on minor 0\nMay 24 12:27:57 localhost kernel: fbcon: cirrusdrmfb (fb0) is primary device\nMay 24 12:27:57 localhost kernel: Console: switching to colour frame buffer device 128x48\nMay 24 12:27:57 localhost kernel: cirrus 0000:00:02.0: [drm] fb0: cirrusdrmfb frame buffer device\nMay 24 12:27:57 localhost systemd[1]: etc-machine\\x2did.mount: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit etc-machine\\x2did.mount has successfully entered the 'dead' state.\nMay 24 12:27:57 localhost systemd[1]: Reached target System Initialization.\n\u2591\u2591 Subject: A start job for unit sysinit.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sysinit.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 118.\nMay 24 12:27:57 localhost systemd[1]: Started dnf makecache --timer.\n\u2591\u2591 Subject: A start job for unit dnf-makecache.timer has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dnf-makecache.timer has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 184.\nMay 24 12:27:57 localhost systemd[1]: Started Daily rotation of log files.\n\u2591\u2591 Subject: A start job for unit logrotate.timer has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit logrotate.timer has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 183.\nMay 24 12:27:57 localhost systemd[1]: Started Daily Cleanup of Temporary Directories.\n\u2591\u2591 Subject: A start job for unit systemd-tmpfiles-clean.timer has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-tmpfiles-clean.timer has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 191.\nMay 24 12:27:57 localhost systemd[1]: Reached target Timer Units.\n\u2591\u2591 Subject: A start job for unit timers.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit timers.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 182.\nMay 24 12:27:57 localhost systemd[1]: Listening on D-Bus System Message Bus Socket.\n\u2591\u2591 Subject: A start job for unit dbus.socket has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dbus.socket has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 188.\nMay 24 12:27:57 localhost systemd[1]: Listening on SSSD Kerberos Cache Manager responder socket.\n\u2591\u2591 Subject: A start job for unit sssd-kcm.socket has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sssd-kcm.socket has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 198.\nMay 24 12:27:57 localhost systemd[1]: Reached target Socket Units.\n\u2591\u2591 Subject: A start job for unit sockets.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sockets.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 194.\nMay 24 12:27:57 localhost systemd[1]: Mounting RPC Pipe File System...\n\u2591\u2591 Subject: A start job for unit var-lib-nfs-rpc_pipefs.mount has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit var-lib-nfs-rpc_pipefs.mount has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 219.\nMay 24 12:27:57 localhost systemd[1]: Starting D-Bus System Message Bus...\n\u2591\u2591 Subject: A start job for unit dbus-broker.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dbus-broker.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 189.\nMay 24 12:27:57 localhost systemd[1]: TPM2 PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).\n\u2591\u2591 Subject: A start job for unit systemd-pcrphase-sysinit.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-pcrphase-sysinit.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 170.\nMay 24 12:27:57 localhost kernel: RPC: Registered named UNIX socket transport module.\nMay 24 12:27:57 localhost kernel: RPC: Registered udp transport module.\nMay 24 12:27:57 localhost kernel: RPC: Registered tcp transport module.\nMay 24 12:27:57 localhost kernel: RPC: Registered tcp-with-tls transport module.\nMay 24 12:27:57 localhost kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.\nMay 24 12:27:57 localhost systemd[1]: Mounted RPC Pipe File System.\n\u2591\u2591 Subject: A start job for unit var-lib-nfs-rpc_pipefs.mount has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit var-lib-nfs-rpc_pipefs.mount has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 219.\nMay 24 12:27:57 localhost systemd[1]: Reached target rpc_pipefs.target.\n\u2591\u2591 Subject: A start job for unit rpc_pipefs.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit rpc_pipefs.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 218.\nMay 24 12:27:57 localhost systemd[1]: Started D-Bus System Message Bus.\n\u2591\u2591 Subject: A start job for unit dbus-broker.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dbus-broker.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 189.\nMay 24 12:27:57 localhost systemd[1]: Reached target Basic System.\n\u2591\u2591 Subject: A start job for unit basic.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit basic.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 117.\nMay 24 12:27:57 localhost dbus-broker-lau[592]: Ready\nMay 24 12:27:57 localhost systemd[1]: Starting NTP client/server...\n\u2591\u2591 Subject: A start job for unit chronyd.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit chronyd.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 221.\nMay 24 12:27:57 localhost systemd[1]: Starting Cloud-init: Local Stage (pre-network)...\n\u2591\u2591 Subject: A start job for unit cloud-init-local.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit cloud-init-local.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 235.\nMay 24 12:27:57 localhost systemd[1]: Starting Restore /run/initramfs on shutdown...\n\u2591\u2591 Subject: A start job for unit dracut-shutdown.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-shutdown.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 151.\nMay 24 12:27:57 localhost systemd[1]: Started irqbalance daemon.\n\u2591\u2591 Subject: A start job for unit irqbalance.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit irqbalance.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 246.\nMay 24 12:27:57 localhost systemd[1]: Load CPU microcode update was skipped because of an unmet condition check (ConditionPathExists=/sys/devices/system/cpu/microcode/reload).\n\u2591\u2591 Subject: A start job for unit microcode.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit microcode.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 193.\nMay 24 12:27:57 localhost systemd[1]: Started Hardware RNG Entropy Gatherer Daemon.\n\u2591\u2591 Subject: A start job for unit rngd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit rngd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 243.\nMay 24 12:27:57 localhost systemd[1]: OpenSSH ecdsa Server Key Generation was skipped because of an unmet condition check (ConditionPathExists=!/run/systemd/generator.early/multi-user.target.wants/cloud-init.target).\n\u2591\u2591 Subject: A start job for unit sshd-keygen@ecdsa.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sshd-keygen@ecdsa.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 234.\nMay 24 12:27:57 localhost systemd[1]: OpenSSH ed25519 Server Key Generation was skipped because of an unmet condition check (ConditionPathExists=!/run/systemd/generator.early/multi-user.target.wants/cloud-init.target).\n\u2591\u2591 Subject: A start job for unit sshd-keygen@ed25519.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sshd-keygen@ed25519.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 233.\nMay 24 12:27:57 localhost systemd[1]: OpenSSH rsa Server Key Generation was skipped because of an unmet condition check (ConditionPathExists=!/run/systemd/generator.early/multi-user.target.wants/cloud-init.target).\n\u2591\u2591 Subject: A start job for unit sshd-keygen@rsa.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sshd-keygen@rsa.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 231.\nMay 24 12:27:57 localhost systemd[1]: Reached target sshd-keygen.target.\n\u2591\u2591 Subject: A start job for unit sshd-keygen.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sshd-keygen.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 230.\nMay 24 12:27:57 localhost systemd[1]: System Security Services Daemon was skipped because no trigger condition checks were met.\n\u2591\u2591 Subject: A start job for unit sssd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sssd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 249.\nMay 24 12:27:57 localhost systemd[1]: Reached target User and Group Name Lookups.\n\u2591\u2591 Subject: A start job for unit nss-user-lookup.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit nss-user-lookup.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 250.\nMay 24 12:27:57 localhost systemd[1]: Starting User Login Management...\n\u2591\u2591 Subject: A start job for unit systemd-logind.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-logind.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 237.\nMay 24 12:27:57 localhost systemd[1]: Starting Rotate log files...\n\u2591\u2591 Subject: A start job for unit logrotate.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit logrotate.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 269.\nMay 24 12:27:57 localhost systemd[1]: Finished Restore /run/initramfs on shutdown.\n\u2591\u2591 Subject: A start job for unit dracut-shutdown.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit dracut-shutdown.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 151.\nMay 24 12:27:57 localhost systemd-logind[601]: New seat seat0.\n\u2591\u2591 Subject: A new seat seat0 is now available\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 Documentation: sd-login(3)\n\u2591\u2591 \n\u2591\u2591 A new seat seat0 has been configured and is now available.\nMay 24 12:27:57 localhost systemd-logind[601]: Watching system buttons on /dev/input/event0 (Power Button)\nMay 24 12:27:57 localhost systemd-logind[601]: Watching system buttons on /dev/input/event1 (Sleep Button)\nMay 24 12:27:57 localhost systemd-logind[601]: Watching system buttons on /dev/input/event2 (AT Translated Set 2 keyboard)\nMay 24 12:27:57 localhost systemd[1]: Started User Login Management.\n\u2591\u2591 Subject: A start job for unit systemd-logind.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-logind.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 237.\nMay 24 12:27:58 localhost systemd[1]: logrotate.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit logrotate.service has successfully entered the 'dead' state.\nMay 24 12:27:58 localhost systemd[1]: Finished Rotate log files.\n\u2591\u2591 Subject: A start job for unit logrotate.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit logrotate.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 269.\nMay 24 12:27:58 localhost rngd[600]: Disabling 7: PKCS11 Entropy generator (pkcs11)\nMay 24 12:27:58 localhost rngd[600]: Disabling 5: NIST Network Entropy Beacon (nist)\nMay 24 12:27:58 localhost rngd[600]: Disabling 9: Qrypt quantum entropy beacon (qrypt)\nMay 24 12:27:58 localhost rngd[600]: Disabling 10: Named pipe entropy input (namedpipe)\nMay 24 12:27:58 localhost rngd[600]: Initializing available sources\nMay 24 12:27:58 localhost rngd[600]: [hwrng ]: Initialization Failed\nMay 24 12:27:58 localhost rngd[600]: [rdrand]: Enabling RDRAND rng support\nMay 24 12:27:58 localhost rngd[600]: [rdrand]: Initialized\nMay 24 12:27:58 localhost rngd[600]: [jitter]: JITTER timeout set to 5 sec\nMay 24 12:27:58 localhost chronyd[609]: chronyd version 4.6.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 +DEBUG)\nMay 24 12:27:58 localhost chronyd[609]: Loaded 0 symmetric keys\nMay 24 12:27:58 localhost chronyd[609]: Using right/UTC timezone to obtain leap second data\nMay 24 12:27:58 localhost chronyd[609]: Frequency 0.000 +/- 1000000.000 ppm read from /var/lib/chrony/drift\nMay 24 12:27:58 localhost rngd[600]: [jitter]: Initializing AES buffer\nMay 24 12:27:58 localhost chronyd[609]: Loaded seccomp filter (level 2)\nMay 24 12:27:58 localhost systemd[1]: Started NTP client/server.\n\u2591\u2591 Subject: A start job for unit chronyd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit chronyd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 221.\nMay 24 12:28:00 localhost cloud-init[614]: Cloud-init v. 24.4-5.el9 running 'init-local' at Sat, 24 May 2025 16:28:00 +0000. Up 12.42 seconds.\nMay 24 12:28:00 localhost dhclient[618]: Internet Systems Consortium DHCP Client 4.4.2b1\nMay 24 12:28:00 localhost dhclient[618]: Copyright 2004-2019 Internet Systems Consortium.\nMay 24 12:28:00 localhost dhclient[618]: All rights reserved.\nMay 24 12:28:00 localhost dhclient[618]: For info, please visit https://www.isc.org/software/dhcp/\nMay 24 12:28:00 localhost dhclient[618]: \nMay 24 12:28:00 localhost dhclient[618]: Listening on LPF/eth0/0e:e0:c8:c6:ff:03\nMay 24 12:28:00 localhost dhclient[618]: Sending on LPF/eth0/0e:e0:c8:c6:ff:03\nMay 24 12:28:00 localhost dhclient[618]: Sending on Socket/fallback\nMay 24 12:28:00 localhost dhclient[618]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0xa2c38250)\nMay 24 12:28:00 localhost dhclient[618]: DHCPOFFER of 10.31.42.9 from 10.31.40.1\nMay 24 12:28:00 localhost dhclient[618]: DHCPREQUEST for 10.31.42.9 on eth0 to 255.255.255.255 port 67 (xid=0xa2c38250)\nMay 24 12:28:00 localhost dhclient[618]: DHCPACK of 10.31.42.9 from 10.31.40.1 (xid=0xa2c38250)\nMay 24 12:28:00 localhost dhclient[618]: bound to 10.31.42.9 -- renewal in 1631 seconds.\nMay 24 12:28:01 localhost systemd[1]: Starting Hostname Service...\n\u2591\u2591 Subject: A start job for unit systemd-hostnamed.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-hostnamed.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 334.\nMay 24 12:28:01 localhost systemd[1]: Started Hostname Service.\n\u2591\u2591 Subject: A start job for unit systemd-hostnamed.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-hostnamed.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 334.\nMay 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-hostnamed[633]: Hostname set to (static)\nMay 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Cloud-init: Local Stage (pre-network).\n\u2591\u2591 Subject: A start job for unit cloud-init-local.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit cloud-init-local.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 235.\nMay 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Preparation for Network.\n\u2591\u2591 Subject: A start job for unit network-pre.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit network-pre.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 180.\nMay 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Network Manager...\n\u2591\u2591 Subject: A start job for unit NetworkManager.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit NetworkManager.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 187.\nMay 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104081.9492] NetworkManager (version 1.53.4-1.el9) is starting... (boot:4051ef22-96d3-40cd-ac57-0cd4501136da)\nMay 24 12:28:01 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104081.9496] Read config: /etc/NetworkManager/NetworkManager.conf, /run/NetworkManager/conf.d/15-carrier-timeout.conf\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0086] manager[0x561ab5ff4080]: monitoring kernel firmware directory '/lib/firmware'.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0123] hostname: hostname: using hostnamed\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0124] hostname: static hostname changed from (none) to \"ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com\"\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0136] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto)\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0696] manager[0x561ab5ff4080]: rfkill: Wi-Fi hardware radio set enabled\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0697] manager[0x561ab5ff4080]: rfkill: WWAN hardware radio set enabled\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0830] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.53.4-1.el9/libnm-device-plugin-team.so)\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0831] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0832] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0833] manager: Networking is enabled by state file\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0844] settings: Loaded settings plugin: keyfile (internal)\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Network Manager Script Dispatcher Service...\n\u2591\u2591 Subject: A start job for unit NetworkManager-dispatcher.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit NetworkManager-dispatcher.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 401.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0929] settings: Loaded settings plugin: ifcfg-rh (\"/usr/lib64/NetworkManager/1.53.4-1.el9/libnm-settings-plugin-ifcfg-rh.so\")\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.0970] Warning: the ifcfg-rh plugin is deprecated, please migrate connections to the keyfile format using \"nmcli connection migrate\"\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1000] dhcp: init: Using DHCP client 'internal'\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1005] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1025] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1054] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1096] device (lo): Activation: starting connection 'lo' (4f273044-8c71-499f-9adb-4acbd5e3d99d)\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.\n\u2591\u2591 Subject: A start job for unit systemd-rfkill.socket has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-rfkill.socket has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 467.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1168] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1177] device (eth0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Network Manager.\n\u2591\u2591 Subject: A start job for unit NetworkManager.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit NetworkManager.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 187.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Network.\n\u2591\u2591 Subject: A start job for unit network.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit network.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 190.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1255] bus-manager: acquired D-Bus service \"org.freedesktop.NetworkManager\"\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1298] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1305] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1310] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1315] device (eth0): carrier: link connected\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1319] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1345] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1359] policy: auto-activating connection 'System eth0' (5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03)\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1380] device (eth0): Activation: starting connection 'System eth0' (5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03)\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1383] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1389] manager: NetworkManager state is now CONNECTING\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1393] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1401] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1406] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Network Manager Wait Online...\n\u2591\u2591 Subject: A start job for unit NetworkManager-wait-online.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit NetworkManager-wait-online.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 186.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1449] dhcp4 (eth0): state changed new lease, address=10.31.42.9\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting GSSAPI Proxy Daemon...\n\u2591\u2591 Subject: A start job for unit gssproxy.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit gssproxy.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 216.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1486] policy: set 'System eth0' (eth0) as default for IPv4 routing and DNS\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.1559] device (eth0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Network Manager Script Dispatcher Service.\n\u2591\u2591 Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit NetworkManager-dispatcher.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 401.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2167] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2171] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2187] device (lo): Activation: successful, device activated.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2283] device (eth0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2286] device (eth0): state change: secondaries -> activated (reason 'none', managed-type: 'full')\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2295] manager: NetworkManager state is now CONNECTED_SITE\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2304] device (eth0): Activation: successful, device activated.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started GSSAPI Proxy Daemon.\n\u2591\u2591 Subject: A start job for unit gssproxy.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit gssproxy.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 216.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: RPC security service for NFS client and server was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab).\n\u2591\u2591 Subject: A start job for unit rpc-gssd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit rpc-gssd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 217.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target NFS client services.\n\u2591\u2591 Subject: A start job for unit nfs-client.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit nfs-client.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 212.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Preparation for Remote File Systems.\n\u2591\u2591 Subject: A start job for unit remote-fs-pre.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit remote-fs-pre.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 213.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Remote File Systems.\n\u2591\u2591 Subject: A start job for unit remote-fs.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit remote-fs.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 211.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: TPM2 PCR Barrier (User) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).\n\u2591\u2591 Subject: A start job for unit systemd-pcrphase.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-pcrphase.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 149.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2404] manager: NetworkManager state is now CONNECTED_GLOBAL\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com NetworkManager[637]: [1748104082.2410] manager: startup complete\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Network Manager Wait Online.\n\u2591\u2591 Subject: A start job for unit NetworkManager-wait-online.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit NetworkManager-wait-online.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 186.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Cloud-init: Network Stage...\n\u2591\u2591 Subject: A start job for unit cloud-init.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit cloud-init.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 228.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: Added source 10.11.160.238\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: Added source 10.18.100.10\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: Added source 10.2.32.37\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: Added source 10.2.32.38\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Cloud-init v. 24.4-5.el9 running 'init' at Sat, 24 May 2025 16:28:02 +0000. Up 14.79 seconds.\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: ++++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++++\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address |\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | eth0 | True | 10.31.42.9 | 255.255.252.0 | global | 0e:e0:c8:c6:ff:03 |\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | eth0 | True | fe80::ce0:c8ff:fec6:ff03/64 | . | link | 0e:e0:c8:c6:ff:03 |\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . |\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | lo | True | ::1/128 | . | host | . |\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: ++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+------------+---------------+-----------+-------+\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+------------+---------------+-----------+-------+\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | 0 | 0.0.0.0 | 10.31.40.1 | 0.0.0.0 | eth0 | UG |\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | 1 | 10.31.40.0 | 0.0.0.0 | 255.255.252.0 | eth0 | U |\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+------------+---------------+-----------+-------+\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+---------+-----------+-------+\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | Route | Destination | Gateway | Interface | Flags |\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+---------+-----------+-------+\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | 1 | fe80::/64 | :: | eth0 | U |\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: | 3 | multicast | :: | eth0 | U |\nMay 24 12:28:02 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: ci-info: +-------+-------------+---------+-----------+-------+\nMay 24 12:28:03 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com rngd[600]: [jitter]: Unable to obtain AES key, disabling JITTER source\nMay 24 12:28:03 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com rngd[600]: [jitter]: Initialization Failed\nMay 24 12:28:03 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com rngd[600]: Process privileges have been dropped to 2:2\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Generating public/private rsa key pair.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your identification has been saved in /etc/ssh/ssh_host_rsa_key\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key fingerprint is:\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: SHA256:zbzEJxtZ81eIa8MSjZogZupURfW2VkGaXxOvfDi7aR4 root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key's randomart image is:\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +---[RSA 3072]----+\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | .o.. .o . |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . . = o + |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | = . B * + o|\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | = . . O O * +.|\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | o S & B * o|\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | o o O . = |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . o E |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | .+ |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | o+ |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +----[SHA256]-----+\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Generating public/private ecdsa key pair.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key fingerprint is:\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: SHA256:cnwNg8gO+/X6khbK89rbxSM9Dj+tVBs7zcxFswcHQY8 root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key's randomart image is:\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +---[ECDSA 256]---+\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | .+. |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . . . + |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . o . o E.+|\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | + . + +o|\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . o S . . o.o|\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . +.o o . Oo|\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | ... o+ B.+ =|\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | +.+o B.o.. |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | .==+o +o |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +----[SHA256]-----+\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Generating public/private ed25519 key pair.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your identification has been saved in /etc/ssh/ssh_host_ed25519_key\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key fingerprint is:\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: SHA256:Pr+CPxgsSWJR6Y0VoUk6hgb2RVdf3EsGHWNqFkg1I5Y root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: The key's randomart image is:\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +--[ED25519 256]--+\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: |.. .++o+...+=B++.|\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: |o.ooooo oEo.*=.|\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: |..++o+ . +o .|\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: |..o.+ . o . |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . o o S |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | o o. |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | . +o |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | o oo |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: | ..oo. |\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[729]: +----[SHA256]-----+\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Cloud-init: Network Stage.\n\u2591\u2591 Subject: A start job for unit cloud-init.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit cloud-init.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 228.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Cloud-config availability.\n\u2591\u2591 Subject: A start job for unit cloud-config.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit cloud-config.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 227.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Network is Online.\n\u2591\u2591 Subject: A start job for unit network-online.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit network-online.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 185.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Cloud-init: Config Stage...\n\u2591\u2591 Subject: A start job for unit cloud-config.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit cloud-config.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 226.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Crash recovery kernel arming...\n\u2591\u2591 Subject: A start job for unit kdump.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit kdump.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 242.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting The restraint harness....\n\u2591\u2591 Subject: A start job for unit restraintd.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit restraintd.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 210.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Notify NFS peers of a restart...\n\u2591\u2591 Subject: A start job for unit rpc-statd-notify.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit rpc-statd-notify.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 214.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting System Logging Service...\n\u2591\u2591 Subject: A start job for unit rsyslog.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit rsyslog.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 209.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting OpenSSH server daemon...\n\u2591\u2591 Subject: A start job for unit sshd.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sshd.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 229.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Permit User Sessions...\n\u2591\u2591 Subject: A start job for unit systemd-user-sessions.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-user-sessions.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 248.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sm-notify[804]: Version 2.5.4 starting\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started The restraint harness..\n\u2591\u2591 Subject: A start job for unit restraintd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit restraintd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 210.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Notify NFS peers of a restart.\n\u2591\u2591 Subject: A start job for unit rpc-statd-notify.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit rpc-statd-notify.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 214.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Permit User Sessions.\n\u2591\u2591 Subject: A start job for unit systemd-user-sessions.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-user-sessions.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 248.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Command Scheduler.\n\u2591\u2591 Subject: A start job for unit crond.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit crond.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 240.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) STARTUP (1.5.7)\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (Syslog will be used instead of sendmail.)\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 55% if used.)\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (running with inotify support)\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Getty on tty1.\n\u2591\u2591 Subject: A start job for unit getty@tty1.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit getty@tty1.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 202.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com restraintd[810]: Listening on http://localhost:8081\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Serial Getty on ttyS0.\n\u2591\u2591 Subject: A start job for unit serial-getty@ttyS0.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit serial-getty@ttyS0.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 206.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Login Prompts.\n\u2591\u2591 Subject: A start job for unit getty.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit getty.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 201.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[806]: Server listening on 0.0.0.0 port 22.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[806]: Server listening on :: port 22.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started OpenSSH server daemon.\n\u2591\u2591 Subject: A start job for unit sshd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sshd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 229.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com rsyslogd[805]: [origin software=\"rsyslogd\" swVersion=\"8.2412.0-2.el9\" x-pid=\"805\" x-info=\"https://www.rsyslog.com\"] start\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started System Logging Service.\n\u2591\u2591 Subject: A start job for unit rsyslog.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit rsyslog.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 209.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Multi-User System.\n\u2591\u2591 Subject: A start job for unit multi-user.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit multi-user.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 116.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Record Runlevel Change in UTMP...\n\u2591\u2591 Subject: A start job for unit systemd-update-utmp-runlevel.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-update-utmp-runlevel.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 244.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-update-utmp-runlevel.service has successfully entered the 'dead' state.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Record Runlevel Change in UTMP.\n\u2591\u2591 Subject: A start job for unit systemd-update-utmp-runlevel.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-update-utmp-runlevel.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 244.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com rsyslogd[805]: imjournal: journal files changed, reloading... [v8.2412.0-2.el9 try https://www.rsyslog.com/e/0 ]\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[867]: Cloud-init v. 24.4-5.el9 running 'modules:config' at Sat, 24 May 2025 16:28:04 +0000. Up 16.56 seconds.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopping OpenSSH server daemon...\n\u2591\u2591 Subject: A stop job for unit sshd.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit sshd.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 488.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[806]: Received signal 15; terminating.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: sshd.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit sshd.service has successfully entered the 'dead' state.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopped OpenSSH server daemon.\n\u2591\u2591 Subject: A stop job for unit sshd.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit sshd.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 488 and the job result is done.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting OpenSSH server daemon...\n\u2591\u2591 Subject: A start job for unit sshd.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sshd.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 488.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[883]: Server listening on 0.0.0.0 port 22.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[883]: Server listening on :: port 22.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started OpenSSH server daemon.\n\u2591\u2591 Subject: A start job for unit sshd.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit sshd.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 488.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Detected change(s) in the following file(s): /etc/fstab\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Cloud-init: Config Stage.\n\u2591\u2591 Subject: A start job for unit cloud-config.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit cloud-config.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 226.\nMay 24 12:28:04 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Cloud-init: Final Stage...\n\u2591\u2591 Subject: A start job for unit cloud-final.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit cloud-final.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 225.\nMay 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1101]: Cloud-init v. 24.4-5.el9 running 'modules:final' at Sat, 24 May 2025 16:28:05 +0000. Up 17.12 seconds.\nMay 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1103]: #############################################################\nMay 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1104]: -----BEGIN SSH HOST KEY FINGERPRINTS-----\nMay 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1106]: 256 SHA256:cnwNg8gO+/X6khbK89rbxSM9Dj+tVBs7zcxFswcHQY8 root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com (ECDSA)\nMay 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1108]: 256 SHA256:Pr+CPxgsSWJR6Y0VoUk6hgb2RVdf3EsGHWNqFkg1I5Y root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com (ED25519)\nMay 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1110]: 3072 SHA256:zbzEJxtZ81eIa8MSjZogZupURfW2VkGaXxOvfDi7aR4 root@ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com (RSA)\nMay 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1111]: -----END SSH HOST KEY FINGERPRINTS-----\nMay 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1112]: #############################################################\nMay 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com cloud-init[1101]: Cloud-init v. 24.4-5.el9 finished at Sat, 24 May 2025 16:28:05 +0000. Datasource DataSourceEc2Local. Up 17.23 seconds\nMay 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Cloud-init: Final Stage.\n\u2591\u2591 Subject: A start job for unit cloud-final.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit cloud-final.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 225.\nMay 24 12:28:05 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Reached target Cloud-init target.\n\u2591\u2591 Subject: A start job for unit cloud-init.target has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit cloud-init.target has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 224.\nMay 24 12:28:06 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com kernel: block xvda: the capability attribute has been deprecated.\nMay 24 12:28:06 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Rebuilding /boot/initramfs-5.14.0-583.el9.x86_64kdump.img\nMay 24 12:28:07 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1448]: dracut-057-87.git20250311.el9\nMay 24 12:28:07 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Executing: /usr/bin/dracut --quiet --hostonly --hostonly-cmdline --hostonly-i18n --hostonly-mode strict --hostonly-nics --mount \"/dev/disk/by-uuid/5de771f1-9acb-4b75-bf56-ae0a7779ba73 /sysroot xfs rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota\" --squash-compressor zstd --no-hostonly-default-device --add-confdir /lib/kdump/dracut.conf.d -f /boot/initramfs-5.14.0-583.el9.x86_64kdump.img 5.14.0-583.el9.x86_64\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 0 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 0 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 48 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 48 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 49 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 49 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 50 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 50 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 51 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 51 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 52 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 52 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 53 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 53 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 54 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 54 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 55 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 55 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 56 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 56 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 57 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 57 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 58 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 58 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: Cannot change IRQ 59 affinity: Operation not permitted\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com irqbalance[599]: IRQ 59 affinity is now unmanaged\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-timesyncd' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-time-wait-sync' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'dbus-daemon' will not be installed, because command 'dbus-daemon' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmand' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Module 'ifcfg' will not be installed, because it's in the list to be omitted!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Module 'plymouth' will not be installed, because it's in the list to be omitted!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: 62bluetooth: Could not find any command of '/usr/lib/bluetooth/bluetoothd /usr/libexec/bluetooth/bluetoothd'!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvmthinpool-monitor' will not be installed, because command 'lvm' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvm' will not be installed, because command 'lvm' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'pcsc' will not be installed, because command 'pcscd' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Module 'resume' will not be installed, because it's in the list to be omitted!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Module 'earlykdump' will not be installed, because it's in the list to be omitted!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: Selected source 10.2.32.38\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com chronyd[609]: System clock TAI offset set to 37 seconds\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: memstrack is not available\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-timesyncd' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-time-wait-sync' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'dbus-daemon' will not be installed, because command 'dbus-daemon' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmand' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: 62bluetooth: Could not find any command of '/usr/lib/bluetooth/bluetoothd /usr/libexec/bluetooth/bluetoothd'!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvmthinpool-monitor' will not be installed, because command 'lvm' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'lvm' will not be installed, because command 'lvm' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'pcsc' will not be installed, because command 'pcscd' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found!\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: memstrack is not available\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: systemd ***\nMay 24 12:28:08 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: fips ***\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: systemd-initrd ***\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: rngd ***\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: i18n ***\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: drm ***\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: prefixdevname ***\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: kernel-modules ***\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: kernel-modules-extra ***\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: kernel-modules-extra: configuration source \"/run/depmod.d\" does not exist\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: kernel-modules-extra: configuration source \"/lib/depmod.d\" does not exist\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: kernel-modules-extra: parsing configuration file \"/etc/depmod.d/dist.conf\"\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: kernel-modules-extra: /etc/depmod.d/dist.conf: added \"updates extra built-in weak-updates\" to the list of search directories\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: fstab-sys ***\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: rootfs-block ***\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: terminfo ***\nMay 24 12:28:09 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: udev-rules ***\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Skipping udev rule: 91-permissions.rules\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Skipping udev rule: 80-drivers-modprobe.rules\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: dracut-systemd ***\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: usrmount ***\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: base ***\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: fs-lib ***\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: kdumpbase ***\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: microcode_ctl-fw_dir_override ***\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl module: mangling fw_dir\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: reset fw_dir to \"/lib/firmware/updates /lib/firmware\"\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel\"...\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: intel: caveats check for kernel version \"5.14.0-583.el9.x86_64\" passed, adding \"/usr/share/microcode_ctl/ucode_with_caveats/intel\" to fw_dir variable\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-2d-07\"...\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration \"intel-06-2d-07\" is ignored\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-4e-03\"...\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration \"intel-06-4e-03\" is ignored\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-4f-01\"...\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration \"intel-06-4f-01\" is ignored\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-55-04\"...\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration \"intel-06-55-04\" is ignored\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-5e-03\"...\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration \"intel-06-5e-03\" is ignored\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8c-01\"...\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration \"intel-06-8c-01\" is ignored\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8e-9e-0x-0xca\"...\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration \"intel-06-8e-9e-0x-0xca\" is ignored\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8e-9e-0x-dell\"...\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: configuration \"intel-06-8e-9e-0x-dell\" is ignored\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: microcode_ctl: final fw_dir: \"/usr/share/microcode_ctl/ucode_with_caveats/intel /lib/firmware/updates /lib/firmware\"\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: openssl ***\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: shutdown ***\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including module: squash ***\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Including modules done ***\nMay 24 12:28:10 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Installing kernel module dependencies ***\nMay 24 12:28:11 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Installing kernel module dependencies done ***\nMay 24 12:28:11 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Resolving executable dependencies ***\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Resolving executable dependencies done ***\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Hardlinking files ***\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Mode: real\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Files: 449\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Linked: 2 files\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Compared: 0 xattrs\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Compared: 12 files\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Saved: 56.21 KiB\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Duration: 0.008749 seconds\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Hardlinking files done ***\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Generating early-microcode cpio image ***\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Constructing GenuineIntel.bin ***\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Constructing GenuineIntel.bin ***\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Store current command line parameters ***\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: Stored kernel commandline:\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: No dracut internal kernel commandline stored in the initramfs\nMay 24 12:28:12 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Install squash loader ***\nMay 24 12:28:13 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Squashing the files inside the initramfs ***\nMay 24 12:28:19 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Squashing the files inside the initramfs done ***\nMay 24 12:28:19 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Creating image file '/boot/initramfs-5.14.0-583.el9.x86_64kdump.img' ***\nMay 24 12:28:19 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com dracut[1450]: *** Creating initramfs image file '/boot/initramfs-5.14.0-583.el9.x86_64kdump.img' done ***\nMay 24 12:28:20 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: kexec: loaded kdump kernel\nMay 24 12:28:20 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Starting kdump: [OK]\nMay 24 12:28:20 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished Crash recovery kernel arming.\n\u2591\u2591 Subject: A start job for unit kdump.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit kdump.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 242.\nMay 24 12:28:20 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Startup finished in 1.148s (kernel) + 3.808s (initrd) + 27.564s (userspace) = 32.521s.\n\u2591\u2591 Subject: System start-up is now complete\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 All system services necessary queued for starting at boot have been\n\u2591\u2591 started. Note that this does not mean that the machine is now idle as services\n\u2591\u2591 might still be busy with completing start-up.\n\u2591\u2591 \n\u2591\u2591 Kernel start-up required 1148938 microseconds.\n\u2591\u2591 \n\u2591\u2591 Initrd start-up required 3808129 microseconds.\n\u2591\u2591 \n\u2591\u2591 Userspace start-up required 27564245 microseconds.\nMay 24 12:28:32 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: systemd-hostnamed.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-hostnamed.service has successfully entered the 'dead' state.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4245]: Accepted publickey for root from 10.30.33.24 port 56132 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Created slice User Slice of UID 0.\n\u2591\u2591 Subject: A start job for unit user-0.slice has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit user-0.slice has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 490.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting User Runtime Directory /run/user/0...\n\u2591\u2591 Subject: A start job for unit user-runtime-dir@0.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit user-runtime-dir@0.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 556.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: New session 1 of user root.\n\u2591\u2591 Subject: A new session 1 has been created for user root\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 Documentation: sd-login(3)\n\u2591\u2591 \n\u2591\u2591 A new session with the ID 1 has been created for the user root.\n\u2591\u2591 \n\u2591\u2591 The leading process of the session is 4245.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished User Runtime Directory /run/user/0.\n\u2591\u2591 Subject: A start job for unit user-runtime-dir@0.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit user-runtime-dir@0.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 556.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting User Manager for UID 0...\n\u2591\u2591 Subject: A start job for unit user@0.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit user@0.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 489.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Queued start job for default target Main User Target.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Created slice User Application Slice.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 5.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Mark boot as successful after the user session has run 2 minutes was skipped because of an unmet condition check (ConditionUser=!@system).\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 10.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Started Daily Cleanup of User's Temporary Directories.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 11.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Paths.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 8.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Timers.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 9.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Starting D-Bus User Message Bus Socket...\n\u2591\u2591 Subject: A start job for unit UNIT has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 4.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Starting Create User's Volatile Files and Directories...\n\u2591\u2591 Subject: A start job for unit UNIT has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 12.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Listening on D-Bus User Message Bus Socket.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 4.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Finished Create User's Volatile Files and Directories.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 12.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Sockets.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 3.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Basic System.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 2.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Main User Target.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 1.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Startup finished in 73ms.\n\u2591\u2591 Subject: User manager start-up is now complete\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The user manager instance for user 0 has been started. All services queued\n\u2591\u2591 for starting have been started. Note that other services might still be starting\n\u2591\u2591 up or be started at any later time.\n\u2591\u2591 \n\u2591\u2591 Startup of the manager took 73418 microseconds.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started User Manager for UID 0.\n\u2591\u2591 Subject: A start job for unit user@0.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit user@0.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 489.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Session 1 of User root.\n\u2591\u2591 Subject: A start job for unit session-1.scope has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit session-1.scope has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 557.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4245]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4258]: Received disconnect from 10.30.33.24 port 56132:11: disconnected by user\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4258]: Disconnected from user root 10.30.33.24 port 56132\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4245]: pam_unix(sshd:session): session closed for user root\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: session-1.scope: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit session-1.scope has successfully entered the 'dead' state.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: Session 1 logged out. Waiting for processes to exit.\nMay 24 12:29:49 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: Removed session 1.\n\u2591\u2591 Subject: Session 1 has been terminated\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 Documentation: sd-login(3)\n\u2591\u2591 \n\u2591\u2591 A session with the ID 1 has been terminated.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopping User Manager for UID 0...\n\u2591\u2591 Subject: A stop job for unit user@0.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit user@0.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 626.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Activating special unit Exit the Session...\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped target Main User Target.\n\u2591\u2591 Subject: A stop job for unit UNIT has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit UNIT has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 20 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped target Basic System.\n\u2591\u2591 Subject: A stop job for unit UNIT has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit UNIT has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 18 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped target Paths.\n\u2591\u2591 Subject: A stop job for unit UNIT has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit UNIT has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 23 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped target Sockets.\n\u2591\u2591 Subject: A stop job for unit UNIT has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit UNIT has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 22 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped target Timers.\n\u2591\u2591 Subject: A stop job for unit UNIT has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit UNIT has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 21 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped Daily Cleanup of User's Temporary Directories.\n\u2591\u2591 Subject: A stop job for unit UNIT has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit UNIT has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 27 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Closed D-Bus User Message Bus Socket.\n\u2591\u2591 Subject: A stop job for unit UNIT has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit UNIT has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 26 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Stopped Create User's Volatile Files and Directories.\n\u2591\u2591 Subject: A stop job for unit UNIT has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit UNIT has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 28 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Removed slice User Application Slice.\n\u2591\u2591 Subject: A stop job for unit UNIT has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit UNIT has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 29 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Shutdown.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 15.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Finished Exit the Session.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 14.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4249]: Reached target Exit the Session.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 13.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: user@0.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit user@0.service has successfully entered the 'dead' state.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopped User Manager for UID 0.\n\u2591\u2591 Subject: A stop job for unit user@0.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit user@0.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 626 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopping User Runtime Directory /run/user/0...\n\u2591\u2591 Subject: A stop job for unit user-runtime-dir@0.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit user-runtime-dir@0.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 627.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: run-user-0.mount: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit run-user-0.mount has successfully entered the 'dead' state.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: user-runtime-dir@0.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit user-runtime-dir@0.service has successfully entered the 'dead' state.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Stopped User Runtime Directory /run/user/0.\n\u2591\u2591 Subject: A stop job for unit user-runtime-dir@0.service has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit user-runtime-dir@0.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 627 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Removed slice User Slice of UID 0.\n\u2591\u2591 Subject: A stop job for unit user-0.slice has finished\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A stop job for unit user-0.slice has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 629 and the job result is done.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4295]: Accepted publickey for root from 10.31.9.54 port 34804 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4294]: Accepted publickey for root from 10.31.9.54 port 34794 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: New session 3 of user root.\n\u2591\u2591 Subject: A new session 3 has been created for user root\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 Documentation: sd-login(3)\n\u2591\u2591 \n\u2591\u2591 A new session with the ID 3 has been created for the user root.\n\u2591\u2591 \n\u2591\u2591 The leading process of the session is 4295.\nMay 24 12:29:59 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Created slice User Slice of UID 0.\n\u2591\u2591 Subject: A start job for unit user-0.slice has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit user-0.slice has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 632.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting User Runtime Directory /run/user/0...\n\u2591\u2591 Subject: A start job for unit user-runtime-dir@0.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit user-runtime-dir@0.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 698.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: New session 4 of user root.\n\u2591\u2591 Subject: A new session 4 has been created for user root\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 Documentation: sd-login(3)\n\u2591\u2591 \n\u2591\u2591 A new session with the ID 4 has been created for the user root.\n\u2591\u2591 \n\u2591\u2591 The leading process of the session is 4294.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Finished User Runtime Directory /run/user/0.\n\u2591\u2591 Subject: A start job for unit user-runtime-dir@0.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit user-runtime-dir@0.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 698.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting User Manager for UID 0...\n\u2591\u2591 Subject: A start job for unit user@0.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit user@0.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 631.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Queued start job for default target Main User Target.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Created slice User Application Slice.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 5.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Mark boot as successful after the user session has run 2 minutes was skipped because of an unmet condition check (ConditionUser=!@system).\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 12.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Started Daily Cleanup of User's Temporary Directories.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 11.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Reached target Paths.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 9.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Reached target Timers.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 10.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Starting D-Bus User Message Bus Socket...\n\u2591\u2591 Subject: A start job for unit UNIT has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 4.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Starting Create User's Volatile Files and Directories...\n\u2591\u2591 Subject: A start job for unit UNIT has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 8.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Finished Create User's Volatile Files and Directories.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 8.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Listening on D-Bus User Message Bus Socket.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 4.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Reached target Sockets.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 3.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Reached target Basic System.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 2.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Reached target Main User Target.\n\u2591\u2591 Subject: A start job for unit UNIT has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit UNIT has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 1.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[4302]: Startup finished in 54ms.\n\u2591\u2591 Subject: User manager start-up is now complete\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The user manager instance for user 0 has been started. All services queued\n\u2591\u2591 for starting have been started. Note that other services might still be starting\n\u2591\u2591 up or be started at any later time.\n\u2591\u2591 \n\u2591\u2591 Startup of the manager took 54357 microseconds.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started User Manager for UID 0.\n\u2591\u2591 Subject: A start job for unit user@0.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit user@0.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 631.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Session 3 of User root.\n\u2591\u2591 Subject: A start job for unit session-3.scope has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit session-3.scope has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 699.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Session 4 of User root.\n\u2591\u2591 Subject: A start job for unit session-4.scope has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit session-4.scope has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 768.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4295]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4294]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4311]: Received disconnect from 10.31.9.54 port 34804:11: disconnected by user\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4311]: Disconnected from user root 10.31.9.54 port 34804\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com sshd[4295]: pam_unix(sshd:session): session closed for user root\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: Session 3 logged out. Waiting for processes to exit.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: session-3.scope: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit session-3.scope has successfully entered the 'dead' state.\nMay 24 12:30:00 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd-logind[601]: Removed session 3.\n\u2591\u2591 Subject: Session 3 has been terminated\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 Documentation: sd-login(3)\n\u2591\u2591 \n\u2591\u2591 A session with the ID 3 has been terminated.\nMay 24 12:30:16 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com unknown: Running test '/Prepare-managed-node/tests/prep_managed_node' (serial number 1) with reboot count 0 and test restart count 0. (Be aware the test name is sanitized!)\nMay 24 12:30:16 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Starting Hostname Service...\n\u2591\u2591 Subject: A start job for unit systemd-hostnamed.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-hostnamed.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 838.\nMay 24 12:30:16 ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com systemd[1]: Started Hostname Service.\n\u2591\u2591 Subject: A start job for unit systemd-hostnamed.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit systemd-hostnamed.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 838.\nMay 24 12:30:16 managed-node2 systemd-hostnamed[6146]: Hostname set to (static)\nMay 24 12:30:16 managed-node2 NetworkManager[637]: [1748104216.7782] hostname: static hostname changed from \"ip-10-31-42-9.testing-farm.us-east-1.aws.redhat.com\" to \"managed-node2\"\nMay 24 12:30:16 managed-node2 systemd[1]: Starting Network Manager Script Dispatcher Service...\n\u2591\u2591 Subject: A start job for unit NetworkManager-dispatcher.service has begun execution\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit NetworkManager-dispatcher.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 904.\nMay 24 12:30:16 managed-node2 systemd[1]: Started Network Manager Script Dispatcher Service.\n\u2591\u2591 Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit NetworkManager-dispatcher.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 904.\nMay 24 12:30:17 managed-node2 unknown: Leaving test '/Prepare-managed-node/tests/prep_managed_node' (serial number 1). (Be aware the test name is sanitized!)\nMay 24 12:30:26 managed-node2 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.\nMay 24 12:30:46 managed-node2 systemd[1]: systemd-hostnamed.service: Deactivated successfully.\n\u2591\u2591 Subject: Unit succeeded\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit systemd-hostnamed.service has successfully entered the 'dead' state.\nMay 24 12:31:11 managed-node2 sshd[6814]: Accepted publickey for root from 10.31.43.10 port 51940 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE\nMay 24 12:31:11 managed-node2 systemd-logind[601]: New session 6 of user root.\n\u2591\u2591 Subject: A new session 6 has been created for user root\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 Documentation: sd-login(3)\n\u2591\u2591 \n\u2591\u2591 A new session with the ID 6 has been created for the user root.\n\u2591\u2591 \n\u2591\u2591 The leading process of the session is 6814.\nMay 24 12:31:11 managed-node2 systemd[1]: Started Session 6 of User root.\n\u2591\u2591 Subject: A start job for unit session-6.scope has finished successfully\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 A start job for unit session-6.scope has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 970.\nMay 24 12:31:11 managed-node2 sshd[6814]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)\nMay 24 12:31:13 managed-node2 python3.9[6991]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d\nMay 24 12:31:14 managed-node2 python3.9[7166]: ansible-tempfile Invoked with state=directory prefix=lsr_ suffix=_podman path=None\nMay 24 12:31:14 managed-node2 python3.9[7315]: ansible-file Invoked with path=/tmp/lsr_jq0x6_jl_podman mode=0777 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 state=None _original_basename=None _diff_peek=None src=None modification_time=None access_time=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None\nMay 24 12:31:15 managed-node2 python3.9[7464]: ansible-user Invoked with name=podman_basic_user uid=3001 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-node2 update_password=always 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\nMay 24 12:31:15 managed-node2 useradd[7466]: new group: name=podman_basic_user, GID=3001\nMay 24 12:31:15 managed-node2 useradd[7466]: new user: name=podman_basic_user, UID=3001, GID=3001, home=/home/podman_basic_user, shell=/bin/bash, from=/dev/pts/0\nMay 24 12:31:16 managed-node2 python3.9[7621]: ansible-file Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd1 state=directory mode=0755 owner=podman_basic_user 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\nMay 24 12:31:16 managed-node2 python3.9[7770]: ansible-file Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd2 state=directory mode=0755 owner=root 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\nMay 24 12:31:17 managed-node2 python3.9[7919]: ansible-file Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd3 state=directory mode=0755 owner=root 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\nMay 24 12:31:17 managed-node2 python3.9[8068]: ansible-ansible.legacy.stat Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd1/index.txt follow=False get_checksum=True get_size=False checksum_algorithm=sha1 get_mime=True get_attributes=True\nMay 24 12:31:17 managed-node2 python3.9[8188]: ansible-ansible.legacy.copy Invoked with dest=/tmp/lsr_jq0x6_jl_podman/httpd1/index.txt mode=0644 owner=podman_basic_user src=/root/.ansible/tmp/ansible-tmp-1748104277.176319-7649-125572707805660/.source.txt _original_basename=.ggm_5xw4 follow=False checksum=40bd001563085fc35165329ea1ff5c5ecbdbbeef 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\nMay 24 12:31:18 managed-node2 python3.9[8337]: ansible-ansible.legacy.stat Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd2/index.txt follow=False get_checksum=True get_size=False checksum_algorithm=sha1 get_mime=True get_attributes=True\nMay 24 12:31:18 managed-node2 python3.9[8457]: ansible-ansible.legacy.copy Invoked with dest=/tmp/lsr_jq0x6_jl_podman/httpd2/index.txt mode=0644 owner=root src=/root/.ansible/tmp/ansible-tmp-1748104277.8073432-7649-214398782870186/.source.txt _original_basename=.ljv9qyi5 follow=False checksum=40bd001563085fc35165329ea1ff5c5ecbdbbeef 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\nMay 24 12:31:18 managed-node2 python3.9[8606]: ansible-ansible.legacy.stat Invoked with path=/tmp/lsr_jq0x6_jl_podman/httpd3/index.txt follow=False get_checksum=True get_size=False checksum_algorithm=sha1 get_mime=True get_attributes=True\nMay 24 12:31:18 managed-node2 python3.9[8726]: ansible-ansible.legacy.copy Invoked with dest=/tmp/lsr_jq0x6_jl_podman/httpd3/index.txt mode=0644 owner=root src=/root/.ansible/tmp/ansible-tmp-1748104278.4192455-7649-81299099379633/.source.txt _original_basename=.th0c4dzz follow=False checksum=40bd001563085fc35165329ea1ff5c5ecbdbbeef 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\nMay 24 12:31:19 managed-node2 python3.9[8875]: ansible-stat Invoked with path=/run/ostree-booted follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nMay 24 12:31:19 managed-node2 python3.9[9024]: ansible-stat Invoked with path=/sbin/transactional-update follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1\nMay 24 12:31:21 managed-node2 sudo[9322]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/sh -c 'echo BECOME-SUCCESS-ugssexxltsvsexmisrhtbwqbqyvehuqq ; /usr/bin/python3.9 /root/.ansible/tmp/ansible-tmp-1748104281.1114032-7844-48172268806028/AnsiballZ_dnf.py'\nMay 24 12:31:21 managed-node2 sudo[9322]: pam_unix(sudo:session): session opened for user root(uid=0) by root(uid=0)\nMay 24 12:31:21 managed-node2 python3.9[9324]: ansible-ansible.legacy.dnf Invoked with name=['podman', 'shadow-utils-subid'] state=present allow_downgrade=False allowerasing=False autoremove=False bugfix=False cacheonly=False disable_gpg_check=False disable_plugin=[] disablerepo=[] download_only=False enable_plugin=[] enablerepo=[] exclude=[] installroot=/ install_repoquery=True install_weak_deps=True security=False skip_broken=False update_cache=False update_only=False validate_certs=True sslverify=True lock_timeout=30 use_backend=auto best=None conf_file=None disable_excludes=None download_dir=None list=None nobest=None releasever=None\nMay 24 12:31:25 managed-node2 sudo[9322]: pam_unix(sudo:session): session closed for user root\nMay 24 12:31:27 managed-node2 sudo[9655]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/sh -c 'echo BECOME-SUCCESS-bbdaiqmbavtalwmnfrvwodvaazdobaqp ; /usr/bin/python3.9 /root/.ansible/tmp/ansible-tmp-1748104287.2291317-7989-229816896276788/AnsiballZ_dnf.py'\nMay 24 12:31:27 managed-node2 sudo[9655]: pam_unix(sudo:session): session opened for user root(uid=0) by root(uid=0)\nMay 24 12:31:27 managed-node2 python3.9[9657]: ansible-ansible.legacy.dnf Invoked with name=['podman', 'shadow-utils-subid'] state=present allow_downgrade=False allowerasing=False autoremove=False bugfix=False cacheonly=False disable_gpg_check=False disable_plugin=[] disablerepo=[] download_only=False enable_plugin=[] enablerepo=[] exclude=[] installroot=/ install_repoquery=True install_weak_deps=True security=False skip_broken=False update_cache=False update_only=False validate_certs=True sslverify=True lock_timeout=30 use_backend=auto best=None conf_file=None disable_excludes=None download_dir=None list=None nobest=None releasever=None\nMay 24 12:31:31 managed-node2 sudo[9655]: pam_unix(sudo:session): session closed for user root\nMay 24 12:31:31 managed-node2 python3.9[9834]: 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-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:447" } ] SYSTEM ROLES ERRORS END v1 TASKS RECAP ******************************************************************** Saturday 24 May 2025 12:31:32 -0400 (0:00:00.335) 0:00:21.388 ********** =============================================================================== fedora.linux_system_roles.podman : Ensure required packages are installed --- 4.82s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:14 fedora.linux_system_roles.podman : Ensure required packages are installed --- 3.97s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:14 Gathering Facts --------------------------------------------------------- 2.35s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:9 Create data files ------------------------------------------------------- 1.87s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:204 fedora.linux_system_roles.podman : Gather the package facts ------------- 1.09s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 Create host directories for data ---------------------------------------- 1.01s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:196 fedora.linux_system_roles.podman : Gather the package facts ------------- 0.77s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/main.yml:6 Write kube_file_src ----------------------------------------------------- 0.58s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:189 Create user ------------------------------------------------------------- 0.58s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:176 Dump journal ------------------------------------------------------------ 0.55s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:447 Create tmpdir for testing ----------------------------------------------- 0.47s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:143 Change tmpdir permissions ----------------------------------------------- 0.43s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:150 Clean up host directories ----------------------------------------------- 0.38s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:463 Clean up storage.conf --------------------------------------------------- 0.36s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:456 fedora.linux_system_roles.podman : Check if transactional-update exists in /sbin --- 0.35s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:23 fedora.linux_system_roles.podman : Check if system is ostree ------------ 0.34s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:11 Remove kube file src ---------------------------------------------------- 0.34s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:470 Create tempfile for kube_src -------------------------------------------- 0.20s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:181 Cleanup ----------------------------------------------------------------- 0.13s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:269 fedora.linux_system_roles.podman : Set platform/version specific variables --- 0.06s /tmp/collections-PO3/ansible_collections/fedora/linux_system_roles/roles/podman/tasks/set_vars.yml:32