ansible-playbook [core 2.17.14] config file = None configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /usr/local/lib/python3.12/site-packages/ansible ansible collection location = /tmp/collections-nT1 executable location = /usr/local/bin/ansible-playbook python version = 3.12.13 (main, Jun 1 2026, 00:00:00) [GCC 11.5.0 20240719 (Red Hat 11.5.0-14)] (/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-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml PLAY [all] ********************************************************************* TASK [Include vault variables] ************************************************* task path: /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:5 Friday 10 July 2026 17:57:09 -0400 (0:00:00.032) 0:00:00.032 *********** 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-KMx/tests/vars/vault-variables.yml" ], "changed": false } PLAY [Ensure that the role runs with default parameters] *********************** TASK [Gathering Facts] ********************************************************* task path: /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:9 Friday 10 July 2026 17:57:09 -0400 (0:00:00.021) 0:00:00.054 *********** [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-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:175 Friday 10 July 2026 17:57:11 -0400 (0:00:02.284) 0:00:02.339 *********** changed: [managed-node2] => { "changed": true, "gid": 0, "group": "root", "mode": "0700", "owner": "root", "path": "/tmp/lsr_veqsgttx_podman", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 6, "state": "directory", "uid": 0 } TASK [Change tmpdir permissions] *********************************************** task path: /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:182 Friday 10 July 2026 17:57:11 -0400 (0:00:00.476) 0:00:02.816 *********** changed: [managed-node2] => { "changed": true, "gid": 0, "group": "root", "mode": "0777", "owner": "root", "path": "/tmp/lsr_veqsgttx_podman", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 6, "state": "directory", "uid": 0 } TASK [Enable podman copr] ****************************************************** task path: /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:193 Friday 10 July 2026 17:57:12 -0400 (0:00:00.512) 0:00:03.328 *********** 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-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:198 Friday 10 July 2026 17:57:12 -0400 (0:00:00.041) 0:00:03.370 *********** 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-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:203 Friday 10 July 2026 17:57:12 -0400 (0:00:00.034) 0:00:03.405 *********** 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-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:208 Friday 10 July 2026 17:57:12 -0400 (0:00:00.034) 0:00:03.440 *********** 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-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:213 Friday 10 July 2026 17:57:13 -0400 (0:00:00.616) 0:00:04.056 *********** changed: [managed-node2 -> localhost] => { "changed": true, "gid": 0, "group": "root", "mode": "0600", "owner": "root", "path": "/tmp/lsr_podman_o4gvu_d4.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-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:221 Friday 10 July 2026 17:57:13 -0400 (0:00:00.252) 0:00:04.309 *********** fatal: [managed-node2 -> localhost]: FAILED! => {} MSG: The task includes an option with an undefined variable.. {{ __start_marker }} apiVersion: v1 kind: ConfigMap metadata: name: testfile3 data: testfile3.txt: | this is a test {{ __end_marker }} {{ __start_marker }} apiVersion: v1 kind: Pod metadata: labels: app: test io.containers.autoupdate: registry name: httpd3 spec: containers: - name: httpd3 image: {{ test_image }} command: - /bin/busybox-extras - httpd - -f - -p - 80 ports: - containerPort: 80 hostPort: 15003 volumeMounts: - mountPath: /var/www:Z name: www - mountPath: /var/httpd-create:Z name: create - mountPath: /etc/testfile3.txt:Z name: testfile3 subPath: testfile3.txt workingDir: /var/www volumes: - name: www hostPath: path: "{{ __test_tmpdir.path ~ '/httpd3' }}" - name: create hostPath: path: "{{ __test_tmpdir.path ~ '/httpd3-create' }}" - name: testfile3 configMap: name: testfile3 {{ __end_marker }} : '__start_marker' is undefined The error appears to be in '/tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml': line 221, column 11, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - name: Write kube_file_src ^ here TASK [Show kube files] ********************************************************* task path: /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:495 Friday 10 July 2026 17:57:13 -0400 (0:00:00.016) 0:00:04.326 *********** ok: [managed-node2] => { "changed": false, "cmd": "set -uxo pipefail\nexec 1>&2\nfor file in /etc/containers/ansible-kubernetes.d/*; do\n if [ -f \"$file\" ]; then\n echo \"File: $file\"\n cat \"$file\"\n fi\ndone\n", "delta": "0:00:00.003666", "end": "2026-07-10 17:57:13.804979", "rc": 0, "start": "2026-07-10 17:57:13.801313" } STDERR: + exec + for file in /etc/containers/ansible-kubernetes.d/* + '[' -f '/etc/containers/ansible-kubernetes.d/*' ']' TASK [Dump journal] ************************************************************ task path: /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:509 Friday 10 July 2026 17:57:13 -0400 (0:00:00.446) 0:00:04.772 *********** fatal: [managed-node2]: FAILED! => { "changed": false, "cmd": [ "journalctl", "-ex" ], "delta": "0:00:00.035984", "end": "2026-07-10 17:57:14.192675", "failed_when_result": true, "rc": 0, "start": "2026-07-10 17:57:14.156691" } STDOUT: Jul 10 17:54:04 localhost kernel: Non-volatile memory driver v1.3 Jul 10 17:54:04 localhost kernel: rdac: device handler registered Jul 10 17:54:04 localhost kernel: hp_sw: device handler registered Jul 10 17:54:04 localhost kernel: emc: device handler registered Jul 10 17:54:04 localhost kernel: alua: device handler registered Jul 10 17:54:04 localhost kernel: usbcore: registered new interface driver usbserial_generic Jul 10 17:54:04 localhost kernel: usbserial: USB Serial support registered for generic Jul 10 17:54:04 localhost kernel: i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12 Jul 10 17:54:04 localhost kernel: i8042: Warning: Keylock active Jul 10 17:54:04 localhost kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Jul 10 17:54:04 localhost kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Jul 10 17:54:04 localhost kernel: mousedev: PS/2 mouse device common for all mice Jul 10 17:54:04 localhost kernel: rtc_cmos 00:00: RTC can wake from S4 Jul 10 17:54:04 localhost kernel: rtc_cmos 00:00: registered as rtc0 Jul 10 17:54:04 localhost kernel: rtc_cmos 00:00: setting system clock to 2026-07-10T21:54:02 UTC (1783720442) Jul 10 17:54:04 localhost kernel: rtc_cmos 00:00: alarms up to one day, 114 bytes nvram Jul 10 17:54:04 localhost kernel: intel_pstate: P-states controlled by the platform Jul 10 17:54:04 localhost kernel: hid: raw HID events driver (C) Jiri Kosina Jul 10 17:54:04 localhost kernel: usbcore: registered new interface driver usbhid Jul 10 17:54:04 localhost kernel: usbhid: USB HID core driver Jul 10 17:54:04 localhost kernel: drop_monitor: Initializing network drop monitor service Jul 10 17:54:04 localhost kernel: Initializing XFRM netlink socket Jul 10 17:54:04 localhost kernel: NET: Registered PF_INET6 protocol family Jul 10 17:54:04 localhost kernel: Segment Routing with IPv6 Jul 10 17:54:04 localhost kernel: NET: Registered PF_PACKET protocol family Jul 10 17:54:04 localhost kernel: mpls_gso: MPLS GSO support Jul 10 17:54:04 localhost kernel: resctrl: No MBM correction factor available Jul 10 17:54:04 localhost kernel: IPI shorthand broadcast: enabled Jul 10 17:54:04 localhost kernel: AVX2 version of gcm_enc/dec engaged. Jul 10 17:54:04 localhost kernel: AES CTR mode by8 optimization enabled Jul 10 17:54:04 localhost kernel: sched_clock: Marking stable (1137482823, 924955257)->(2960230556, -897792476) Jul 10 17:54:04 localhost kernel: registered taskstats version 1 Jul 10 17:54:04 localhost kernel: Loading compiled-in X.509 certificates Jul 10 17:54:04 localhost kernel: Loaded X.509 cert 'The CentOS Project: CentOS Stream kernel signing key: 6b5ef142514248e1227595b1abbec48f1eefee95' Jul 10 17:54:04 localhost kernel: Loaded X.509 cert 'Red Hat Enterprise Linux Driver Update Program (key 3): bf57f3e87362bc7229d9f465321773dfd1f77a80' Jul 10 17:54:04 localhost kernel: Loaded X.509 cert 'Red Hat Enterprise Linux kpatch signing key: 4d38fd864ebe18c5f0b72e3852e2014c3a676fc8' Jul 10 17:54:04 localhost kernel: Loaded X.509 cert 'RH-IMA-CA: Red Hat IMA CA: fb31825dd0e073685b264e3038963673f753959a' Jul 10 17:54:04 localhost kernel: Loaded X.509 cert 'Nvidia GPU OOT signing 001: 55e1cef88193e60419f0b0ec379c49f77545acf0' Jul 10 17:54:04 localhost kernel: Loaded X.509 cert 'NVIDIA Jetson SoC OOT signing 001: 7e60d156a289e05b18f70ac4a2d8296c5c8ab797' Jul 10 17:54:04 localhost kernel: Loaded X.509 cert 'NVIDIA Bluefield DPU OOT signing 001: e251cec14b15b5d4c0e452770ca269261ea466bc' Jul 10 17:54:04 localhost kernel: Demotion targets for Node 0: null Jul 10 17:54:04 localhost kernel: page_owner is disabled Jul 10 17:54:04 localhost kernel: Key type .fscrypt registered Jul 10 17:54:04 localhost kernel: Key type fscrypt-provisioning registered Jul 10 17:54:04 localhost kernel: Key type big_key registered Jul 10 17:54:04 localhost kernel: Key type encrypted registered Jul 10 17:54:04 localhost kernel: ima: No TPM chip found, activating TPM-bypass! Jul 10 17:54:04 localhost kernel: Loading compiled-in module X.509 certificates Jul 10 17:54:04 localhost kernel: Loaded X.509 cert 'The CentOS Project: CentOS Stream kernel signing key: 6b5ef142514248e1227595b1abbec48f1eefee95' Jul 10 17:54:04 localhost kernel: ima: Allocated hash algorithm: sha256 Jul 10 17:54:04 localhost kernel: ima: No architecture policies found Jul 10 17:54:04 localhost kernel: evm: Initialising EVM extended attributes: Jul 10 17:54:04 localhost kernel: evm: security.selinux Jul 10 17:54:04 localhost kernel: evm: security.SMACK64 (disabled) Jul 10 17:54:04 localhost kernel: evm: security.SMACK64EXEC (disabled) Jul 10 17:54:04 localhost kernel: evm: security.SMACK64TRANSMUTE (disabled) Jul 10 17:54:04 localhost kernel: evm: security.SMACK64MMAP (disabled) Jul 10 17:54:04 localhost kernel: evm: security.apparmor (disabled) Jul 10 17:54:04 localhost kernel: evm: security.ima Jul 10 17:54:04 localhost kernel: evm: security.capability Jul 10 17:54:04 localhost kernel: evm: HMAC attrs: 0x1 Jul 10 17:54:04 localhost kernel: Running certificate verification RSA selftest Jul 10 17:54:04 localhost kernel: Loaded X.509 cert 'Certificate verification self-testing key: f58703bb33ce1b73ee02eccdee5b8817518fe3db' Jul 10 17:54:04 localhost kernel: Running certificate verification ECDSA selftest Jul 10 17:54:04 localhost kernel: Loaded X.509 cert 'Certificate verification ECDSA self-testing key: 2900bcea1deb7bc8479a84a23d758efdfdd2b2d3' Jul 10 17:54:04 localhost kernel: clk: Disabling unused clocks Jul 10 17:54:04 localhost kernel: Freeing unused decrypted memory: 2028K Jul 10 17:54:04 localhost kernel: Freeing unused kernel image (initmem) memory: 4224K Jul 10 17:54:04 localhost kernel: Write protecting the kernel read-only data: 30720k Jul 10 17:54:04 localhost kernel: Freeing unused kernel image (rodata/data gap) memory: 308K Jul 10 17:54:04 localhost kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2 Jul 10 17:54:04 localhost kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found. Jul 10 17:54:04 localhost kernel: x86/mm: Checking user space page tables Jul 10 17:54:04 localhost kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found. Jul 10 17:54:04 localhost kernel: Run /init as init process Jul 10 17:54:04 localhost kernel: with arguments: Jul 10 17:54:04 localhost kernel: /init Jul 10 17:54:04 localhost kernel: rhgb Jul 10 17:54:04 localhost kernel: with environment: Jul 10 17:54:04 localhost kernel: HOME=/ Jul 10 17:54:04 localhost kernel: TERM=linux Jul 10 17:54:04 localhost kernel: BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-5.14.0-721.el9.x86_64 Jul 10 17:54:04 localhost systemd[1]: systemd 252-71.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) Jul 10 17:54:04 localhost systemd[1]: Detected virtualization amazon. Jul 10 17:54:04 localhost systemd[1]: Detected architecture x86-64. Jul 10 17:54:04 localhost systemd[1]: Running in initrd. Jul 10 17:54:04 localhost systemd[1]: No hostname configured, using default hostname. Jul 10 17:54:04 localhost systemd[1]: Hostname set to . Jul 10 17:54:04 localhost systemd[1]: Queued start job for default target Initrd Default Target. Jul 10 17:54:04 localhost systemd[1]: Started Dispatch Password Requests to Console Directory Watch. Jul 10 17:54:04 localhost systemd[1]: Reached target Initrd /usr File System. Jul 10 17:54:04 localhost systemd[1]: Reached target Local File Systems. Jul 10 17:54:04 localhost systemd[1]: Reached target Path Units. Jul 10 17:54:04 localhost systemd[1]: Reached target Slice Units. Jul 10 17:54:04 localhost systemd[1]: Reached target Swaps. Jul 10 17:54:04 localhost systemd[1]: Reached target Timer Units. Jul 10 17:54:04 localhost systemd[1]: Listening on D-Bus System Message Bus Socket. Jul 10 17:54:04 localhost systemd[1]: Listening on Journal Socket (/dev/log). Jul 10 17:54:04 localhost systemd[1]: Listening on Journal Socket. Jul 10 17:54:04 localhost systemd[1]: Listening on udev Control Socket. Jul 10 17:54:04 localhost systemd[1]: Listening on udev Kernel Socket. Jul 10 17:54:04 localhost systemd[1]: Reached target Socket Units. Jul 10 17:54:04 localhost systemd[1]: Starting Create List of Static Device Nodes... Jul 10 17:54:04 localhost systemd[1]: Starting Journal Service... Jul 10 17:54:04 localhost systemd[1]: Load Kernel Modules was skipped because no trigger condition checks were met. Jul 10 17:54:04 localhost systemd[1]: Starting Apply Kernel Variables... Jul 10 17:54:04 localhost systemd[1]: Starting Create System Users... Jul 10 17:54:04 localhost systemd[1]: Starting Setup Virtual Console... Jul 10 17:54:04 localhost systemd[1]: Finished Create List of Static Device Nodes. Jul 10 17:54:04 localhost kernel: input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4 Jul 10 17:54:04 localhost systemd[1]: Finished Apply Kernel Variables. Jul 10 17:54:04 localhost systemd[1]: Finished Create System Users. Jul 10 17:54:04 localhost systemd[1]: Starting Create Static Device Nodes in /dev... Jul 10 17:54:04 localhost systemd[1]: Finished Create Static Device Nodes in /dev. Jul 10 17:54:04 localhost systemd-journald[233]: 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. Jul 10 17:54:04 localhost systemd-journald[233]: Runtime Journal (/run/log/journal/3904df565a3f4d0d8d3c70085470592d) is 8.0M, max 68.3M, 60.3M free. ░░ Subject: Disk space used by the journal ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ Runtime Journal (/run/log/journal/3904df565a3f4d0d8d3c70085470592d) is currently using 8.0M. ░░ Maximum allowed usage is set to 68.3M. ░░ Leaving at least 34.1M free (of currently available 675.0M of disk space). ░░ Enforced usage limit is thus 68.3M, of which 60.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. Jul 10 17:54:03 localhost systemd-sysusers[235]: Creating group 'nobody' with GID 65534. Jul 10 17:54:03 localhost systemd-sysusers[235]: Creating group 'users' with GID 100. Jul 10 17:54:03 localhost systemd-sysusers[235]: Creating group 'dbus' with GID 81. Jul 10 17:54:03 localhost systemd-sysusers[235]: Creating user 'dbus' (System Message Bus) with UID 81 and GID 81. Jul 10 17:54:04 localhost systemd[1]: Started Journal Service. Jul 10 17:54:04 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 24. Jul 10 17:54:04 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 24. Jul 10 17:54:04 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 49. Jul 10 17:54:04 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 48. Jul 10 17:54:04 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 33. Jul 10 17:54:04 localhost dracut-cmdline[248]: dracut-9 dracut-057-118.git20260624.el9 Jul 10 17:54:04 localhost dracut-cmdline[248]: Using kernel command line parameters: BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-5.14.0-721.el9.x86_64 root=UUID=7c0d6762-a0be-4063-a43a-c35e843399f8 ro rhgb crashkernel=1G-2G:192M,2G-64G:256M,64G-:512M net.ifnames=0 console=tty0 console=ttyS0,115200n8 Jul 10 17:54:04 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 33. Jul 10 17:54:04 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 32. Jul 10 17:54:04 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 32. Jul 10 17:54:04 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 17. Jul 10 17:54:04 localhost systemd-udevd[329]: Using default interface naming scheme 'rhel-9.0'. Jul 10 17:54:04 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 17. Jul 10 17:54:04 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 50. Jul 10 17:54:04 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 21. Jul 10 17:54:04 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 21. Jul 10 17:54:04 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. Jul 10 17:54:04 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. Jul 10 17:54:04 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 43. Jul 10 17:54:04 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 45. Jul 10 17:54:04 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 42. Jul 10 17:54:04 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 40. Jul 10 17:54:04 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 23. Jul 10 17:54:04 localhost systemd[1]: Created slice Slice /system/modprobe. ░░ Subject: A start job for unit system-modprobe.slice has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit system-modprobe.slice has finished successfully. ░░ ░░ The job identifier is 59. Jul 10 17:54:04 localhost rngd[348]: Disabling 7: PKCS11 Entropy generator (pkcs11) Jul 10 17:54:04 localhost rngd[348]: Disabling 5: NIST Network Entropy Beacon (nist) Jul 10 17:54:04 localhost rngd[348]: Disabling 9: Qrypt quantum entropy beacon (qrypt) Jul 10 17:54:04 localhost rngd[348]: Initializing available sources Jul 10 17:54:04 localhost rngd[348]: [hwrng ]: Initialization Failed Jul 10 17:54:04 localhost rngd[348]: [rdrand]: Enabling RDSEED rng support Jul 10 17:54:04 localhost rngd[348]: [rdrand]: Initialized Jul 10 17:54:04 localhost rngd[348]: [jitter]: JITTER timeout set to 5 sec Jul 10 17:54:04 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 58. Jul 10 17:54:04 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. Jul 10 17:54:04 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 58. Jul 10 17:54:04 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 56. Jul 10 17:54:04 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 56. Jul 10 17:54:04 localhost rngd[348]: [jitter]: Initializing AES buffer Jul 10 17:54:04 localhost kernel: Key type psk registered Jul 10 17:54:04 localhost kernel: ena 0000:00:05.0: ENA device version: 0.10 Jul 10 17:54:04 localhost kernel: ena 0000:00:05.0: ENA controller version: 0.0.1 implementation version 1 Jul 10 17:54:04 localhost kernel: ena 0000:00:05.0: Elastic Network Adapter (ENA) found at mem febf4000, mac addr 0e:26:17:53:a2:a3 Jul 10 17:54:04 localhost systemd-udevd[332]: Network interface NamePolicy= disabled on kernel command line. Jul 10 17:54:04 localhost kernel: nvme nvme0: pci function 0000:00:04.0 Jul 10 17:54:04 localhost kernel: ACPI: \_SB_.LNKD: Enabled at IRQ 11 Jul 10 17:54:04 localhost kernel: nvme nvme0: 2/0/0 default/read/poll queues Jul 10 17:54:04 localhost kernel: nvme0n1: p1 Jul 10 17:54:05 localhost systemd[1]: Found device Amazon Elastic Block Store 1. ░░ Subject: A start job for unit dev-disk-by\x2duuid-7c0d6762\x2da0be\x2d4063\x2da43a\x2dc35e843399f8.device has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dev-disk-by\x2duuid-7c0d6762\x2da0be\x2d4063\x2da43a\x2dc35e843399f8.device has finished successfully. ░░ ░░ The job identifier is 38. Jul 10 17:54:05 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 55. Jul 10 17:54:06 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 40. Jul 10 17:54:06 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 41. Jul 10 17:54:06 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 47. Jul 10 17:54:06 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 34. Jul 10 17:54:06 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 34. Jul 10 17:54:06 localhost systemd[1]: Starting File System Check on /dev/disk/by-uuid/7c0d6762-a0be-4063-a43a-c35e843399f8... ░░ 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 37. Jul 10 17:54:06 localhost systemd-fsck[397]: /usr/sbin/fsck.xfs: XFS file system. Jul 10 17:54:06 localhost systemd[1]: Finished File System Check on /dev/disk/by-uuid/7c0d6762-a0be-4063-a43a-c35e843399f8. ░░ 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 37. Jul 10 17:54:06 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 36. Jul 10 17:54:06 localhost kernel: SGI XFS with ACLs, security attributes, scrub, quota, no debug enabled Jul 10 17:54:06 localhost kernel: XFS (nvme0n1p1): Mounting V5 Filesystem 7c0d6762-a0be-4063-a43a-c35e843399f8 Jul 10 17:54:07 localhost kernel: XFS (nvme0n1p1): Ending clean mount Jul 10 17:54:07 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 36. Jul 10 17:54:07 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 51. Jul 10 17:54:07 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 53. Jul 10 17:54:07 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. Jul 10 17:54:07 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 53. Jul 10 17:54:07 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 52. Jul 10 17:54:07 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. Jul 10 17:54:07 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 54. Jul 10 17:54:07 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 46. Jul 10 17:54:07 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 46. Jul 10 17:54:07 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 62. Jul 10 17:54:07 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 109 and the job result is done. Jul 10 17:54:07 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 110 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 116 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 112 and the job result is done. Jul 10 17:54:07 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 98 and the job result is done. Jul 10 17:54:07 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 120 and the job result is done. Jul 10 17:54:07 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 99 and the job result is done. Jul 10 17:54:07 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 125 and the job result is done. Jul 10 17:54:07 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 123 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 100 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 115 and the job result is done. Jul 10 17:54:07 localhost systemd[1]: Stopping Hardware RNG Entropy Gatherer Daemon... ░░ Subject: A stop job for unit rngd.service has begun execution ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit rngd.service has begun execution. ░░ ░░ The job identifier is 102. Jul 10 17:54:07 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. Jul 10 17:54:07 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 97 and the job result is done. Jul 10 17:54:07 localhost systemd[1]: rngd.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit rngd.service has successfully entered the 'dead' state. Jul 10 17:54:07 localhost systemd[1]: Stopped Hardware RNG Entropy Gatherer Daemon. ░░ Subject: A stop job for unit rngd.service has finished ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A stop job for unit rngd.service has finished. ░░ ░░ The job identifier is 102 and the job result is done. Jul 10 17:54:07 localhost systemd[1]: rngd.service: Consumed 4.077s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit rngd.service completed and consumed the indicated resources. Jul 10 17:54:07 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 105 and the job result is done. Jul 10 17:54:07 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 111 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 104 and the job result is done. Jul 10 17:54:07 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 106 and the job result is done. Jul 10 17:54:07 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 101 and the job result is done. Jul 10 17:54:07 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 121 and the job result is done. Jul 10 17:54:07 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 103 and the job result is done. Jul 10 17:54:07 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 108 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 107 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 96 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 70 and the job result is done. Jul 10 17:54:07 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 72. Jul 10 17:54:07 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. Jul 10 17:54:07 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. Jul 10 17:54:07 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. Jul 10 17:54:07 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 62. Jul 10 17:54:07 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. Jul 10 17:54:07 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 72 and the job result is done. Jul 10 17:54:07 localhost systemd[1]: systemd-udevd.service: Consumed 1.082s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit systemd-udevd.service completed and consumed the indicated resources. Jul 10 17:54:07 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. Jul 10 17:54:07 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. Jul 10 17:54:07 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. Jul 10 17:54:07 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 73 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 114 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 113 and the job result is done. Jul 10 17:54:07 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 66. Jul 10 17:54:07 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. Jul 10 17:54:07 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 93 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 124 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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 95 and the job result is done. Jul 10 17:54:07 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. Jul 10 17:54:07 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. Jul 10 17:54:07 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. Jul 10 17:54:07 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 66. Jul 10 17:54:07 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 65. Jul 10 17:54:07 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 74. Jul 10 17:54:07 localhost systemd[1]: Switching root. Jul 10 17:54:07 localhost systemd-journald[233]: 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. Jul 10 17:54:18 localhost systemd-journald[233]: Received SIGTERM from PID 1 (systemd). Jul 10 17:54:18 localhost kernel: audit: type=1404 audit(1783720453.249:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1 Jul 10 17:54:18 localhost kernel: SELinux: policy capability network_peer_controls=1 Jul 10 17:54:18 localhost kernel: SELinux: policy capability open_perms=1 Jul 10 17:54:18 localhost kernel: SELinux: policy capability extended_socket_class=1 Jul 10 17:54:18 localhost kernel: SELinux: policy capability always_check_network=0 Jul 10 17:54:18 localhost kernel: SELinux: policy capability cgroup_seclabel=1 Jul 10 17:54:18 localhost kernel: SELinux: policy capability nnp_nosuid_transition=1 Jul 10 17:54:18 localhost kernel: SELinux: policy capability genfs_seclabel_symlinks=1 Jul 10 17:54:18 localhost kernel: audit: type=1403 audit(1783720453.966:3): auid=4294967295 ses=4294967295 lsm=selinux res=1 Jul 10 17:54:18 localhost systemd[1]: Successfully loaded SELinux policy in 842.753ms. Jul 10 17:54:18 localhost systemd[1]: Relabelled /dev, /dev/shm, /run, /sys/fs/cgroup in 19.316ms. Jul 10 17:54:18 localhost systemd[1]: systemd 252-71.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) Jul 10 17:54:18 localhost systemd[1]: Detected virtualization amazon. Jul 10 17:54:18 localhost systemd[1]: Detected architecture x86-64. Jul 10 17:54:18 localhost systemd[1]: Initializing machine ID from VM UUID. Jul 10 17:54:18 localhost systemd[1]: Installed transient /etc/machine-id file. Jul 10 17:54:18 localhost systemd-rc-local-generator[463]: /etc/rc.d/rc.local is not marked executable, skipping. Jul 10 17:54:18 localhost systemd[1]: initrd-switch-root.service: Deactivated successfully. Jul 10 17:54:18 localhost systemd[1]: Stopped Switch Root. Jul 10 17:54:18 localhost systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1. Jul 10 17:54:18 localhost systemd[1]: Created slice Slice /system/getty. Jul 10 17:54:18 localhost systemd[1]: Created slice Slice /system/serial-getty. Jul 10 17:54:18 localhost systemd[1]: Created slice Slice /system/sshd-keygen. Jul 10 17:54:18 localhost systemd[1]: Created slice User and Session Slice. Jul 10 17:54:18 localhost systemd[1]: Started Dispatch Password Requests to Console Directory Watch. Jul 10 17:54:18 localhost systemd[1]: Started Forward Password Requests to Wall Directory Watch. Jul 10 17:54:18 localhost systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. Jul 10 17:54:18 localhost systemd[1]: Reached target Local Encrypted Volumes. Jul 10 17:54:18 localhost systemd[1]: Stopped target Switch Root. Jul 10 17:54:18 localhost systemd[1]: Stopped target Initrd File Systems. Jul 10 17:54:18 localhost systemd[1]: Stopped target Initrd Root File System. Jul 10 17:54:18 localhost systemd[1]: Reached target Local Integrity Protected Volumes. Jul 10 17:54:18 localhost systemd[1]: Reached target Path Units. Jul 10 17:54:18 localhost systemd[1]: Reached target Slice Units. Jul 10 17:54:18 localhost systemd[1]: Reached target Swaps. Jul 10 17:54:18 localhost systemd[1]: Reached target Local Verity Protected Volumes. Jul 10 17:54:18 localhost systemd[1]: Listening on RPCbind Server Activation Socket. Jul 10 17:54:18 localhost systemd[1]: Reached target RPC Port Mapper. Jul 10 17:54:18 localhost systemd[1]: Listening on Process Core Dump Socket. Jul 10 17:54:18 localhost systemd[1]: Listening on initctl Compatibility Named Pipe. Jul 10 17:54:18 localhost systemd[1]: Listening on udev Control Socket. Jul 10 17:54:18 localhost systemd[1]: Listening on udev Kernel Socket. Jul 10 17:54:18 localhost systemd[1]: Mounting Huge Pages File System... Jul 10 17:54:18 localhost systemd[1]: Mounting POSIX Message Queue File System... Jul 10 17:54:18 localhost systemd[1]: Mounting Kernel Debug File System... Jul 10 17:54:18 localhost systemd[1]: Mounting Kernel Trace File System... Jul 10 17:54:18 localhost systemd[1]: Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab). Jul 10 17:54:18 localhost systemd[1]: Starting Create List of Static Device Nodes... Jul 10 17:54:18 localhost systemd[1]: Starting Load Kernel Module configfs... Jul 10 17:54:18 localhost systemd[1]: Starting Load Kernel Module drm... Jul 10 17:54:18 localhost systemd[1]: Starting Load Kernel Module efi_pstore... Jul 10 17:54:18 localhost systemd[1]: Starting Load Kernel Module fuse... Jul 10 17:54:18 localhost systemd[1]: Starting Read and set NIS domainname from /etc/sysconfig/network... Jul 10 17:54:18 localhost systemd[1]: systemd-fsck-root.service: Deactivated successfully. Jul 10 17:54:18 localhost systemd[1]: Stopped File System Check on Root Device. Jul 10 17:54:18 localhost systemd[1]: Stopped Journal Service. Jul 10 17:54:18 localhost systemd[1]: Starting Journal Service... Jul 10 17:54:18 localhost systemd[1]: Load Kernel Modules was skipped because no trigger condition checks were met. Jul 10 17:54:18 localhost systemd[1]: Starting Generate network units from Kernel command line... Jul 10 17:54:18 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). Jul 10 17:54:18 localhost systemd[1]: Starting Remount Root and Kernel File Systems... Jul 10 17:54:18 localhost systemd[1]: Repartition Root Disk was skipped because no trigger condition checks were met. Jul 10 17:54:18 localhost kernel: fuse: init (API version 7.37) Jul 10 17:54:18 localhost systemd[1]: Starting Apply Kernel Variables... Jul 10 17:54:18 localhost systemd[1]: Starting Coldplug All udev Devices... Jul 10 17:54:18 localhost systemd-journald[509]: 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. Jul 10 17:54:18 localhost systemd-journald[509]: Runtime Journal (/run/log/journal/ec2f5b688767bfa432bd0e242a9410c2) is 8.0M, max 68.3M, 60.3M free. ░░ Subject: Disk space used by the journal ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ Runtime Journal (/run/log/journal/ec2f5b688767bfa432bd0e242a9410c2) is currently using 8.0M. ░░ Maximum allowed usage is set to 68.3M. ░░ Leaving at least 34.1M free (of currently available 667.0M of disk space). ░░ Enforced usage limit is thus 68.3M, of which 60.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. Jul 10 17:54:17 localhost systemd[1]: Queued start job for default target Multi-User System. Jul 10 17:54:18 localhost systemd[1]: Mounted Huge Pages File System. Jul 10 17:54:18 localhost systemd[1]: Started Journal Service. Jul 10 17:54:17 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. Jul 10 17:54:18 localhost systemd[1]: Mounted POSIX Message Queue File System. ░░ Subject: A start job for unit dev-mqueue.mount has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dev-mqueue.mount has finished successfully. ░░ ░░ The job identifier is 191. Jul 10 17:54:18 localhost systemd[1]: Mounted Kernel Debug File System. ░░ Subject: A start job for unit sys-kernel-debug.mount has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sys-kernel-debug.mount has finished successfully. ░░ ░░ The job identifier is 171. Jul 10 17:54:18 localhost systemd[1]: Mounted Kernel Trace File System. ░░ Subject: A start job for unit sys-kernel-tracing.mount has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit sys-kernel-tracing.mount has finished successfully. ░░ ░░ The job identifier is 137. Jul 10 17:54:18 localhost kernel: ACPI: bus type drm_connector registered Jul 10 17:54:18 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 142. Jul 10 17:54:18 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. Jul 10 17:54:18 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 180. Jul 10 17:54:18 localhost systemd[1]: modprobe@drm.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit modprobe@drm.service has successfully entered the 'dead' state. Jul 10 17:54:18 localhost systemd[1]: Finished Load Kernel Module drm. ░░ Subject: A start job for unit modprobe@drm.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit modprobe@drm.service has finished successfully. ░░ ░░ The job identifier is 214. Jul 10 17:54:18 localhost systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit modprobe@efi_pstore.service has successfully entered the 'dead' state. Jul 10 17:54:18 localhost systemd[1]: Finished Load Kernel Module efi_pstore. ░░ Subject: A start job for unit modprobe@efi_pstore.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit modprobe@efi_pstore.service has finished successfully. ░░ ░░ The job identifier is 147. Jul 10 17:54:18 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. Jul 10 17:54:18 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 155. Jul 10 17:54:18 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 157. Jul 10 17:54:18 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 172. Jul 10 17:54:18 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 134. Jul 10 17:54:18 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 154. Jul 10 17:54:18 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 167. Jul 10 17:54:18 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 170. Jul 10 17:54:18 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 176. Jul 10 17:54:18 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 146. Jul 10 17:54:18 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 189. Jul 10 17:54:18 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 140. Jul 10 17:54:18 localhost systemd-journald[509]: Runtime Journal (/run/log/journal/ec2f5b688767bfa432bd0e242a9410c2) is 8.0M, max 68.3M, 60.3M free. ░░ Subject: Disk space used by the journal ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ Runtime Journal (/run/log/journal/ec2f5b688767bfa432bd0e242a9410c2) is currently using 8.0M. ░░ Maximum allowed usage is set to 68.3M. ░░ Leaving at least 34.1M free (of currently available 667.0M of disk space). ░░ Enforced usage limit is thus 68.3M, of which 60.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. Jul 10 17:54:18 localhost systemd-journald[509]: Received client request to flush runtime journal. Jul 10 17:54:18 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 175. Jul 10 17:54:18 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 154. Jul 10 17:54:18 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 176. Jul 10 17:54:18 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 153. Jul 10 17:54:18 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 189. Jul 10 17:54:18 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 168. Jul 10 17:54:18 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 181. Jul 10 17:54:18 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 175. Jul 10 17:54:18 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 135. Jul 10 17:54:18 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 133. Jul 10 17:54:18 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 151. Jul 10 17:54:18 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 145. Jul 10 17:54:18 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 152. Jul 10 17:54:18 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 150. Jul 10 17:54:18 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 190. Jul 10 17:54:18 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 187. Jul 10 17:54:18 localhost bootctl[522]: Couldn't find EFI system partition, skipping. Jul 10 17:54:18 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 143. Jul 10 17:54:18 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 182. Jul 10 17:54:18 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 190. Jul 10 17:54:18 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 187. Jul 10 17:54:18 localhost systemd-udevd[526]: Using default interface naming scheme 'rhel-9.0'. Jul 10 17:54:19 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 143. Jul 10 17:54:19 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 231. Jul 10 17:54:19 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 211. Jul 10 17:54:19 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 149. Jul 10 17:54:19 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 174. Jul 10 17:54:19 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 182. Jul 10 17:54:19 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 273. Jul 10 17:54:19 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. Jul 10 17:54:19 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 273. Jul 10 17:54:19 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 224. Jul 10 17:54:19 localhost kernel: input: PC Speaker as /devices/platform/pcspkr/input/input5 Jul 10 17:54:19 localhost nfsrahead[553]: skipping non-NFS device 259:0 Jul 10 17:54:19 localhost kernel: parport_pc 00:03: reported by Plug and Play ACPI Jul 10 17:54:19 localhost kernel: ppdev: user-space parallel port driver Jul 10 17:54:19 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. Jul 10 17:54:19 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 247. Jul 10 17:54:19 localhost kernel: piix4_smbus 0000:00:01.3: SMBus Host Controller at 0xb100, revision 255 Jul 10 17:54:19 localhost kernel: i2c i2c-0: 1/1 memory slots populated (from DMI) Jul 10 17:54:19 localhost kernel: i2c i2c-0: Failed! (ff) Jul 10 17:54:19 localhost kernel: RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer Jul 10 17:54:19 localhost auditd[562]: No plugins found, not dispatching events Jul 10 17:54:19 localhost systemd-udevd[535]: Network interface NamePolicy= disabled on kernel command line. Jul 10 17:54:19 localhost auditd[562]: Init complete, auditd 3.1.5 listening for events (startup state enable) Jul 10 17:54:19 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 211. Jul 10 17:54:19 localhost kernel: RPC: Registered named UNIX socket transport module. Jul 10 17:54:19 localhost kernel: RPC: Registered udp transport module. Jul 10 17:54:19 localhost kernel: RPC: Registered tcp transport module. Jul 10 17:54:19 localhost kernel: RPC: Registered tcp-with-tls transport module. Jul 10 17:54:19 localhost kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Jul 10 17:54:19 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 247. Jul 10 17:54:19 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 246. Jul 10 17:54:19 localhost augenrules[566]: /sbin/augenrules: No change Jul 10 17:54:19 localhost augenrules[586]: No rules Jul 10 17:54:19 localhost augenrules[586]: enabled 1 Jul 10 17:54:19 localhost augenrules[586]: failure 1 Jul 10 17:54:19 localhost augenrules[586]: pid 562 Jul 10 17:54:19 localhost augenrules[586]: rate_limit 0 Jul 10 17:54:19 localhost augenrules[586]: backlog_limit 8192 Jul 10 17:54:19 localhost augenrules[586]: lost 0 Jul 10 17:54:19 localhost augenrules[586]: backlog 3 Jul 10 17:54:19 localhost augenrules[586]: backlog_wait_time 60000 Jul 10 17:54:19 localhost augenrules[586]: backlog_wait_time_actual 0 Jul 10 17:54:19 localhost augenrules[586]: enabled 1 Jul 10 17:54:19 localhost augenrules[586]: failure 1 Jul 10 17:54:19 localhost augenrules[586]: pid 562 Jul 10 17:54:19 localhost augenrules[586]: rate_limit 0 Jul 10 17:54:19 localhost augenrules[586]: backlog_limit 8192 Jul 10 17:54:19 localhost augenrules[586]: lost 0 Jul 10 17:54:19 localhost augenrules[586]: backlog 3 Jul 10 17:54:19 localhost augenrules[586]: backlog_wait_time 60000 Jul 10 17:54:19 localhost augenrules[586]: backlog_wait_time_actual 0 Jul 10 17:54:19 localhost augenrules[586]: enabled 1 Jul 10 17:54:19 localhost augenrules[586]: failure 1 Jul 10 17:54:19 localhost augenrules[586]: pid 562 Jul 10 17:54:19 localhost augenrules[586]: rate_limit 0 Jul 10 17:54:19 localhost augenrules[586]: backlog_limit 8192 Jul 10 17:54:19 localhost augenrules[586]: lost 0 Jul 10 17:54:19 localhost augenrules[586]: backlog 3 Jul 10 17:54:19 localhost augenrules[586]: backlog_wait_time 60000 Jul 10 17:54:19 localhost augenrules[586]: backlog_wait_time_actual 0 Jul 10 17:54:19 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 231. Jul 10 17:54:19 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 226. Jul 10 17:54:20 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 226. Jul 10 17:54:20 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 130. Jul 10 17:54:20 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 195. Jul 10 17:54:20 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 194. Jul 10 17:54:20 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 193. Jul 10 17:54:20 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 192. Jul 10 17:54:20 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 199. Jul 10 17:54:20 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 207. Jul 10 17:54:20 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 205. Jul 10 17:54:20 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 200. Jul 10 17:54:20 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 138. Jul 10 17:54:20 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 200. Jul 10 17:54:20 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 127. Jul 10 17:54:20 localhost dbus-broker-lau[598]: Ready Jul 10 17:54:20 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 257. Jul 10 17:54:20 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 252. Jul 10 17:54:20 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 131. Jul 10 17:54:20 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 238. Jul 10 17:54:20 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 202. Jul 10 17:54:20 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 216. Jul 10 17:54:20 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 236. Jul 10 17:54:20 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 234. Jul 10 17:54:20 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 237. Jul 10 17:54:20 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 233. Jul 10 17:54:20 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 227. Jul 10 17:54:20 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 228. Jul 10 17:54:20 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 213. Jul 10 17:54:20 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 279. Jul 10 17:54:20 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 131. Jul 10 17:54:20 localhost systemd-logind[607]: Watching system buttons on /dev/input/event0 (Power Button) Jul 10 17:54:20 localhost systemd-logind[607]: Watching system buttons on /dev/input/event1 (Sleep Button) Jul 10 17:54:20 localhost systemd-logind[607]: Watching system buttons on /dev/input/event2 (AT Translated Set 2 keyboard) Jul 10 17:54:20 localhost systemd-logind[607]: 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. Jul 10 17:54:20 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 213. Jul 10 17:54:21 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. Jul 10 17:54:21 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 279. Jul 10 17:54:21 localhost chronyd[612]: chronyd version 4.8 starting (+CMDMON +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +NTS +SECHASH +IPV6 +DEBUG) Jul 10 17:54:21 localhost chronyd[612]: Loaded 0 symmetric keys Jul 10 17:54:21 localhost chronyd[612]: Using right/UTC timezone to obtain leap second data Jul 10 17:54:21 localhost chronyd[612]: Frequency 0.000 +/- 1000000.000 ppm read from /var/lib/chrony/drift Jul 10 17:54:21 localhost chronyd[612]: Loaded seccomp filter (level 2) Jul 10 17:54:21 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 257. Jul 10 17:54:21 localhost rngd[606]: Disabling 7: PKCS11 Entropy generator (pkcs11) Jul 10 17:54:21 localhost rngd[606]: Disabling 5: NIST Network Entropy Beacon (nist) Jul 10 17:54:21 localhost rngd[606]: Disabling 9: Qrypt quantum entropy beacon (qrypt) Jul 10 17:54:21 localhost rngd[606]: Disabling 10: Named pipe entropy input (namedpipe) Jul 10 17:54:21 localhost rngd[606]: Disabling 6: JITTER Entropy generator (jitter) Jul 10 17:54:21 localhost rngd[606]: Disabling 11: Radiacode radiation detector entropy source (radiacode) Jul 10 17:54:21 localhost rngd[606]: Disabling 8: RTLSDR software defined radio generator (rtlsdr) Jul 10 17:54:21 localhost rngd[606]: Initializing available sources Jul 10 17:54:21 localhost rngd[606]: [hwrng ]: Initialization Failed Jul 10 17:54:21 localhost rngd[606]: [rdrand]: Enabling RDSEED rng support Jul 10 17:54:21 localhost rngd[606]: [rdrand]: Initialized Jul 10 17:54:21 localhost rngd[606]: Process privileges have been dropped to 2:2 Jul 10 17:54:24 localhost cloud-init[616]: Cloud-init v. 24.4-8.el9.1 running 'init-local' at Fri, 10 Jul 2026 21:54:24 +0000. Up 22.86 seconds. Jul 10 17:54:24 localhost dhclient[620]: Internet Systems Consortium DHCP Client 4.4.2b1 Jul 10 17:54:24 localhost dhclient[620]: Copyright 2004-2019 Internet Systems Consortium. Jul 10 17:54:24 localhost dhclient[620]: All rights reserved. Jul 10 17:54:24 localhost dhclient[620]: For info, please visit https://www.isc.org/software/dhcp/ Jul 10 17:54:24 localhost dhclient[620]: Jul 10 17:54:24 localhost dhclient[620]: Listening on LPF/eth0/0e:26:17:53:a2:a3 Jul 10 17:54:24 localhost dhclient[620]: Sending on LPF/eth0/0e:26:17:53:a2:a3 Jul 10 17:54:24 localhost dhclient[620]: Sending on Socket/fallback Jul 10 17:54:24 localhost dhclient[620]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 (xid=0x73669b62) Jul 10 17:54:24 localhost dhclient[620]: DHCPOFFER of 10.31.43.137 from 10.31.40.1 Jul 10 17:54:24 localhost dhclient[620]: DHCPREQUEST for 10.31.43.137 on eth0 to 255.255.255.255 port 67 (xid=0x73669b62) Jul 10 17:54:24 localhost dhclient[620]: DHCPACK of 10.31.43.137 from 10.31.40.1 (xid=0x73669b62) Jul 10 17:54:24 localhost dhclient[620]: bound to 10.31.43.137 -- renewal in 1399 seconds. Jul 10 17:54:25 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 344. Jul 10 17:54:25 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 344. Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-hostnamed[635]: Hostname set to (static) Jul 10 17:54:25 ip-10-31-43-137.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 252. Jul 10 17:54:25 ip-10-31-43-137.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 173. Jul 10 17:54:25 ip-10-31-43-137.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 198. Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6675] NetworkManager (version 1.54.4-2.el9) is starting... (boot:50eb0d97-b313-41b1-8455-cf0354e5b387) Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6677] Read config: /etc/NetworkManager/NetworkManager.conf, /run/NetworkManager/conf.d/15-carrier-timeout.conf Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6782] manager[0x55e40ef57000]: monitoring kernel firmware directory '/lib/firmware'. Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6812] hostname: hostname: using hostnamed Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6812] hostname: static hostname changed from (none) to "ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com" Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6817] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto) Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.8068] manager[0x55e40ef57000]: rfkill: Wi-Fi hardware radio set enabled Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.8069] manager[0x55e40ef57000]: rfkill: WWAN hardware radio set enabled Jul 10 17:54:25 ip-10-31-43-137.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 411. Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9465] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.54.4-2.el9/libnm-device-plugin-team.so) Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9467] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9468] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9468] manager: Networking is enabled by state file Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9476] settings: Loaded settings plugin: keyfile (internal) Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9512] settings: Loaded settings plugin: ifcfg-rh ("/usr/lib64/NetworkManager/1.54.4-2.el9/libnm-settings-plugin-ifcfg-rh.so") Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9542] Warning: the ifcfg-rh plugin is deprecated, please migrate connections to the keyfile format using "nmcli connection migrate" Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9557] dhcp: init: Using DHCP client 'internal' Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9560] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1) Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9570] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9581] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Jul 10 17:54:25 ip-10-31-43-137.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 418. Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9619] device (lo): Activation: starting connection 'lo' (302ef318-820a-4c31-bc97-abc1be340944) Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9625] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9629] device (eth0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external') Jul 10 17:54:25 ip-10-31-43-137.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 198. Jul 10 17:54:25 ip-10-31-43-137.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 201. Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9718] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9724] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9730] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external') Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9733] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external') Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9736] device (eth0): carrier: link connected Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9738] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9745] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full') Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9750] policy: auto-activating connection 'System eth0' (5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03) Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9755] device (eth0): Activation: starting connection 'System eth0' (5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03) Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9756] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full') Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9758] manager: NetworkManager state is now CONNECTING Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9760] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full') Jul 10 17:54:25 ip-10-31-43-137.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 197. Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9786] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full') Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9790] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9804] dhcp4 (eth0): state changed new lease, address=10.31.43.137 Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9819] policy: set 'System eth0' (eth0) as default for IPv4 routing and DNS Jul 10 17:54:25 ip-10-31-43-137.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 244. Jul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9898] device (eth0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full') Jul 10 17:54:26 ip-10-31-43-137.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 244. Jul 10 17:54:26 ip-10-31-43-137.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 245. Jul 10 17:54:26 ip-10-31-43-137.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 241. Jul 10 17:54:26 ip-10-31-43-137.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 249. Jul 10 17:54:26 ip-10-31-43-137.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 256. Jul 10 17:54:26 ip-10-31-43-137.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 186. Jul 10 17:54:26 ip-10-31-43-137.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 418. Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2078] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2081] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external') Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2090] device (lo): Activation: successful, device activated. Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2125] device (eth0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full') Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2129] device (eth0): state change: secondaries -> activated (reason 'none', managed-type: 'full') Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2135] manager: NetworkManager state is now CONNECTED_SITE Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2154] device (eth0): Activation: successful, device activated. Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2164] manager: NetworkManager state is now CONNECTED_GLOBAL Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2170] manager: startup complete Jul 10 17:54:26 ip-10-31-43-137.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 197. Jul 10 17:54:26 ip-10-31-43-137.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 251. Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: Added source 10.11.160.238 Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: Added source 10.18.100.10 Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: Added source 10.2.32.37 Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: Added source 10.2.32.38 Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Cloud-init v. 24.4-8.el9.1 running 'init' at Fri, 10 Jul 2026 21:54:26 +0000. Up 25.07 seconds. Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: ++++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++++ Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+ Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address | Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+ Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | eth0 | True | 10.31.43.137 | 255.255.252.0 | global | 0e:26:17:53:a2:a3 | Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | eth0 | True | fe80::c26:17ff:fe53:a2a3/64 | . | link | 0e:26:17:53:a2:a3 | Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . | Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | lo | True | ::1/128 | . | host | . | Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+ Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: ++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++ Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+------------+---------------+-----------+-------+ Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags | Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+------------+---------------+-----------+-------+ Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | 0 | 0.0.0.0 | 10.31.40.1 | 0.0.0.0 | eth0 | UG | Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | 1 | 10.31.40.0 | 0.0.0.0 | 255.255.252.0 | eth0 | U | Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+------------+---------------+-----------+-------+ Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++ Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+---------+-----------+-------+ Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | Route | Destination | Gateway | Interface | Flags | Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+---------+-----------+-------+ Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | 1 | fe80::/64 | :: | eth0 | U | Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | 3 | multicast | :: | eth0 | U | Jul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+---------+-----------+-------+ Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Generating public/private rsa key pair. Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your identification has been saved in /etc/ssh/ssh_host_rsa_key Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key fingerprint is: Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: SHA256:dmFeaAMb/pejg2wfOzTth6u62tK3BMbUAWOZ/eHAwS0 root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key's randomart image is: Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +---[RSA 3072]----+ Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | *Boo | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | oo*Eoo | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | + B=.. | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | o = +o. | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | S +.+ | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | + +oo.. | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | .+.=o . | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | .o.oo+o . | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | .o++=+.o | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +----[SHA256]-----+ Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Generating public/private ecdsa key pair. Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key fingerprint is: Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: SHA256:C0qeOqMG364qgBsVlyBHRFOYQACccHJCFiKDwLSDFyY root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key's randomart image is: Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +---[ECDSA 256]---+ Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |E@#=.. | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |*#=oo | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |.o.o | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | .o | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |.. . . S | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |= o o . . | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |o+ .+ . | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |o.+.. | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |=oo=. | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +----[SHA256]-----+ Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Generating public/private ed25519 key pair. Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your identification has been saved in /etc/ssh/ssh_host_ed25519_key Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key fingerprint is: Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: SHA256:dNPitcZCSglodInvKUrvKnskGjz+zXLMcbT/KrzIp14 root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key's randomart image is: Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +--[ED25519 256]--+ Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | ..oo. | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | +... . . | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | . . + = o | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | .+ = = . | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |. ...S o + | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |ooo ..oo o | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |o=.oo.+E. | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |o.o.=+o+ . | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |.+o+=Bo.o.o. | Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +----[SHA256]-----+ Jul 10 17:54:27 ip-10-31-43-137.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 251. Jul 10 17:54:27 ip-10-31-43-137.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 254. Jul 10 17:54:27 ip-10-31-43-137.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 196. Jul 10 17:54:27 ip-10-31-43-137.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 253. Jul 10 17:54:27 ip-10-31-43-137.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 212. Jul 10 17:54:27 ip-10-31-43-137.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 230. Jul 10 17:54:27 ip-10-31-43-137.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 242. Jul 10 17:54:27 ip-10-31-43-137.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 229. Jul 10 17:54:27 ip-10-31-43-137.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 232. Jul 10 17:54:27 ip-10-31-43-137.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 239. Jul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sm-notify[804]: Version 2.5.4 starting Jul 10 17:54:27 ip-10-31-43-137.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 230. Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd[806]: Server listening on 0.0.0.0 port 22. Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd[806]: Server listening on :: port 22. Jul 10 17:54:28 ip-10-31-43-137.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 232. Jul 10 17:54:28 ip-10-31-43-137.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 242. Jul 10 17:54:28 ip-10-31-43-137.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 239. Jul 10 17:54:28 ip-10-31-43-137.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 260. Jul 10 17:54:28 ip-10-31-43-137.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 218. Jul 10 17:54:28 ip-10-31-43-137.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 222. Jul 10 17:54:28 ip-10-31-43-137.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 217. Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com restraintd[810]: Listening on http://localhost:8081 Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) STARTUP (1.5.7) Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (Syslog will be used instead of sendmail.) Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 70% if used.) Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (running with inotify support) Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[931]: Cloud-init v. 24.4-8.el9.1 running 'modules:config' at Fri, 10 Jul 2026 21:54:28 +0000. Up 26.88 seconds. Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com rsyslogd[805]: [origin software="rsyslogd" swVersion="8.2604.0-1.el9" x-pid="805" x-info="https://www.rsyslog.com"] start Jul 10 17:54:28 ip-10-31-43-137.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 229. Jul 10 17:54:28 ip-10-31-43-137.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 126. Jul 10 17:54:28 ip-10-31-43-137.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 225. Jul 10 17:54:28 ip-10-31-43-137.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. Jul 10 17:54:28 ip-10-31-43-137.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 225. Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd[806]: Received signal 15; terminating. Jul 10 17:54:28 ip-10-31-43-137.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 514. Jul 10 17:54:28 ip-10-31-43-137.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. Jul 10 17:54:28 ip-10-31-43-137.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 514 and the job result is done. Jul 10 17:54:28 ip-10-31-43-137.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 514. Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd[938]: Server listening on 0.0.0.0 port 22. Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd[938]: Server listening on :: port 22. Jul 10 17:54:28 ip-10-31-43-137.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 514. Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com rsyslogd[805]: imjournal: journal files changed, reloading... [v8.2604.0-1.el9 try https://www.rsyslog.com/e/0 ] Jul 10 17:54:28 ip-10-31-43-137.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 253. Jul 10 17:54:28 ip-10-31-43-137.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 255. Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[942]: Cloud-init v. 24.4-8.el9.1 running 'modules:final' at Fri, 10 Jul 2026 21:54:28 +0000. Up 27.30 seconds. Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1014]: ############################################################# Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1020]: -----BEGIN SSH HOST KEY FINGERPRINTS----- Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1030]: 256 SHA256:C0qeOqMG364qgBsVlyBHRFOYQACccHJCFiKDwLSDFyY root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com (ECDSA) Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1039]: 256 SHA256:dNPitcZCSglodInvKUrvKnskGjz+zXLMcbT/KrzIp14 root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com (ED25519) Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1051]: 3072 SHA256:dmFeaAMb/pejg2wfOzTth6u62tK3BMbUAWOZ/eHAwS0 root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com (RSA) Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1054]: -----END SSH HOST KEY FINGERPRINTS----- Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1059]: ############################################################# Jul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[942]: Cloud-init v. 24.4-8.el9.1 finished at Fri, 10 Jul 2026 21:54:28 +0000. Datasource DataSourceEc2Local. Up 27.51 seconds Jul 10 17:54:29 ip-10-31-43-137.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 255. Jul 10 17:54:29 ip-10-31-43-137.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 250. Jul 10 17:54:29 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Detected change(s) in the following file(s): /etc/fstab Jul 10 17:54:32 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: Selected source 10.2.32.37 Jul 10 17:54:32 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: System clock TAI offset set to 37 seconds Jul 10 17:54:32 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kernel: block nvme0n1: the capability attribute has been deprecated. Jul 10 17:54:33 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Detected change in block device driver, new loaded module: nvme Jul 10 17:54:33 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Rebuilding /boot/initramfs-5.14.0-721.el9.x86_64kdump.img Jul 10 17:54:33 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1991]: dracut-057-118.git20260624.el9 Jul 10 17:54:33 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Executing: /usr/bin/dracut --quiet --hostonly --hostonly-cmdline --hostonly-i18n --hostonly-mode strict --hostonly-nics --mount "/dev/disk/by-uuid/7c0d6762-a0be-4063-a43a-c35e843399f8 /sysroot xfs rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota" --squash-compressor zstd --no-hostonly-default-device --add-drivers nvme --add-confdir /lib/kdump/dracut.conf.d -f /boot/initramfs-5.14.0-721.el9.x86_64kdump.img 5.14.0-721.el9.x86_64 Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-timesyncd' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-time-wait-sync' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'busybox' will not be installed, because command 'busybox' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'dbus-daemon' will not be installed, because command 'dbus-daemon' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmand' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Module 'ifcfg' will not be installed, because it's in the list to be omitted! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Module 'plymouth' will not be installed, because it's in the list to be omitted! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: 62bluetooth: Could not find any command of '/usr/lib/bluetooth/bluetoothd /usr/libexec/bluetooth/bluetoothd'! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvmthinpool-monitor' will not be installed, because command 'lvm' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvm' will not be installed, because command 'lvm' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'pcsc' will not be installed, because command 'pcscd' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Module 'resume' will not be installed, because it's in the list to be omitted! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! Jul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Module 'earlykdump' will not be installed, because it's in the list to be omitted! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: memstrack is not available Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-timesyncd' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-time-wait-sync' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'busybox' will not be installed, because command 'busybox' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'dbus-daemon' will not be installed, because command 'dbus-daemon' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmand' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: 62bluetooth: Could not find any command of '/usr/lib/bluetooth/bluetoothd /usr/libexec/bluetooth/bluetoothd'! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvmthinpool-monitor' will not be installed, because command 'lvm' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvm' will not be installed, because command 'lvm' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'pcsc' will not be installed, because command 'pcscd' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found! Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: memstrack is not available Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: systemd *** Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: fips *** Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: systemd-initrd *** Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: rngd *** Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: i18n *** Jul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: drm *** Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: prefixdevname *** Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: kernel-modules *** Jul 10 17:54:36 ip-10-31-43-137.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. Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: kernel-modules-extra *** Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: kernel-modules-extra: configuration source "/run/depmod.d" does not exist Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: kernel-modules-extra: configuration source "/lib/depmod.d" does not exist Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: kernel-modules-extra: parsing configuration file "/etc/depmod.d/dist.conf" Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: kernel-modules-extra: /etc/depmod.d/dist.conf: added "updates extra built-in weak-updates" to the list of search directories Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: nvdimm *** Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: fstab-sys *** Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: rootfs-block *** Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: terminfo *** Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: udev-rules *** Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Skipping udev rule: 91-permissions.rules Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Skipping udev rule: 80-drivers-modprobe.rules Jul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: dracut-systemd *** Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: usrmount *** Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: base *** Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: fs-lib *** Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: kdumpbase *** Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: microcode_ctl-fw_dir_override *** Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl module: mangling fw_dir Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: reset fw_dir to "/lib/firmware/updates /lib/firmware" Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel"... Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: intel: caveats check for kernel version "5.14.0-721.el9.x86_64" passed, adding "/usr/share/microcode_ctl/ucode_with_caveats/intel" to fw_dir variable Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-2d-07"... Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration "intel-06-2d-07" is ignored Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-4e-03"... Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration "intel-06-4e-03" is ignored Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-4f-01"... Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration "intel-06-4f-01" is ignored Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-55-04"... Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: intel-06-55-04: caveats check for kernel version "5.14.0-721.el9.x86_64" passed, adding "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-55-04" to fw_dir variable Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-5e-03"... Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration "intel-06-5e-03" is ignored Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8c-01"... Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration "intel-06-8c-01" is ignored Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8e-9e-0x-0xca"... Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration "intel-06-8e-9e-0x-0xca" is ignored Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8e-9e-0x-dell"... Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration "intel-06-8e-9e-0x-dell" is ignored Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8f-08"... Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration "intel-06-8f-08" is ignored Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: final fw_dir: "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-55-04 /lib/firmware/updates /lib/firmware" Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: openssl *** Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: shutdown *** Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: squash *** Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including modules done *** Jul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Installing kernel module dependencies *** Jul 10 17:54:38 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Installing kernel module dependencies done *** Jul 10 17:54:38 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Resolving executable dependencies *** Jul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Resolving executable dependencies done *** Jul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Generating early-microcode cpio image *** Jul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Constructing GenuineIntel.bin *** Jul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Constructing GenuineIntel.bin *** Jul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Store current command line parameters *** Jul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Stored kernel commandline: Jul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: No dracut internal kernel commandline stored in the initramfs Jul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Install squash loader *** Jul 10 17:54:40 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Squashing the files inside the initramfs *** Jul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Squashing the files inside the initramfs done *** Jul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Creating image file '/boot/initramfs-5.14.0-721.el9.x86_64kdump.img' *** Jul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Hardlinking files *** Jul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Mode: real Jul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Files: 51 Jul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Linked: 0 files Jul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Compared: 0 xattrs Jul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Compared: 0 files Jul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Saved: 0 B Jul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Duration: 0.000284 seconds Jul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Hardlinking files done *** Jul 10 17:54:47 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Creating initramfs image file '/boot/initramfs-5.14.0-721.el9.x86_64kdump.img' done *** Jul 10 17:54:47 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: kexec: loaded kdump kernel Jul 10 17:54:47 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Starting kdump: [OK] Jul 10 17:54:47 ip-10-31-43-137.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 212. Jul 10 17:54:47 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[1]: Startup finished in 1.714s (kernel) + 9.909s (initrd) + 34.589s (userspace) = 46.213s. ░░ 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 1714473 microseconds. ░░ ░░ Initrd start-up required 9909188 microseconds. ░░ ░░ Userspace start-up required 34589926 microseconds. Jul 10 17:54:55 ip-10-31-43-137.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. Jul 10 17:55:20 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com irqbalance[603]: Cannot change IRQ 29 affinity: Operation not permitted Jul 10 17:55:20 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com irqbalance[603]: IRQ 29 affinity is now unmanaged Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5237]: Accepted publickey for root from 10.30.34.89 port 40702 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU Jul 10 17:56:03 ip-10-31-43-137.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 516. Jul 10 17:56:03 ip-10-31-43-137.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 520. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: 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 5237. Jul 10 17:56:03 ip-10-31-43-137.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 520. Jul 10 17:56:03 ip-10-31-43-137.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 515. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0) Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: Queued start job for default target Main User Target. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 9. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 11. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 8. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: Startup finished in 84ms. ░░ 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 84296 microseconds. Jul 10 17:56:03 ip-10-31-43-137.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 515. Jul 10 17:56:03 ip-10-31-43-137.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 583. Jul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5237]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) Jul 10 17:56:04 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5250]: Received disconnect from 10.30.34.89 port 40702:11: disconnected by user Jul 10 17:56:04 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5250]: Disconnected from user root 10.30.34.89 port 40702 Jul 10 17:56:04 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5237]: pam_unix(sshd:session): session closed for user root Jul 10 17:56:04 ip-10-31-43-137.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. Jul 10 17:56:04 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: Session 1 logged out. Waiting for processes to exit. Jul 10 17:56:04 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: 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. Jul 10 17:56:10 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com irqbalance[603]: Cannot change IRQ 28 affinity: Operation not permitted Jul 10 17:56:10 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com irqbalance[603]: IRQ 28 affinity is now unmanaged Jul 10 17:56:14 ip-10-31-43-137.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 652. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: Activating special unit Exit the Session... Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 24 and the job result is done. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 28 and the job result is done. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 29 and the job result is done. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 17 and the job result is done. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 16 and the job result is done. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 27 and the job result is done. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 23 and the job result is done. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 26 and the job result is done. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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. Jul 10 17:56:14 ip-10-31-43-137.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. Jul 10 17:56:14 ip-10-31-43-137.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 652 and the job result is done. Jul 10 17:56:14 ip-10-31-43-137.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 653. Jul 10 17:56:14 ip-10-31-43-137.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. Jul 10 17:56:14 ip-10-31-43-137.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. Jul 10 17:56:14 ip-10-31-43-137.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 653 and the job result is done. Jul 10 17:56:14 ip-10-31-43-137.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 655 and the job result is done. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5287]: Accepted publickey for root from 10.31.8.121 port 37590 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5288]: Accepted publickey for root from 10.31.8.121 port 37592 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: 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 5287. Jul 10 17:56:15 ip-10-31-43-137.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 659. Jul 10 17:56:15 ip-10-31-43-137.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 658. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: 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 5288. Jul 10 17:56:15 ip-10-31-43-137.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 658. Jul 10 17:56:15 ip-10-31-43-137.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 657. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0) Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: Queued start job for default target Main User Target. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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 9. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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 9. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: Startup finished in 75ms. ░░ 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 75368 microseconds. Jul 10 17:56:15 ip-10-31-43-137.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 657. Jul 10 17:56:15 ip-10-31-43-137.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 725. Jul 10 17:56:15 ip-10-31-43-137.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 794. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5287]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5288]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5304]: Received disconnect from 10.31.8.121 port 37592:11: disconnected by user Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5304]: Disconnected from user root 10.31.8.121 port 37592 Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5288]: pam_unix(sshd:session): session closed for user root Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[1]: session-4.scope: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit session-4.scope has successfully entered the 'dead' state. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: Session 4 logged out. Waiting for processes to exit. Jul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: Removed session 4. ░░ Subject: Session 4 has been terminated ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A session with the ID 4 has been terminated. Jul 10 17:56:17 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sudo[5800]: root : PWD=/root ; USER=root ; COMMAND=/bin/true Jul 10 17:56:17 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sudo[5800]: pam_unix(sudo:session): session opened for user root(uid=0) by root(uid=0) Jul 10 17:56:17 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sudo[5800]: pam_unix(sudo:session): session closed for user root Jul 10 17:56:19 ip-10-31-43-137.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!) Jul 10 17:56:20 ip-10-31-43-137.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 863. Jul 10 17:56:21 ip-10-31-43-137.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 863. Jul 10 17:56:21 managed-node2 systemd-hostnamed[8033]: Hostname set to (static) Jul 10 17:56:21 managed-node2 NetworkManager[639]: [1783720581.0053] hostname: static hostname changed from "ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com" to "managed-node2" Jul 10 17:56:21 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 929. Jul 10 17:56:21 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 929. Jul 10 17:56:21 managed-node2 unknown: Leaving test '/Prepare-managed-node/tests/prep_managed_node' (serial number 1). (Be aware the test name is sanitized!) Jul 10 17:56:31 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. Jul 10 17:56:43 managed-node2 chronyd[612]: Selected source 38.45.67.7 (2.centos.pool.ntp.org) Jul 10 17:56:51 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. Jul 10 17:57:06 managed-node2 sshd-session[8742]: Accepted publickey for root from 10.31.41.91 port 38426 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE Jul 10 17:57:06 managed-node2 systemd-logind[607]: 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 8742. Jul 10 17:57:06 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 995. Jul 10 17:57:06 managed-node2 sshd-session[8742]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) Jul 10 17:57:06 managed-node2 sshd-session[8745]: Received disconnect from 10.31.41.91 port 38426:11: disconnected by user Jul 10 17:57:06 managed-node2 sshd-session[8745]: Disconnected from user root 10.31.41.91 port 38426 Jul 10 17:57:06 managed-node2 sshd-session[8742]: pam_unix(sshd:session): session closed for user root Jul 10 17:57:06 managed-node2 systemd[1]: session-6.scope: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit session-6.scope has successfully entered the 'dead' state. Jul 10 17:57:06 managed-node2 systemd-logind[607]: Session 6 logged out. Waiting for processes to exit. Jul 10 17:57:06 managed-node2 systemd-logind[607]: Removed session 6. ░░ Subject: Session 6 has been terminated ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A session with the ID 6 has been terminated. Jul 10 17:57:06 managed-node2 sshd-session[8769]: Accepted publickey for root from 10.31.41.91 port 38440 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE Jul 10 17:57:06 managed-node2 systemd-logind[607]: New session 7 of user root. ░░ Subject: A new session 7 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 7 has been created for the user root. ░░ ░░ The leading process of the session is 8769. Jul 10 17:57:06 managed-node2 systemd[1]: Started Session 7 of User root. ░░ Subject: A start job for unit session-7.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-7.scope has finished successfully. ░░ ░░ The job identifier is 1064. Jul 10 17:57:06 managed-node2 sshd-session[8769]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) Jul 10 17:57:06 managed-node2 sshd-session[8772]: Received disconnect from 10.31.41.91 port 38440:11: disconnected by user Jul 10 17:57:06 managed-node2 sshd-session[8772]: Disconnected from user root 10.31.41.91 port 38440 Jul 10 17:57:06 managed-node2 sshd-session[8769]: pam_unix(sshd:session): session closed for user root Jul 10 17:57:06 managed-node2 systemd[1]: session-7.scope: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit session-7.scope has successfully entered the 'dead' state. Jul 10 17:57:06 managed-node2 systemd-logind[607]: Session 7 logged out. Waiting for processes to exit. Jul 10 17:57:06 managed-node2 systemd-logind[607]: Removed session 7. ░░ Subject: Session 7 has been terminated ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A session with the ID 7 has been terminated. Jul 10 17:57:09 managed-node2 sshd-session[8798]: Accepted publickey for root from 10.31.41.91 port 38454 ssh2: ECDSA SHA256:8WqKavN+MmkbmRUBckBNpJdwML/N5YgGt4RNFPp+svU Jul 10 17:57:09 managed-node2 systemd-logind[607]: New session 8 of user root. ░░ Subject: A new session 8 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 8 has been created for the user root. ░░ ░░ The leading process of the session is 8798. Jul 10 17:57:09 managed-node2 systemd[1]: Started Session 8 of User root. ░░ Subject: A start job for unit session-8.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-8.scope has finished successfully. ░░ ░░ The job identifier is 1133. Jul 10 17:57:09 managed-node2 sshd-session[8798]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) Jul 10 17:57:11 managed-node2 python3.9[8975]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d Jul 10 17:57:11 managed-node2 python3.9[9150]: ansible-tempfile Invoked with state=directory prefix=lsr_ suffix=_podman path=None Jul 10 17:57:12 managed-node2 python3.9[9299]: ansible-file Invoked with path=/tmp/lsr_veqsgttx_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 Jul 10 17:57:13 managed-node2 python3.9[9448]: 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 Jul 10 17:57:13 managed-node2 useradd[9450]: new group: name=podman_basic_user, GID=3001 Jul 10 17:57:13 managed-node2 useradd[9450]: new user: name=podman_basic_user, UID=3001, GID=3001, home=/home/podman_basic_user, shell=/bin/bash, from=/dev/pts/0 Jul 10 17:57:13 managed-node2 python3.9[9605]: ansible-ansible.legacy.command Invoked with executable=/bin/bash _raw_params=set -uxo pipefail exec 1>&2 for file in /etc/containers/ansible-kubernetes.d/*; do if [ -f "$file" ]; then echo "File: $file" cat "$file" fi done _uses_shell=True expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None creates=None removes=None stdin=None Jul 10 17:57:14 managed-node2 python3.9[9755]: 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-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:518 Friday 10 July 2026 17:57:14 -0400 (0:00:00.422) 0:00:05.195 *********** ok: [managed-node2] => { "changed": false, "path": "/etc/containers/storage.conf", "state": "absent" } TASK [Clean up host directories] *********************************************** task path: /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:525 Friday 10 July 2026 17:57:14 -0400 (0:00:00.353) 0:00:05.548 *********** changed: [managed-node2] => { "changed": true, "path": "/tmp/lsr_veqsgttx_podman", "state": "absent" } TASK [Remove kube file src] **************************************************** task path: /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:532 Friday 10 July 2026 17:57:14 -0400 (0:00:00.360) 0:00:05.909 *********** changed: [managed-node2 -> localhost] => { "changed": true, "path": "/tmp/lsr_podman_o4gvu_d4.yml", "state": "absent" } PLAY RECAP ********************************************************************* managed-node2 : ok=10 changed=6 unreachable=0 failed=1 skipped=3 rescued=1 ignored=0 SYSTEM ROLES ERRORS BEGIN v1 [ { "ansible_version": "2.17.14", "end_time": "2026-07-10T21:57:13.409900+00:00Z", "host": "managed-node2", "message": "The task includes an option with an undefined variable.. {{ __start_marker }}\napiVersion: v1\nkind: ConfigMap\nmetadata:\n name: testfile3\ndata:\n testfile3.txt: |\n this is a test\n{{ __end_marker }}\n{{ __start_marker }}\napiVersion: v1\nkind: Pod\nmetadata:\n labels:\n app: test\n io.containers.autoupdate: registry\n name: httpd3\nspec:\n containers:\n - name: httpd3\n image: {{ test_image }}\n command:\n - /bin/busybox-extras\n - httpd\n - -f\n - -p\n - 80\n ports:\n - containerPort: 80\n hostPort: 15003\n volumeMounts:\n - mountPath: /var/www:Z\n name: www\n - mountPath: /var/httpd-create:Z\n name: create\n - mountPath: /etc/testfile3.txt:Z\n name: testfile3\n subPath: testfile3.txt\n workingDir: /var/www\n volumes:\n - name: www\n hostPath:\n path: \"{{ __test_tmpdir.path ~ '/httpd3' }}\"\n - name: create\n hostPath:\n path: \"{{ __test_tmpdir.path ~ '/httpd3-create' }}\"\n - name: testfile3\n configMap:\n name: testfile3\n{{ __end_marker }}\n: '__start_marker' is undefined\n\nThe error appears to be in '/tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml': line 221, column 11, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - name: Write kube_file_src\n ^ here\n", "start_time": "2026-07-10T21:57:13.396368+00:00Z", "task_name": "Write kube_file_src", "task_path": "/tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:221" }, { "ansible_version": "2.17.14", "delta": "0:00:00.035984", "end_time": "2026-07-10 17:57:14.192675", "host": "managed-node2", "message": "", "rc": 0, "start_time": "2026-07-10 17:57:14.156691", "stdout": "Jul 10 17:54:04 localhost kernel: Non-volatile memory driver v1.3\nJul 10 17:54:04 localhost kernel: rdac: device handler registered\nJul 10 17:54:04 localhost kernel: hp_sw: device handler registered\nJul 10 17:54:04 localhost kernel: emc: device handler registered\nJul 10 17:54:04 localhost kernel: alua: device handler registered\nJul 10 17:54:04 localhost kernel: usbcore: registered new interface driver usbserial_generic\nJul 10 17:54:04 localhost kernel: usbserial: USB Serial support registered for generic\nJul 10 17:54:04 localhost kernel: i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12\nJul 10 17:54:04 localhost kernel: i8042: Warning: Keylock active\nJul 10 17:54:04 localhost kernel: serio: i8042 KBD port at 0x60,0x64 irq 1\nJul 10 17:54:04 localhost kernel: serio: i8042 AUX port at 0x60,0x64 irq 12\nJul 10 17:54:04 localhost kernel: mousedev: PS/2 mouse device common for all mice\nJul 10 17:54:04 localhost kernel: rtc_cmos 00:00: RTC can wake from S4\nJul 10 17:54:04 localhost kernel: rtc_cmos 00:00: registered as rtc0\nJul 10 17:54:04 localhost kernel: rtc_cmos 00:00: setting system clock to 2026-07-10T21:54:02 UTC (1783720442)\nJul 10 17:54:04 localhost kernel: rtc_cmos 00:00: alarms up to one day, 114 bytes nvram\nJul 10 17:54:04 localhost kernel: intel_pstate: P-states controlled by the platform\nJul 10 17:54:04 localhost kernel: hid: raw HID events driver (C) Jiri Kosina\nJul 10 17:54:04 localhost kernel: usbcore: registered new interface driver usbhid\nJul 10 17:54:04 localhost kernel: usbhid: USB HID core driver\nJul 10 17:54:04 localhost kernel: drop_monitor: Initializing network drop monitor service\nJul 10 17:54:04 localhost kernel: Initializing XFRM netlink socket\nJul 10 17:54:04 localhost kernel: NET: Registered PF_INET6 protocol family\nJul 10 17:54:04 localhost kernel: Segment Routing with IPv6\nJul 10 17:54:04 localhost kernel: NET: Registered PF_PACKET protocol family\nJul 10 17:54:04 localhost kernel: mpls_gso: MPLS GSO support\nJul 10 17:54:04 localhost kernel: resctrl: No MBM correction factor available\nJul 10 17:54:04 localhost kernel: IPI shorthand broadcast: enabled\nJul 10 17:54:04 localhost kernel: AVX2 version of gcm_enc/dec engaged.\nJul 10 17:54:04 localhost kernel: AES CTR mode by8 optimization enabled\nJul 10 17:54:04 localhost kernel: sched_clock: Marking stable (1137482823, 924955257)->(2960230556, -897792476)\nJul 10 17:54:04 localhost kernel: registered taskstats version 1\nJul 10 17:54:04 localhost kernel: Loading compiled-in X.509 certificates\nJul 10 17:54:04 localhost kernel: Loaded X.509 cert 'The CentOS Project: CentOS Stream kernel signing key: 6b5ef142514248e1227595b1abbec48f1eefee95'\nJul 10 17:54:04 localhost kernel: Loaded X.509 cert 'Red Hat Enterprise Linux Driver Update Program (key 3): bf57f3e87362bc7229d9f465321773dfd1f77a80'\nJul 10 17:54:04 localhost kernel: Loaded X.509 cert 'Red Hat Enterprise Linux kpatch signing key: 4d38fd864ebe18c5f0b72e3852e2014c3a676fc8'\nJul 10 17:54:04 localhost kernel: Loaded X.509 cert 'RH-IMA-CA: Red Hat IMA CA: fb31825dd0e073685b264e3038963673f753959a'\nJul 10 17:54:04 localhost kernel: Loaded X.509 cert 'Nvidia GPU OOT signing 001: 55e1cef88193e60419f0b0ec379c49f77545acf0'\nJul 10 17:54:04 localhost kernel: Loaded X.509 cert 'NVIDIA Jetson SoC OOT signing 001: 7e60d156a289e05b18f70ac4a2d8296c5c8ab797'\nJul 10 17:54:04 localhost kernel: Loaded X.509 cert 'NVIDIA Bluefield DPU OOT signing 001: e251cec14b15b5d4c0e452770ca269261ea466bc'\nJul 10 17:54:04 localhost kernel: Demotion targets for Node 0: null\nJul 10 17:54:04 localhost kernel: page_owner is disabled\nJul 10 17:54:04 localhost kernel: Key type .fscrypt registered\nJul 10 17:54:04 localhost kernel: Key type fscrypt-provisioning registered\nJul 10 17:54:04 localhost kernel: Key type big_key registered\nJul 10 17:54:04 localhost kernel: Key type encrypted registered\nJul 10 17:54:04 localhost kernel: ima: No TPM chip found, activating TPM-bypass!\nJul 10 17:54:04 localhost kernel: Loading compiled-in module X.509 certificates\nJul 10 17:54:04 localhost kernel: Loaded X.509 cert 'The CentOS Project: CentOS Stream kernel signing key: 6b5ef142514248e1227595b1abbec48f1eefee95'\nJul 10 17:54:04 localhost kernel: ima: Allocated hash algorithm: sha256\nJul 10 17:54:04 localhost kernel: ima: No architecture policies found\nJul 10 17:54:04 localhost kernel: evm: Initialising EVM extended attributes:\nJul 10 17:54:04 localhost kernel: evm: security.selinux\nJul 10 17:54:04 localhost kernel: evm: security.SMACK64 (disabled)\nJul 10 17:54:04 localhost kernel: evm: security.SMACK64EXEC (disabled)\nJul 10 17:54:04 localhost kernel: evm: security.SMACK64TRANSMUTE (disabled)\nJul 10 17:54:04 localhost kernel: evm: security.SMACK64MMAP (disabled)\nJul 10 17:54:04 localhost kernel: evm: security.apparmor (disabled)\nJul 10 17:54:04 localhost kernel: evm: security.ima\nJul 10 17:54:04 localhost kernel: evm: security.capability\nJul 10 17:54:04 localhost kernel: evm: HMAC attrs: 0x1\nJul 10 17:54:04 localhost kernel: Running certificate verification RSA selftest\nJul 10 17:54:04 localhost kernel: Loaded X.509 cert 'Certificate verification self-testing key: f58703bb33ce1b73ee02eccdee5b8817518fe3db'\nJul 10 17:54:04 localhost kernel: Running certificate verification ECDSA selftest\nJul 10 17:54:04 localhost kernel: Loaded X.509 cert 'Certificate verification ECDSA self-testing key: 2900bcea1deb7bc8479a84a23d758efdfdd2b2d3'\nJul 10 17:54:04 localhost kernel: clk: Disabling unused clocks\nJul 10 17:54:04 localhost kernel: Freeing unused decrypted memory: 2028K\nJul 10 17:54:04 localhost kernel: Freeing unused kernel image (initmem) memory: 4224K\nJul 10 17:54:04 localhost kernel: Write protecting the kernel read-only data: 30720k\nJul 10 17:54:04 localhost kernel: Freeing unused kernel image (rodata/data gap) memory: 308K\nJul 10 17:54:04 localhost kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2\nJul 10 17:54:04 localhost kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.\nJul 10 17:54:04 localhost kernel: x86/mm: Checking user space page tables\nJul 10 17:54:04 localhost kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.\nJul 10 17:54:04 localhost kernel: Run /init as init process\nJul 10 17:54:04 localhost kernel: with arguments:\nJul 10 17:54:04 localhost kernel: /init\nJul 10 17:54:04 localhost kernel: rhgb\nJul 10 17:54:04 localhost kernel: with environment:\nJul 10 17:54:04 localhost kernel: HOME=/\nJul 10 17:54:04 localhost kernel: TERM=linux\nJul 10 17:54:04 localhost kernel: BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-5.14.0-721.el9.x86_64\nJul 10 17:54:04 localhost systemd[1]: systemd 252-71.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)\nJul 10 17:54:04 localhost systemd[1]: Detected virtualization amazon.\nJul 10 17:54:04 localhost systemd[1]: Detected architecture x86-64.\nJul 10 17:54:04 localhost systemd[1]: Running in initrd.\nJul 10 17:54:04 localhost systemd[1]: No hostname configured, using default hostname.\nJul 10 17:54:04 localhost systemd[1]: Hostname set to .\nJul 10 17:54:04 localhost systemd[1]: Queued start job for default target Initrd Default Target.\nJul 10 17:54:04 localhost systemd[1]: Started Dispatch Password Requests to Console Directory Watch.\nJul 10 17:54:04 localhost systemd[1]: Reached target Initrd /usr File System.\nJul 10 17:54:04 localhost systemd[1]: Reached target Local File Systems.\nJul 10 17:54:04 localhost systemd[1]: Reached target Path Units.\nJul 10 17:54:04 localhost systemd[1]: Reached target Slice Units.\nJul 10 17:54:04 localhost systemd[1]: Reached target Swaps.\nJul 10 17:54:04 localhost systemd[1]: Reached target Timer Units.\nJul 10 17:54:04 localhost systemd[1]: Listening on D-Bus System Message Bus Socket.\nJul 10 17:54:04 localhost systemd[1]: Listening on Journal Socket (/dev/log).\nJul 10 17:54:04 localhost systemd[1]: Listening on Journal Socket.\nJul 10 17:54:04 localhost systemd[1]: Listening on udev Control Socket.\nJul 10 17:54:04 localhost systemd[1]: Listening on udev Kernel Socket.\nJul 10 17:54:04 localhost systemd[1]: Reached target Socket Units.\nJul 10 17:54:04 localhost systemd[1]: Starting Create List of Static Device Nodes...\nJul 10 17:54:04 localhost systemd[1]: Starting Journal Service...\nJul 10 17:54:04 localhost systemd[1]: Load Kernel Modules was skipped because no trigger condition checks were met.\nJul 10 17:54:04 localhost systemd[1]: Starting Apply Kernel Variables...\nJul 10 17:54:04 localhost systemd[1]: Starting Create System Users...\nJul 10 17:54:04 localhost systemd[1]: Starting Setup Virtual Console...\nJul 10 17:54:04 localhost systemd[1]: Finished Create List of Static Device Nodes.\nJul 10 17:54:04 localhost kernel: input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4\nJul 10 17:54:04 localhost systemd[1]: Finished Apply Kernel Variables.\nJul 10 17:54:04 localhost systemd[1]: Finished Create System Users.\nJul 10 17:54:04 localhost systemd[1]: Starting Create Static Device Nodes in /dev...\nJul 10 17:54:04 localhost systemd[1]: Finished Create Static Device Nodes in /dev.\nJul 10 17:54:04 localhost systemd-journald[233]: 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.\nJul 10 17:54:04 localhost systemd-journald[233]: Runtime Journal (/run/log/journal/3904df565a3f4d0d8d3c70085470592d) is 8.0M, max 68.3M, 60.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/3904df565a3f4d0d8d3c70085470592d) is currently using 8.0M.\n\u2591\u2591 Maximum allowed usage is set to 68.3M.\n\u2591\u2591 Leaving at least 34.1M free (of currently available 675.0M of disk space).\n\u2591\u2591 Enforced usage limit is thus 68.3M, of which 60.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.\nJul 10 17:54:03 localhost systemd-sysusers[235]: Creating group 'nobody' with GID 65534.\nJul 10 17:54:03 localhost systemd-sysusers[235]: Creating group 'users' with GID 100.\nJul 10 17:54:03 localhost systemd-sysusers[235]: Creating group 'dbus' with GID 81.\nJul 10 17:54:03 localhost systemd-sysusers[235]: Creating user 'dbus' (System Message Bus) with UID 81 and GID 81.\nJul 10 17:54:04 localhost systemd[1]: Started Journal Service.\nJul 10 17:54:04 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 24.\nJul 10 17:54:04 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 24.\nJul 10 17:54:04 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 49.\nJul 10 17:54:04 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 48.\nJul 10 17:54:04 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 33.\nJul 10 17:54:04 localhost dracut-cmdline[248]: dracut-9 dracut-057-118.git20260624.el9\nJul 10 17:54:04 localhost dracut-cmdline[248]: Using kernel command line parameters: BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-5.14.0-721.el9.x86_64 root=UUID=7c0d6762-a0be-4063-a43a-c35e843399f8 ro rhgb crashkernel=1G-2G:192M,2G-64G:256M,64G-:512M net.ifnames=0 console=tty0 console=ttyS0,115200n8\nJul 10 17:54:04 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 33.\nJul 10 17:54:04 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 32.\nJul 10 17:54:04 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 32.\nJul 10 17:54:04 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 17.\nJul 10 17:54:04 localhost systemd-udevd[329]: Using default interface naming scheme 'rhel-9.0'.\nJul 10 17:54:04 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 17.\nJul 10 17:54:04 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 50.\nJul 10 17:54:04 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 21.\nJul 10 17:54:04 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 21.\nJul 10 17:54:04 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.\nJul 10 17:54:04 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.\nJul 10 17:54:04 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 43.\nJul 10 17:54:04 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 45.\nJul 10 17:54:04 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 42.\nJul 10 17:54:04 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 40.\nJul 10 17:54:04 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 23.\nJul 10 17:54:04 localhost systemd[1]: Created slice Slice /system/modprobe.\n\u2591\u2591 Subject: A start job for unit system-modprobe.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 system-modprobe.slice has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 59.\nJul 10 17:54:04 localhost rngd[348]: Disabling 7: PKCS11 Entropy generator (pkcs11)\nJul 10 17:54:04 localhost rngd[348]: Disabling 5: NIST Network Entropy Beacon (nist)\nJul 10 17:54:04 localhost rngd[348]: Disabling 9: Qrypt quantum entropy beacon (qrypt)\nJul 10 17:54:04 localhost rngd[348]: Initializing available sources\nJul 10 17:54:04 localhost rngd[348]: [hwrng ]: Initialization Failed\nJul 10 17:54:04 localhost rngd[348]: [rdrand]: Enabling RDSEED rng support\nJul 10 17:54:04 localhost rngd[348]: [rdrand]: Initialized\nJul 10 17:54:04 localhost rngd[348]: [jitter]: JITTER timeout set to 5 sec\nJul 10 17:54:04 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 58.\nJul 10 17:54:04 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.\nJul 10 17:54:04 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 58.\nJul 10 17:54:04 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 56.\nJul 10 17:54:04 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 56.\nJul 10 17:54:04 localhost rngd[348]: [jitter]: Initializing AES buffer\nJul 10 17:54:04 localhost kernel: Key type psk registered\nJul 10 17:54:04 localhost kernel: ena 0000:00:05.0: ENA device version: 0.10\nJul 10 17:54:04 localhost kernel: ena 0000:00:05.0: ENA controller version: 0.0.1 implementation version 1\nJul 10 17:54:04 localhost kernel: ena 0000:00:05.0: Elastic Network Adapter (ENA) found at mem febf4000, mac addr 0e:26:17:53:a2:a3\nJul 10 17:54:04 localhost systemd-udevd[332]: Network interface NamePolicy= disabled on kernel command line.\nJul 10 17:54:04 localhost kernel: nvme nvme0: pci function 0000:00:04.0\nJul 10 17:54:04 localhost kernel: ACPI: \\_SB_.LNKD: Enabled at IRQ 11\nJul 10 17:54:04 localhost kernel: nvme nvme0: 2/0/0 default/read/poll queues\nJul 10 17:54:04 localhost kernel: nvme0n1: p1\nJul 10 17:54:05 localhost systemd[1]: Found device Amazon Elastic Block Store 1.\n\u2591\u2591 Subject: A start job for unit dev-disk-by\\x2duuid-7c0d6762\\x2da0be\\x2d4063\\x2da43a\\x2dc35e843399f8.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-7c0d6762\\x2da0be\\x2d4063\\x2da43a\\x2dc35e843399f8.device has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 38.\nJul 10 17:54:05 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 55.\nJul 10 17:54:06 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 40.\nJul 10 17:54:06 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 41.\nJul 10 17:54:06 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 47.\nJul 10 17:54:06 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 34.\nJul 10 17:54:06 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 34.\nJul 10 17:54:06 localhost systemd[1]: Starting File System Check on /dev/disk/by-uuid/7c0d6762-a0be-4063-a43a-c35e843399f8...\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 37.\nJul 10 17:54:06 localhost systemd-fsck[397]: /usr/sbin/fsck.xfs: XFS file system.\nJul 10 17:54:06 localhost systemd[1]: Finished File System Check on /dev/disk/by-uuid/7c0d6762-a0be-4063-a43a-c35e843399f8.\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 37.\nJul 10 17:54:06 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 36.\nJul 10 17:54:06 localhost kernel: SGI XFS with ACLs, security attributes, scrub, quota, no debug enabled\nJul 10 17:54:06 localhost kernel: XFS (nvme0n1p1): Mounting V5 Filesystem 7c0d6762-a0be-4063-a43a-c35e843399f8\nJul 10 17:54:07 localhost kernel: XFS (nvme0n1p1): Ending clean mount\nJul 10 17:54:07 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 36.\nJul 10 17:54:07 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 51.\nJul 10 17:54:07 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 53.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 53.\nJul 10 17:54:07 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 52.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 54.\nJul 10 17:54:07 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 46.\nJul 10 17:54:07 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 46.\nJul 10 17:54:07 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 62.\nJul 10 17:54:07 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 109 and the job result is done.\nJul 10 17:54:07 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 110 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 116 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 112 and the job result is done.\nJul 10 17:54:07 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 98 and the job result is done.\nJul 10 17:54:07 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 120 and the job result is done.\nJul 10 17:54:07 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 99 and the job result is done.\nJul 10 17:54:07 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 125 and the job result is done.\nJul 10 17:54:07 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 123 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 100 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 115 and the job result is done.\nJul 10 17:54:07 localhost systemd[1]: Stopping Hardware RNG Entropy Gatherer Daemon...\n\u2591\u2591 Subject: A stop job for unit rngd.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 rngd.service has begun execution.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 102.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 97 and the job result is done.\nJul 10 17:54:07 localhost systemd[1]: rngd.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 rngd.service has successfully entered the 'dead' state.\nJul 10 17:54:07 localhost systemd[1]: Stopped Hardware RNG Entropy Gatherer Daemon.\n\u2591\u2591 Subject: A stop job for unit rngd.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 rngd.service has finished.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 102 and the job result is done.\nJul 10 17:54:07 localhost systemd[1]: rngd.service: Consumed 4.077s CPU time.\n\u2591\u2591 Subject: Resources consumed by unit runtime\n\u2591\u2591 Defined-By: systemd\n\u2591\u2591 Support: https://access.redhat.com/support\n\u2591\u2591 \n\u2591\u2591 The unit rngd.service completed and consumed the indicated resources.\nJul 10 17:54:07 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 105 and the job result is done.\nJul 10 17:54:07 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 111 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 104 and the job result is done.\nJul 10 17:54:07 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 106 and the job result is done.\nJul 10 17:54:07 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 101 and the job result is done.\nJul 10 17:54:07 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 121 and the job result is done.\nJul 10 17:54:07 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 103 and the job result is done.\nJul 10 17:54:07 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 108 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 107 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 96 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 70 and the job result is done.\nJul 10 17:54:07 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 72.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 62.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 72 and the job result is done.\nJul 10 17:54:07 localhost systemd[1]: systemd-udevd.service: Consumed 1.082s CPU time.\n\u2591\u2591 Subject: Resources consumed by unit runtime\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 completed and consumed the indicated resources.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 73 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 114 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 113 and the job result is done.\nJul 10 17:54:07 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 66.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 93 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 124 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 95 and the job result is done.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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.\nJul 10 17:54:07 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 66.\nJul 10 17:54:07 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 65.\nJul 10 17:54:07 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 74.\nJul 10 17:54:07 localhost systemd[1]: Switching root.\nJul 10 17:54:07 localhost systemd-journald[233]: 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.\nJul 10 17:54:18 localhost systemd-journald[233]: Received SIGTERM from PID 1 (systemd).\nJul 10 17:54:18 localhost kernel: audit: type=1404 audit(1783720453.249:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1\nJul 10 17:54:18 localhost kernel: SELinux: policy capability network_peer_controls=1\nJul 10 17:54:18 localhost kernel: SELinux: policy capability open_perms=1\nJul 10 17:54:18 localhost kernel: SELinux: policy capability extended_socket_class=1\nJul 10 17:54:18 localhost kernel: SELinux: policy capability always_check_network=0\nJul 10 17:54:18 localhost kernel: SELinux: policy capability cgroup_seclabel=1\nJul 10 17:54:18 localhost kernel: SELinux: policy capability nnp_nosuid_transition=1\nJul 10 17:54:18 localhost kernel: SELinux: policy capability genfs_seclabel_symlinks=1\nJul 10 17:54:18 localhost kernel: audit: type=1403 audit(1783720453.966:3): auid=4294967295 ses=4294967295 lsm=selinux res=1\nJul 10 17:54:18 localhost systemd[1]: Successfully loaded SELinux policy in 842.753ms.\nJul 10 17:54:18 localhost systemd[1]: Relabelled /dev, /dev/shm, /run, /sys/fs/cgroup in 19.316ms.\nJul 10 17:54:18 localhost systemd[1]: systemd 252-71.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)\nJul 10 17:54:18 localhost systemd[1]: Detected virtualization amazon.\nJul 10 17:54:18 localhost systemd[1]: Detected architecture x86-64.\nJul 10 17:54:18 localhost systemd[1]: Initializing machine ID from VM UUID.\nJul 10 17:54:18 localhost systemd[1]: Installed transient /etc/machine-id file.\nJul 10 17:54:18 localhost systemd-rc-local-generator[463]: /etc/rc.d/rc.local is not marked executable, skipping.\nJul 10 17:54:18 localhost systemd[1]: initrd-switch-root.service: Deactivated successfully.\nJul 10 17:54:18 localhost systemd[1]: Stopped Switch Root.\nJul 10 17:54:18 localhost systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.\nJul 10 17:54:18 localhost systemd[1]: Created slice Slice /system/getty.\nJul 10 17:54:18 localhost systemd[1]: Created slice Slice /system/serial-getty.\nJul 10 17:54:18 localhost systemd[1]: Created slice Slice /system/sshd-keygen.\nJul 10 17:54:18 localhost systemd[1]: Created slice User and Session Slice.\nJul 10 17:54:18 localhost systemd[1]: Started Dispatch Password Requests to Console Directory Watch.\nJul 10 17:54:18 localhost systemd[1]: Started Forward Password Requests to Wall Directory Watch.\nJul 10 17:54:18 localhost systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.\nJul 10 17:54:18 localhost systemd[1]: Reached target Local Encrypted Volumes.\nJul 10 17:54:18 localhost systemd[1]: Stopped target Switch Root.\nJul 10 17:54:18 localhost systemd[1]: Stopped target Initrd File Systems.\nJul 10 17:54:18 localhost systemd[1]: Stopped target Initrd Root File System.\nJul 10 17:54:18 localhost systemd[1]: Reached target Local Integrity Protected Volumes.\nJul 10 17:54:18 localhost systemd[1]: Reached target Path Units.\nJul 10 17:54:18 localhost systemd[1]: Reached target Slice Units.\nJul 10 17:54:18 localhost systemd[1]: Reached target Swaps.\nJul 10 17:54:18 localhost systemd[1]: Reached target Local Verity Protected Volumes.\nJul 10 17:54:18 localhost systemd[1]: Listening on RPCbind Server Activation Socket.\nJul 10 17:54:18 localhost systemd[1]: Reached target RPC Port Mapper.\nJul 10 17:54:18 localhost systemd[1]: Listening on Process Core Dump Socket.\nJul 10 17:54:18 localhost systemd[1]: Listening on initctl Compatibility Named Pipe.\nJul 10 17:54:18 localhost systemd[1]: Listening on udev Control Socket.\nJul 10 17:54:18 localhost systemd[1]: Listening on udev Kernel Socket.\nJul 10 17:54:18 localhost systemd[1]: Mounting Huge Pages File System...\nJul 10 17:54:18 localhost systemd[1]: Mounting POSIX Message Queue File System...\nJul 10 17:54:18 localhost systemd[1]: Mounting Kernel Debug File System...\nJul 10 17:54:18 localhost systemd[1]: Mounting Kernel Trace File System...\nJul 10 17:54:18 localhost systemd[1]: Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab).\nJul 10 17:54:18 localhost systemd[1]: Starting Create List of Static Device Nodes...\nJul 10 17:54:18 localhost systemd[1]: Starting Load Kernel Module configfs...\nJul 10 17:54:18 localhost systemd[1]: Starting Load Kernel Module drm...\nJul 10 17:54:18 localhost systemd[1]: Starting Load Kernel Module efi_pstore...\nJul 10 17:54:18 localhost systemd[1]: Starting Load Kernel Module fuse...\nJul 10 17:54:18 localhost systemd[1]: Starting Read and set NIS domainname from /etc/sysconfig/network...\nJul 10 17:54:18 localhost systemd[1]: systemd-fsck-root.service: Deactivated successfully.\nJul 10 17:54:18 localhost systemd[1]: Stopped File System Check on Root Device.\nJul 10 17:54:18 localhost systemd[1]: Stopped Journal Service.\nJul 10 17:54:18 localhost systemd[1]: Starting Journal Service...\nJul 10 17:54:18 localhost systemd[1]: Load Kernel Modules was skipped because no trigger condition checks were met.\nJul 10 17:54:18 localhost systemd[1]: Starting Generate network units from Kernel command line...\nJul 10 17:54:18 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).\nJul 10 17:54:18 localhost systemd[1]: Starting Remount Root and Kernel File Systems...\nJul 10 17:54:18 localhost systemd[1]: Repartition Root Disk was skipped because no trigger condition checks were met.\nJul 10 17:54:18 localhost kernel: fuse: init (API version 7.37)\nJul 10 17:54:18 localhost systemd[1]: Starting Apply Kernel Variables...\nJul 10 17:54:18 localhost systemd[1]: Starting Coldplug All udev Devices...\nJul 10 17:54:18 localhost systemd-journald[509]: 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.\nJul 10 17:54:18 localhost systemd-journald[509]: Runtime Journal (/run/log/journal/ec2f5b688767bfa432bd0e242a9410c2) is 8.0M, max 68.3M, 60.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/ec2f5b688767bfa432bd0e242a9410c2) is currently using 8.0M.\n\u2591\u2591 Maximum allowed usage is set to 68.3M.\n\u2591\u2591 Leaving at least 34.1M free (of currently available 667.0M of disk space).\n\u2591\u2591 Enforced usage limit is thus 68.3M, of which 60.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.\nJul 10 17:54:17 localhost systemd[1]: Queued start job for default target Multi-User System.\nJul 10 17:54:18 localhost systemd[1]: Mounted Huge Pages File System.\nJul 10 17:54:18 localhost systemd[1]: Started Journal Service.\nJul 10 17:54:17 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.\nJul 10 17:54:18 localhost systemd[1]: Mounted POSIX Message Queue File System.\n\u2591\u2591 Subject: A start job for unit dev-mqueue.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 dev-mqueue.mount has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 191.\nJul 10 17:54:18 localhost systemd[1]: Mounted Kernel Debug File System.\n\u2591\u2591 Subject: A start job for unit sys-kernel-debug.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-debug.mount has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 171.\nJul 10 17:54:18 localhost systemd[1]: Mounted Kernel Trace File System.\n\u2591\u2591 Subject: A start job for unit sys-kernel-tracing.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-tracing.mount has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 137.\nJul 10 17:54:18 localhost kernel: ACPI: bus type drm_connector registered\nJul 10 17:54:18 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 142.\nJul 10 17:54:18 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.\nJul 10 17:54:18 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 180.\nJul 10 17:54:18 localhost systemd[1]: modprobe@drm.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@drm.service has successfully entered the 'dead' state.\nJul 10 17:54:18 localhost systemd[1]: Finished Load Kernel Module drm.\n\u2591\u2591 Subject: A start job for unit modprobe@drm.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@drm.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 214.\nJul 10 17:54:18 localhost systemd[1]: modprobe@efi_pstore.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@efi_pstore.service has successfully entered the 'dead' state.\nJul 10 17:54:18 localhost systemd[1]: Finished Load Kernel Module efi_pstore.\n\u2591\u2591 Subject: A start job for unit modprobe@efi_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 modprobe@efi_pstore.service has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 147.\nJul 10 17:54:18 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.\nJul 10 17:54:18 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 155.\nJul 10 17:54:18 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 157.\nJul 10 17:54:18 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 172.\nJul 10 17:54:18 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 134.\nJul 10 17:54:18 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 154.\nJul 10 17:54:18 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 167.\nJul 10 17:54:18 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 170.\nJul 10 17:54:18 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 176.\nJul 10 17:54:18 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 146.\nJul 10 17:54:18 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 189.\nJul 10 17:54:18 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 140.\nJul 10 17:54:18 localhost systemd-journald[509]: Runtime Journal (/run/log/journal/ec2f5b688767bfa432bd0e242a9410c2) is 8.0M, max 68.3M, 60.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/ec2f5b688767bfa432bd0e242a9410c2) is currently using 8.0M.\n\u2591\u2591 Maximum allowed usage is set to 68.3M.\n\u2591\u2591 Leaving at least 34.1M free (of currently available 667.0M of disk space).\n\u2591\u2591 Enforced usage limit is thus 68.3M, of which 60.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.\nJul 10 17:54:18 localhost systemd-journald[509]: Received client request to flush runtime journal.\nJul 10 17:54:18 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 175.\nJul 10 17:54:18 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 154.\nJul 10 17:54:18 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 176.\nJul 10 17:54:18 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 153.\nJul 10 17:54:18 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 189.\nJul 10 17:54:18 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 168.\nJul 10 17:54:18 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 181.\nJul 10 17:54:18 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 175.\nJul 10 17:54:18 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 135.\nJul 10 17:54:18 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 133.\nJul 10 17:54:18 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 151.\nJul 10 17:54:18 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 145.\nJul 10 17:54:18 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 152.\nJul 10 17:54:18 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 150.\nJul 10 17:54:18 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 190.\nJul 10 17:54:18 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 187.\nJul 10 17:54:18 localhost bootctl[522]: Couldn't find EFI system partition, skipping.\nJul 10 17:54:18 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 143.\nJul 10 17:54:18 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 182.\nJul 10 17:54:18 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 190.\nJul 10 17:54:18 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 187.\nJul 10 17:54:18 localhost systemd-udevd[526]: Using default interface naming scheme 'rhel-9.0'.\nJul 10 17:54:19 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 143.\nJul 10 17:54:19 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 231.\nJul 10 17:54:19 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 211.\nJul 10 17:54:19 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 149.\nJul 10 17:54:19 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 174.\nJul 10 17:54:19 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 182.\nJul 10 17:54:19 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 273.\nJul 10 17:54:19 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.\nJul 10 17:54:19 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 273.\nJul 10 17:54:19 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 224.\nJul 10 17:54:19 localhost kernel: input: PC Speaker as /devices/platform/pcspkr/input/input5\nJul 10 17:54:19 localhost nfsrahead[553]: skipping non-NFS device 259:0\nJul 10 17:54:19 localhost kernel: parport_pc 00:03: reported by Plug and Play ACPI\nJul 10 17:54:19 localhost kernel: ppdev: user-space parallel port driver\nJul 10 17:54:19 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.\nJul 10 17:54:19 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 247.\nJul 10 17:54:19 localhost kernel: piix4_smbus 0000:00:01.3: SMBus Host Controller at 0xb100, revision 255\nJul 10 17:54:19 localhost kernel: i2c i2c-0: 1/1 memory slots populated (from DMI)\nJul 10 17:54:19 localhost kernel: i2c i2c-0: Failed! (ff)\nJul 10 17:54:19 localhost kernel: RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer\nJul 10 17:54:19 localhost auditd[562]: No plugins found, not dispatching events\nJul 10 17:54:19 localhost systemd-udevd[535]: Network interface NamePolicy= disabled on kernel command line.\nJul 10 17:54:19 localhost auditd[562]: Init complete, auditd 3.1.5 listening for events (startup state enable)\nJul 10 17:54:19 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 211.\nJul 10 17:54:19 localhost kernel: RPC: Registered named UNIX socket transport module.\nJul 10 17:54:19 localhost kernel: RPC: Registered udp transport module.\nJul 10 17:54:19 localhost kernel: RPC: Registered tcp transport module.\nJul 10 17:54:19 localhost kernel: RPC: Registered tcp-with-tls transport module.\nJul 10 17:54:19 localhost kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.\nJul 10 17:54:19 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 247.\nJul 10 17:54:19 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 246.\nJul 10 17:54:19 localhost augenrules[566]: /sbin/augenrules: No change\nJul 10 17:54:19 localhost augenrules[586]: No rules\nJul 10 17:54:19 localhost augenrules[586]: enabled 1\nJul 10 17:54:19 localhost augenrules[586]: failure 1\nJul 10 17:54:19 localhost augenrules[586]: pid 562\nJul 10 17:54:19 localhost augenrules[586]: rate_limit 0\nJul 10 17:54:19 localhost augenrules[586]: backlog_limit 8192\nJul 10 17:54:19 localhost augenrules[586]: lost 0\nJul 10 17:54:19 localhost augenrules[586]: backlog 3\nJul 10 17:54:19 localhost augenrules[586]: backlog_wait_time 60000\nJul 10 17:54:19 localhost augenrules[586]: backlog_wait_time_actual 0\nJul 10 17:54:19 localhost augenrules[586]: enabled 1\nJul 10 17:54:19 localhost augenrules[586]: failure 1\nJul 10 17:54:19 localhost augenrules[586]: pid 562\nJul 10 17:54:19 localhost augenrules[586]: rate_limit 0\nJul 10 17:54:19 localhost augenrules[586]: backlog_limit 8192\nJul 10 17:54:19 localhost augenrules[586]: lost 0\nJul 10 17:54:19 localhost augenrules[586]: backlog 3\nJul 10 17:54:19 localhost augenrules[586]: backlog_wait_time 60000\nJul 10 17:54:19 localhost augenrules[586]: backlog_wait_time_actual 0\nJul 10 17:54:19 localhost augenrules[586]: enabled 1\nJul 10 17:54:19 localhost augenrules[586]: failure 1\nJul 10 17:54:19 localhost augenrules[586]: pid 562\nJul 10 17:54:19 localhost augenrules[586]: rate_limit 0\nJul 10 17:54:19 localhost augenrules[586]: backlog_limit 8192\nJul 10 17:54:19 localhost augenrules[586]: lost 0\nJul 10 17:54:19 localhost augenrules[586]: backlog 3\nJul 10 17:54:19 localhost augenrules[586]: backlog_wait_time 60000\nJul 10 17:54:19 localhost augenrules[586]: backlog_wait_time_actual 0\nJul 10 17:54:19 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 231.\nJul 10 17:54:19 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 226.\nJul 10 17:54:20 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 226.\nJul 10 17:54:20 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 130.\nJul 10 17:54:20 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 195.\nJul 10 17:54:20 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 194.\nJul 10 17:54:20 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 193.\nJul 10 17:54:20 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 192.\nJul 10 17:54:20 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 199.\nJul 10 17:54:20 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 207.\nJul 10 17:54:20 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 205.\nJul 10 17:54:20 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 200.\nJul 10 17:54:20 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 138.\nJul 10 17:54:20 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 200.\nJul 10 17:54:20 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 127.\nJul 10 17:54:20 localhost dbus-broker-lau[598]: Ready\nJul 10 17:54:20 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 257.\nJul 10 17:54:20 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 252.\nJul 10 17:54:20 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 131.\nJul 10 17:54:20 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 238.\nJul 10 17:54:20 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 202.\nJul 10 17:54:20 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 216.\nJul 10 17:54:20 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 236.\nJul 10 17:54:20 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 234.\nJul 10 17:54:20 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 237.\nJul 10 17:54:20 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 233.\nJul 10 17:54:20 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 227.\nJul 10 17:54:20 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 228.\nJul 10 17:54:20 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 213.\nJul 10 17:54:20 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 279.\nJul 10 17:54:20 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 131.\nJul 10 17:54:20 localhost systemd-logind[607]: Watching system buttons on /dev/input/event0 (Power Button)\nJul 10 17:54:20 localhost systemd-logind[607]: Watching system buttons on /dev/input/event1 (Sleep Button)\nJul 10 17:54:20 localhost systemd-logind[607]: Watching system buttons on /dev/input/event2 (AT Translated Set 2 keyboard)\nJul 10 17:54:20 localhost systemd-logind[607]: 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.\nJul 10 17:54:20 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 213.\nJul 10 17:54:21 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.\nJul 10 17:54:21 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 279.\nJul 10 17:54:21 localhost chronyd[612]: chronyd version 4.8 starting (+CMDMON +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +NTS +SECHASH +IPV6 +DEBUG)\nJul 10 17:54:21 localhost chronyd[612]: Loaded 0 symmetric keys\nJul 10 17:54:21 localhost chronyd[612]: Using right/UTC timezone to obtain leap second data\nJul 10 17:54:21 localhost chronyd[612]: Frequency 0.000 +/- 1000000.000 ppm read from /var/lib/chrony/drift\nJul 10 17:54:21 localhost chronyd[612]: Loaded seccomp filter (level 2)\nJul 10 17:54:21 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 257.\nJul 10 17:54:21 localhost rngd[606]: Disabling 7: PKCS11 Entropy generator (pkcs11)\nJul 10 17:54:21 localhost rngd[606]: Disabling 5: NIST Network Entropy Beacon (nist)\nJul 10 17:54:21 localhost rngd[606]: Disabling 9: Qrypt quantum entropy beacon (qrypt)\nJul 10 17:54:21 localhost rngd[606]: Disabling 10: Named pipe entropy input (namedpipe)\nJul 10 17:54:21 localhost rngd[606]: Disabling 6: JITTER Entropy generator (jitter)\nJul 10 17:54:21 localhost rngd[606]: Disabling 11: Radiacode radiation detector entropy source (radiacode)\nJul 10 17:54:21 localhost rngd[606]: Disabling 8: RTLSDR software defined radio generator (rtlsdr)\nJul 10 17:54:21 localhost rngd[606]: Initializing available sources\nJul 10 17:54:21 localhost rngd[606]: [hwrng ]: Initialization Failed\nJul 10 17:54:21 localhost rngd[606]: [rdrand]: Enabling RDSEED rng support\nJul 10 17:54:21 localhost rngd[606]: [rdrand]: Initialized\nJul 10 17:54:21 localhost rngd[606]: Process privileges have been dropped to 2:2\nJul 10 17:54:24 localhost cloud-init[616]: Cloud-init v. 24.4-8.el9.1 running 'init-local' at Fri, 10 Jul 2026 21:54:24 +0000. Up 22.86 seconds.\nJul 10 17:54:24 localhost dhclient[620]: Internet Systems Consortium DHCP Client 4.4.2b1\nJul 10 17:54:24 localhost dhclient[620]: Copyright 2004-2019 Internet Systems Consortium.\nJul 10 17:54:24 localhost dhclient[620]: All rights reserved.\nJul 10 17:54:24 localhost dhclient[620]: For info, please visit https://www.isc.org/software/dhcp/\nJul 10 17:54:24 localhost dhclient[620]: \nJul 10 17:54:24 localhost dhclient[620]: Listening on LPF/eth0/0e:26:17:53:a2:a3\nJul 10 17:54:24 localhost dhclient[620]: Sending on LPF/eth0/0e:26:17:53:a2:a3\nJul 10 17:54:24 localhost dhclient[620]: Sending on Socket/fallback\nJul 10 17:54:24 localhost dhclient[620]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 (xid=0x73669b62)\nJul 10 17:54:24 localhost dhclient[620]: DHCPOFFER of 10.31.43.137 from 10.31.40.1\nJul 10 17:54:24 localhost dhclient[620]: DHCPREQUEST for 10.31.43.137 on eth0 to 255.255.255.255 port 67 (xid=0x73669b62)\nJul 10 17:54:24 localhost dhclient[620]: DHCPACK of 10.31.43.137 from 10.31.40.1 (xid=0x73669b62)\nJul 10 17:54:24 localhost dhclient[620]: bound to 10.31.43.137 -- renewal in 1399 seconds.\nJul 10 17:54:25 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 344.\nJul 10 17:54:25 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 344.\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-hostnamed[635]: Hostname set to (static)\nJul 10 17:54:25 ip-10-31-43-137.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 252.\nJul 10 17:54:25 ip-10-31-43-137.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 173.\nJul 10 17:54:25 ip-10-31-43-137.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 198.\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6675] NetworkManager (version 1.54.4-2.el9) is starting... (boot:50eb0d97-b313-41b1-8455-cf0354e5b387)\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6677] Read config: /etc/NetworkManager/NetworkManager.conf, /run/NetworkManager/conf.d/15-carrier-timeout.conf\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6782] manager[0x55e40ef57000]: monitoring kernel firmware directory '/lib/firmware'.\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6812] hostname: hostname: using hostnamed\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6812] hostname: static hostname changed from (none) to \"ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com\"\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.6817] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto)\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.8068] manager[0x55e40ef57000]: rfkill: Wi-Fi hardware radio set enabled\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.8069] manager[0x55e40ef57000]: rfkill: WWAN hardware radio set enabled\nJul 10 17:54:25 ip-10-31-43-137.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 411.\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9465] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.54.4-2.el9/libnm-device-plugin-team.so)\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9467] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9468] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9468] manager: Networking is enabled by state file\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9476] settings: Loaded settings plugin: keyfile (internal)\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9512] settings: Loaded settings plugin: ifcfg-rh (\"/usr/lib64/NetworkManager/1.54.4-2.el9/libnm-settings-plugin-ifcfg-rh.so\")\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9542] Warning: the ifcfg-rh plugin is deprecated, please migrate connections to the keyfile format using \"nmcli connection migrate\"\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9557] dhcp: init: Using DHCP client 'internal'\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9560] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9570] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9581] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')\nJul 10 17:54:25 ip-10-31-43-137.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 418.\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9619] device (lo): Activation: starting connection 'lo' (302ef318-820a-4c31-bc97-abc1be340944)\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9625] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9629] device (eth0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')\nJul 10 17:54:25 ip-10-31-43-137.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 198.\nJul 10 17:54:25 ip-10-31-43-137.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 201.\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9718] bus-manager: acquired D-Bus service \"org.freedesktop.NetworkManager\"\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9724] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9730] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9733] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9736] device (eth0): carrier: link connected\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9738] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9745] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9750] policy: auto-activating connection 'System eth0' (5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03)\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9755] device (eth0): Activation: starting connection 'System eth0' (5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03)\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9756] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9758] manager: NetworkManager state is now CONNECTING\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9760] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')\nJul 10 17:54:25 ip-10-31-43-137.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 197.\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9786] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9790] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9804] dhcp4 (eth0): state changed new lease, address=10.31.43.137\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9819] policy: set 'System eth0' (eth0) as default for IPv4 routing and DNS\nJul 10 17:54:25 ip-10-31-43-137.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 244.\nJul 10 17:54:25 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720465.9898] device (eth0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')\nJul 10 17:54:26 ip-10-31-43-137.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 244.\nJul 10 17:54:26 ip-10-31-43-137.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 245.\nJul 10 17:54:26 ip-10-31-43-137.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 241.\nJul 10 17:54:26 ip-10-31-43-137.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 249.\nJul 10 17:54:26 ip-10-31-43-137.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 256.\nJul 10 17:54:26 ip-10-31-43-137.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 186.\nJul 10 17:54:26 ip-10-31-43-137.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 418.\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2078] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2081] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2090] device (lo): Activation: successful, device activated.\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2125] device (eth0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2129] device (eth0): state change: secondaries -> activated (reason 'none', managed-type: 'full')\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2135] manager: NetworkManager state is now CONNECTED_SITE\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2154] device (eth0): Activation: successful, device activated.\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2164] manager: NetworkManager state is now CONNECTED_GLOBAL\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com NetworkManager[639]: [1783720466.2170] manager: startup complete\nJul 10 17:54:26 ip-10-31-43-137.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 197.\nJul 10 17:54:26 ip-10-31-43-137.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 251.\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: Added source 10.11.160.238\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: Added source 10.18.100.10\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: Added source 10.2.32.37\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: Added source 10.2.32.38\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Cloud-init v. 24.4-8.el9.1 running 'init' at Fri, 10 Jul 2026 21:54:26 +0000. Up 25.07 seconds.\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: ++++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++++\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address |\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | eth0 | True | 10.31.43.137 | 255.255.252.0 | global | 0e:26:17:53:a2:a3 |\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | eth0 | True | fe80::c26:17ff:fe53:a2a3/64 | . | link | 0e:26:17:53:a2:a3 |\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . |\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | lo | True | ::1/128 | . | host | . |\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: ++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+------------+---------------+-----------+-------+\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+------------+---------------+-----------+-------+\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | 0 | 0.0.0.0 | 10.31.40.1 | 0.0.0.0 | eth0 | UG |\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | 1 | 10.31.40.0 | 0.0.0.0 | 255.255.252.0 | eth0 | U |\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+------------+---------------+-----------+-------+\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+---------+-----------+-------+\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | Route | Destination | Gateway | Interface | Flags |\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+---------+-----------+-------+\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | 1 | fe80::/64 | :: | eth0 | U |\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: | 3 | multicast | :: | eth0 | U |\nJul 10 17:54:26 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: ci-info: +-------+-------------+---------+-----------+-------+\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Generating public/private rsa key pair.\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your identification has been saved in /etc/ssh/ssh_host_rsa_key\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key fingerprint is:\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: SHA256:dmFeaAMb/pejg2wfOzTth6u62tK3BMbUAWOZ/eHAwS0 root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key's randomart image is:\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +---[RSA 3072]----+\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | *Boo |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | oo*Eoo |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | + B=.. |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | o = +o. |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | S +.+ |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | + +oo.. |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | .+.=o . |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | .o.oo+o . |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | .o++=+.o |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +----[SHA256]-----+\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Generating public/private ecdsa key pair.\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key fingerprint is:\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: SHA256:C0qeOqMG364qgBsVlyBHRFOYQACccHJCFiKDwLSDFyY root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key's randomart image is:\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +---[ECDSA 256]---+\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |E@#=.. |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |*#=oo |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |.o.o |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | .o |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |.. . . S |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |= o o . . |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |o+ .+ . |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |o.+.. |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |=oo=. |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +----[SHA256]-----+\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Generating public/private ed25519 key pair.\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your identification has been saved in /etc/ssh/ssh_host_ed25519_key\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key fingerprint is:\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: SHA256:dNPitcZCSglodInvKUrvKnskGjz+zXLMcbT/KrzIp14 root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: The key's randomart image is:\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +--[ED25519 256]--+\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | ..oo. |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | +... . . |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | . . + = o |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: | .+ = = . |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |. ...S o + |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |ooo ..oo o |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |o=.oo.+E. |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |o.o.=+o+ . |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: |.+o+=Bo.o.o. |\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[731]: +----[SHA256]-----+\nJul 10 17:54:27 ip-10-31-43-137.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 251.\nJul 10 17:54:27 ip-10-31-43-137.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 254.\nJul 10 17:54:27 ip-10-31-43-137.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 196.\nJul 10 17:54:27 ip-10-31-43-137.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 253.\nJul 10 17:54:27 ip-10-31-43-137.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 212.\nJul 10 17:54:27 ip-10-31-43-137.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 230.\nJul 10 17:54:27 ip-10-31-43-137.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 242.\nJul 10 17:54:27 ip-10-31-43-137.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 229.\nJul 10 17:54:27 ip-10-31-43-137.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 232.\nJul 10 17:54:27 ip-10-31-43-137.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 239.\nJul 10 17:54:27 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sm-notify[804]: Version 2.5.4 starting\nJul 10 17:54:27 ip-10-31-43-137.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 230.\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd[806]: Server listening on 0.0.0.0 port 22.\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd[806]: Server listening on :: port 22.\nJul 10 17:54:28 ip-10-31-43-137.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 232.\nJul 10 17:54:28 ip-10-31-43-137.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 242.\nJul 10 17:54:28 ip-10-31-43-137.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 239.\nJul 10 17:54:28 ip-10-31-43-137.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 260.\nJul 10 17:54:28 ip-10-31-43-137.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 218.\nJul 10 17:54:28 ip-10-31-43-137.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 222.\nJul 10 17:54:28 ip-10-31-43-137.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 217.\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com restraintd[810]: Listening on http://localhost:8081\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) STARTUP (1.5.7)\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (Syslog will be used instead of sendmail.)\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 70% if used.)\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com crond[811]: (CRON) INFO (running with inotify support)\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[931]: Cloud-init v. 24.4-8.el9.1 running 'modules:config' at Fri, 10 Jul 2026 21:54:28 +0000. Up 26.88 seconds.\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com rsyslogd[805]: [origin software=\"rsyslogd\" swVersion=\"8.2604.0-1.el9\" x-pid=\"805\" x-info=\"https://www.rsyslog.com\"] start\nJul 10 17:54:28 ip-10-31-43-137.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 229.\nJul 10 17:54:28 ip-10-31-43-137.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 126.\nJul 10 17:54:28 ip-10-31-43-137.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 225.\nJul 10 17:54:28 ip-10-31-43-137.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.\nJul 10 17:54:28 ip-10-31-43-137.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 225.\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd[806]: Received signal 15; terminating.\nJul 10 17:54:28 ip-10-31-43-137.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 514.\nJul 10 17:54:28 ip-10-31-43-137.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.\nJul 10 17:54:28 ip-10-31-43-137.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 514 and the job result is done.\nJul 10 17:54:28 ip-10-31-43-137.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 514.\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd[938]: Server listening on 0.0.0.0 port 22.\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd[938]: Server listening on :: port 22.\nJul 10 17:54:28 ip-10-31-43-137.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 514.\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com rsyslogd[805]: imjournal: journal files changed, reloading... [v8.2604.0-1.el9 try https://www.rsyslog.com/e/0 ]\nJul 10 17:54:28 ip-10-31-43-137.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 253.\nJul 10 17:54:28 ip-10-31-43-137.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 255.\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[942]: Cloud-init v. 24.4-8.el9.1 running 'modules:final' at Fri, 10 Jul 2026 21:54:28 +0000. Up 27.30 seconds.\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1014]: #############################################################\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1020]: -----BEGIN SSH HOST KEY FINGERPRINTS-----\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1030]: 256 SHA256:C0qeOqMG364qgBsVlyBHRFOYQACccHJCFiKDwLSDFyY root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com (ECDSA)\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1039]: 256 SHA256:dNPitcZCSglodInvKUrvKnskGjz+zXLMcbT/KrzIp14 root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com (ED25519)\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1051]: 3072 SHA256:dmFeaAMb/pejg2wfOzTth6u62tK3BMbUAWOZ/eHAwS0 root@ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com (RSA)\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1054]: -----END SSH HOST KEY FINGERPRINTS-----\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[1059]: #############################################################\nJul 10 17:54:28 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com cloud-init[942]: Cloud-init v. 24.4-8.el9.1 finished at Fri, 10 Jul 2026 21:54:28 +0000. Datasource DataSourceEc2Local. Up 27.51 seconds\nJul 10 17:54:29 ip-10-31-43-137.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 255.\nJul 10 17:54:29 ip-10-31-43-137.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 250.\nJul 10 17:54:29 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Detected change(s) in the following file(s): /etc/fstab\nJul 10 17:54:32 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: Selected source 10.2.32.37\nJul 10 17:54:32 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com chronyd[612]: System clock TAI offset set to 37 seconds\nJul 10 17:54:32 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kernel: block nvme0n1: the capability attribute has been deprecated.\nJul 10 17:54:33 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Detected change in block device driver, new loaded module: nvme\nJul 10 17:54:33 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Rebuilding /boot/initramfs-5.14.0-721.el9.x86_64kdump.img\nJul 10 17:54:33 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1991]: dracut-057-118.git20260624.el9\nJul 10 17:54:33 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Executing: /usr/bin/dracut --quiet --hostonly --hostonly-cmdline --hostonly-i18n --hostonly-mode strict --hostonly-nics --mount \"/dev/disk/by-uuid/7c0d6762-a0be-4063-a43a-c35e843399f8 /sysroot xfs rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota\" --squash-compressor zstd --no-hostonly-default-device --add-drivers nvme --add-confdir /lib/kdump/dracut.conf.d -f /boot/initramfs-5.14.0-721.el9.x86_64kdump.img 5.14.0-721.el9.x86_64\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-timesyncd' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-time-wait-sync' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'dbus-daemon' will not be installed, because command 'dbus-daemon' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmand' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Module 'ifcfg' will not be installed, because it's in the list to be omitted!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Module 'plymouth' will not be installed, because it's in the list to be omitted!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: 62bluetooth: Could not find any command of '/usr/lib/bluetooth/bluetoothd /usr/libexec/bluetooth/bluetoothd'!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvmthinpool-monitor' will not be installed, because command 'lvm' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvm' will not be installed, because command 'lvm' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'pcsc' will not be installed, because command 'pcscd' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Module 'resume' will not be installed, because it's in the list to be omitted!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found!\nJul 10 17:54:34 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Module 'earlykdump' will not be installed, because it's in the list to be omitted!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: memstrack is not available\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-timesyncd' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'systemd-timesyncd' will not be installed, because command '/usr/lib/systemd/systemd-time-wait-sync' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'dbus-daemon' will not be installed, because command 'dbus-daemon' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmand' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: 62bluetooth: Could not find any command of '/usr/lib/bluetooth/bluetoothd /usr/libexec/bluetooth/bluetoothd'!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvmthinpool-monitor' will not be installed, because command 'lvm' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'lvm' will not be installed, because command 'lvm' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'pcsc' will not be installed, because command 'pcscd' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found!\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: memstrack is not available\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: systemd ***\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: fips ***\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: systemd-initrd ***\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: rngd ***\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: i18n ***\nJul 10 17:54:35 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: drm ***\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: prefixdevname ***\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: kernel-modules ***\nJul 10 17:54:36 ip-10-31-43-137.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.\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: kernel-modules-extra ***\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: kernel-modules-extra: configuration source \"/run/depmod.d\" does not exist\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: kernel-modules-extra: configuration source \"/lib/depmod.d\" does not exist\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: kernel-modules-extra: parsing configuration file \"/etc/depmod.d/dist.conf\"\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: kernel-modules-extra: /etc/depmod.d/dist.conf: added \"updates extra built-in weak-updates\" to the list of search directories\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: nvdimm ***\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: fstab-sys ***\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: rootfs-block ***\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: terminfo ***\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: udev-rules ***\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Skipping udev rule: 91-permissions.rules\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Skipping udev rule: 80-drivers-modprobe.rules\nJul 10 17:54:36 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: dracut-systemd ***\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: usrmount ***\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: base ***\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: fs-lib ***\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: kdumpbase ***\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: microcode_ctl-fw_dir_override ***\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl module: mangling fw_dir\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: reset fw_dir to \"/lib/firmware/updates /lib/firmware\"\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel\"...\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: intel: caveats check for kernel version \"5.14.0-721.el9.x86_64\" passed, adding \"/usr/share/microcode_ctl/ucode_with_caveats/intel\" to fw_dir variable\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-2d-07\"...\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration \"intel-06-2d-07\" is ignored\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-4e-03\"...\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration \"intel-06-4e-03\" is ignored\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-4f-01\"...\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration \"intel-06-4f-01\" is ignored\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-55-04\"...\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: intel-06-55-04: caveats check for kernel version \"5.14.0-721.el9.x86_64\" passed, adding \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-55-04\" to fw_dir variable\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-5e-03\"...\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration \"intel-06-5e-03\" is ignored\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8c-01\"...\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration \"intel-06-8c-01\" is ignored\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8e-9e-0x-0xca\"...\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration \"intel-06-8e-9e-0x-0xca\" is ignored\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8e-9e-0x-dell\"...\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration \"intel-06-8e-9e-0x-dell\" is ignored\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: processing data directory \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8f-08\"...\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: configuration \"intel-06-8f-08\" is ignored\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: microcode_ctl: final fw_dir: \"/usr/share/microcode_ctl/ucode_with_caveats/intel-06-55-04 /lib/firmware/updates /lib/firmware\"\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: openssl ***\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: shutdown ***\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including module: squash ***\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Including modules done ***\nJul 10 17:54:37 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Installing kernel module dependencies ***\nJul 10 17:54:38 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Installing kernel module dependencies done ***\nJul 10 17:54:38 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Resolving executable dependencies ***\nJul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Resolving executable dependencies done ***\nJul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Generating early-microcode cpio image ***\nJul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Constructing GenuineIntel.bin ***\nJul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Constructing GenuineIntel.bin ***\nJul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Store current command line parameters ***\nJul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Stored kernel commandline:\nJul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: No dracut internal kernel commandline stored in the initramfs\nJul 10 17:54:39 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Install squash loader ***\nJul 10 17:54:40 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Squashing the files inside the initramfs ***\nJul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Squashing the files inside the initramfs done ***\nJul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Creating image file '/boot/initramfs-5.14.0-721.el9.x86_64kdump.img' ***\nJul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Hardlinking files ***\nJul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Mode: real\nJul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Files: 51\nJul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Linked: 0 files\nJul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Compared: 0 xattrs\nJul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Compared: 0 files\nJul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Saved: 0 B\nJul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: Duration: 0.000284 seconds\nJul 10 17:54:46 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Hardlinking files done ***\nJul 10 17:54:47 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com dracut[1993]: *** Creating initramfs image file '/boot/initramfs-5.14.0-721.el9.x86_64kdump.img' done ***\nJul 10 17:54:47 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: kexec: loaded kdump kernel\nJul 10 17:54:47 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com kdumpctl[817]: kdump: Starting kdump: [OK]\nJul 10 17:54:47 ip-10-31-43-137.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 212.\nJul 10 17:54:47 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[1]: Startup finished in 1.714s (kernel) + 9.909s (initrd) + 34.589s (userspace) = 46.213s.\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 1714473 microseconds.\n\u2591\u2591 \n\u2591\u2591 Initrd start-up required 9909188 microseconds.\n\u2591\u2591 \n\u2591\u2591 Userspace start-up required 34589926 microseconds.\nJul 10 17:54:55 ip-10-31-43-137.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.\nJul 10 17:55:20 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com irqbalance[603]: Cannot change IRQ 29 affinity: Operation not permitted\nJul 10 17:55:20 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com irqbalance[603]: IRQ 29 affinity is now unmanaged\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5237]: Accepted publickey for root from 10.30.34.89 port 40702 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU\nJul 10 17:56:03 ip-10-31-43-137.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 516.\nJul 10 17:56:03 ip-10-31-43-137.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 520.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: 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 5237.\nJul 10 17:56:03 ip-10-31-43-137.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 520.\nJul 10 17:56:03 ip-10-31-43-137.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 515.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: Queued start job for default target Main User Target.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 9.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 11.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 8.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: Startup finished in 84ms.\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 84296 microseconds.\nJul 10 17:56:03 ip-10-31-43-137.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 515.\nJul 10 17:56:03 ip-10-31-43-137.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 583.\nJul 10 17:56:03 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5237]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)\nJul 10 17:56:04 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5250]: Received disconnect from 10.30.34.89 port 40702:11: disconnected by user\nJul 10 17:56:04 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5250]: Disconnected from user root 10.30.34.89 port 40702\nJul 10 17:56:04 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5237]: pam_unix(sshd:session): session closed for user root\nJul 10 17:56:04 ip-10-31-43-137.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.\nJul 10 17:56:04 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: Session 1 logged out. Waiting for processes to exit.\nJul 10 17:56:04 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: 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.\nJul 10 17:56:10 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com irqbalance[603]: Cannot change IRQ 28 affinity: Operation not permitted\nJul 10 17:56:10 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com irqbalance[603]: IRQ 28 affinity is now unmanaged\nJul 10 17:56:14 ip-10-31-43-137.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 652.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: Activating special unit Exit the Session...\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 24 and the job result is done.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 28 and the job result is done.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 29 and the job result is done.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 17 and the job result is done.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 16 and the job result is done.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 27 and the job result is done.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 23 and the job result is done.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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 26 and the job result is done.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:14 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5241]: 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.\nJul 10 17:56:14 ip-10-31-43-137.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.\nJul 10 17:56:14 ip-10-31-43-137.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 652 and the job result is done.\nJul 10 17:56:14 ip-10-31-43-137.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 653.\nJul 10 17:56:14 ip-10-31-43-137.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.\nJul 10 17:56:14 ip-10-31-43-137.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.\nJul 10 17:56:14 ip-10-31-43-137.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 653 and the job result is done.\nJul 10 17:56:14 ip-10-31-43-137.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 655 and the job result is done.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5287]: Accepted publickey for root from 10.31.8.121 port 37590 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5288]: Accepted publickey for root from 10.31.8.121 port 37592 ssh2: RSA SHA256:W3cSdmPJK+d9RwU97ardijPXIZnxHswrpTHWW9oYtEU\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: 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 5287.\nJul 10 17:56:15 ip-10-31-43-137.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 659.\nJul 10 17:56:15 ip-10-31-43-137.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 658.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: 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 5288.\nJul 10 17:56:15 ip-10-31-43-137.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 658.\nJul 10 17:56:15 ip-10-31-43-137.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 657.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: Queued start job for default target Main User Target.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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 9.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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 9.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: 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.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[5294]: Startup finished in 75ms.\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 75368 microseconds.\nJul 10 17:56:15 ip-10-31-43-137.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 657.\nJul 10 17:56:15 ip-10-31-43-137.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 725.\nJul 10 17:56:15 ip-10-31-43-137.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 794.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5287]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5288]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5304]: Received disconnect from 10.31.8.121 port 37592:11: disconnected by user\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5304]: Disconnected from user root 10.31.8.121 port 37592\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sshd-session[5288]: pam_unix(sshd:session): session closed for user root\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd[1]: session-4.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-4.scope has successfully entered the 'dead' state.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: Session 4 logged out. Waiting for processes to exit.\nJul 10 17:56:15 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com systemd-logind[607]: Removed session 4.\n\u2591\u2591 Subject: Session 4 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 4 has been terminated.\nJul 10 17:56:17 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sudo[5800]: root : PWD=/root ; USER=root ; COMMAND=/bin/true\nJul 10 17:56:17 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sudo[5800]: pam_unix(sudo:session): session opened for user root(uid=0) by root(uid=0)\nJul 10 17:56:17 ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com sudo[5800]: pam_unix(sudo:session): session closed for user root\nJul 10 17:56:19 ip-10-31-43-137.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!)\nJul 10 17:56:20 ip-10-31-43-137.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 863.\nJul 10 17:56:21 ip-10-31-43-137.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 863.\nJul 10 17:56:21 managed-node2 systemd-hostnamed[8033]: Hostname set to (static)\nJul 10 17:56:21 managed-node2 NetworkManager[639]: [1783720581.0053] hostname: static hostname changed from \"ip-10-31-43-137.testing-farm.us-east-1.aws.redhat.com\" to \"managed-node2\"\nJul 10 17:56:21 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 929.\nJul 10 17:56:21 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 929.\nJul 10 17:56:21 managed-node2 unknown: Leaving test '/Prepare-managed-node/tests/prep_managed_node' (serial number 1). (Be aware the test name is sanitized!)\nJul 10 17:56:31 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.\nJul 10 17:56:43 managed-node2 chronyd[612]: Selected source 38.45.67.7 (2.centos.pool.ntp.org)\nJul 10 17:56:51 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.\nJul 10 17:57:06 managed-node2 sshd-session[8742]: Accepted publickey for root from 10.31.41.91 port 38426 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE\nJul 10 17:57:06 managed-node2 systemd-logind[607]: 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 8742.\nJul 10 17:57:06 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 995.\nJul 10 17:57:06 managed-node2 sshd-session[8742]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)\nJul 10 17:57:06 managed-node2 sshd-session[8745]: Received disconnect from 10.31.41.91 port 38426:11: disconnected by user\nJul 10 17:57:06 managed-node2 sshd-session[8745]: Disconnected from user root 10.31.41.91 port 38426\nJul 10 17:57:06 managed-node2 sshd-session[8742]: pam_unix(sshd:session): session closed for user root\nJul 10 17:57:06 managed-node2 systemd[1]: session-6.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-6.scope has successfully entered the 'dead' state.\nJul 10 17:57:06 managed-node2 systemd-logind[607]: Session 6 logged out. Waiting for processes to exit.\nJul 10 17:57:06 managed-node2 systemd-logind[607]: Removed session 6.\n\u2591\u2591 Subject: Session 6 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 6 has been terminated.\nJul 10 17:57:06 managed-node2 sshd-session[8769]: Accepted publickey for root from 10.31.41.91 port 38440 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE\nJul 10 17:57:06 managed-node2 systemd-logind[607]: New session 7 of user root.\n\u2591\u2591 Subject: A new session 7 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 7 has been created for the user root.\n\u2591\u2591 \n\u2591\u2591 The leading process of the session is 8769.\nJul 10 17:57:06 managed-node2 systemd[1]: Started Session 7 of User root.\n\u2591\u2591 Subject: A start job for unit session-7.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-7.scope has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 1064.\nJul 10 17:57:06 managed-node2 sshd-session[8769]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)\nJul 10 17:57:06 managed-node2 sshd-session[8772]: Received disconnect from 10.31.41.91 port 38440:11: disconnected by user\nJul 10 17:57:06 managed-node2 sshd-session[8772]: Disconnected from user root 10.31.41.91 port 38440\nJul 10 17:57:06 managed-node2 sshd-session[8769]: pam_unix(sshd:session): session closed for user root\nJul 10 17:57:06 managed-node2 systemd[1]: session-7.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-7.scope has successfully entered the 'dead' state.\nJul 10 17:57:06 managed-node2 systemd-logind[607]: Session 7 logged out. Waiting for processes to exit.\nJul 10 17:57:06 managed-node2 systemd-logind[607]: Removed session 7.\n\u2591\u2591 Subject: Session 7 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 7 has been terminated.\nJul 10 17:57:09 managed-node2 sshd-session[8798]: Accepted publickey for root from 10.31.41.91 port 38454 ssh2: ECDSA SHA256:8WqKavN+MmkbmRUBckBNpJdwML/N5YgGt4RNFPp+svU\nJul 10 17:57:09 managed-node2 systemd-logind[607]: New session 8 of user root.\n\u2591\u2591 Subject: A new session 8 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 8 has been created for the user root.\n\u2591\u2591 \n\u2591\u2591 The leading process of the session is 8798.\nJul 10 17:57:09 managed-node2 systemd[1]: Started Session 8 of User root.\n\u2591\u2591 Subject: A start job for unit session-8.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-8.scope has finished successfully.\n\u2591\u2591 \n\u2591\u2591 The job identifier is 1133.\nJul 10 17:57:09 managed-node2 sshd-session[8798]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)\nJul 10 17:57:11 managed-node2 python3.9[8975]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d\nJul 10 17:57:11 managed-node2 python3.9[9150]: ansible-tempfile Invoked with state=directory prefix=lsr_ suffix=_podman path=None\nJul 10 17:57:12 managed-node2 python3.9[9299]: ansible-file Invoked with path=/tmp/lsr_veqsgttx_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\nJul 10 17:57:13 managed-node2 python3.9[9448]: 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\nJul 10 17:57:13 managed-node2 useradd[9450]: new group: name=podman_basic_user, GID=3001\nJul 10 17:57:13 managed-node2 useradd[9450]: new user: name=podman_basic_user, UID=3001, GID=3001, home=/home/podman_basic_user, shell=/bin/bash, from=/dev/pts/0\nJul 10 17:57:13 managed-node2 python3.9[9605]: ansible-ansible.legacy.command Invoked with executable=/bin/bash _raw_params=set -uxo pipefail\n exec 1>&2\n for file in /etc/containers/ansible-kubernetes.d/*; do\n if [ -f \"$file\" ]; then\n echo \"File: $file\"\n cat \"$file\"\n fi\n done\n _uses_shell=True expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None creates=None removes=None stdin=None\nJul 10 17:57:14 managed-node2 python3.9[9755]: 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-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:509" } ] SYSTEM ROLES ERRORS END v1 TASKS RECAP ******************************************************************** Friday 10 July 2026 17:57:15 -0400 (0:00:00.232) 0:00:06.141 *********** =============================================================================== Gathering Facts --------------------------------------------------------- 2.29s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:9 Create user ------------------------------------------------------------- 0.62s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:208 Change tmpdir permissions ----------------------------------------------- 0.51s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:182 Create tmpdir for testing ----------------------------------------------- 0.48s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:175 Show kube files --------------------------------------------------------- 0.45s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:495 Dump journal ------------------------------------------------------------ 0.42s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:509 Clean up host directories ----------------------------------------------- 0.36s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:525 Clean up storage.conf --------------------------------------------------- 0.35s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:518 Create tempfile for kube_src -------------------------------------------- 0.25s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:213 Remove kube file src ---------------------------------------------------- 0.23s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:532 Enable podman copr ------------------------------------------------------ 0.04s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:193 Install podman from updates-testing ------------------------------------- 0.03s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:198 Podman version ---------------------------------------------------------- 0.03s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:203 Include vault variables ------------------------------------------------- 0.02s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:5 Write kube_file_src ----------------------------------------------------- 0.02s /tmp/collections-nT1/ansible_collections/fedora/linux_system_roles/tests/podman/tests_basic.yml:221 Jul 10 17:57:09 managed-node2 sshd-session[8798]: Accepted publickey for root from 10.31.41.91 port 38454 ssh2: ECDSA SHA256:8WqKavN+MmkbmRUBckBNpJdwML/N5YgGt4RNFPp+svU Jul 10 17:57:09 managed-node2 systemd-logind[607]: New session 8 of user root. ░░ Subject: A new session 8 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 8 has been created for the user root. ░░ ░░ The leading process of the session is 8798. Jul 10 17:57:09 managed-node2 systemd[1]: Started Session 8 of User root. ░░ Subject: A start job for unit session-8.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-8.scope has finished successfully. ░░ ░░ The job identifier is 1133. Jul 10 17:57:09 managed-node2 sshd-session[8798]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) Jul 10 17:57:11 managed-node2 python3.9[8975]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d Jul 10 17:57:11 managed-node2 python3.9[9150]: ansible-tempfile Invoked with state=directory prefix=lsr_ suffix=_podman path=None Jul 10 17:57:12 managed-node2 python3.9[9299]: ansible-file Invoked with path=/tmp/lsr_veqsgttx_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 Jul 10 17:57:13 managed-node2 python3.9[9448]: 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 Jul 10 17:57:13 managed-node2 useradd[9450]: new group: name=podman_basic_user, GID=3001 Jul 10 17:57:13 managed-node2 useradd[9450]: new user: name=podman_basic_user, UID=3001, GID=3001, home=/home/podman_basic_user, shell=/bin/bash, from=/dev/pts/0 Jul 10 17:57:13 managed-node2 python3.9[9605]: ansible-ansible.legacy.command Invoked with executable=/bin/bash _raw_params=set -uxo pipefail exec 1>&2 for file in /etc/containers/ansible-kubernetes.d/*; do if [ -f "$file" ]; then echo "File: $file" cat "$file" fi done _uses_shell=True expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None creates=None removes=None stdin=None Jul 10 17:57:14 managed-node2 python3.9[9755]: ansible-ansible.legacy.command Invoked with _raw_params=journalctl -ex _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None Jul 10 17:57:14 managed-node2 python3.9[9905]: ansible-file Invoked with path=/etc/containers/storage.conf state=absent recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 10 17:57:14 managed-node2 python3.9[10054]: ansible-file Invoked with path=/tmp/lsr_veqsgttx_podman state=absent recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S unsafe_writes=False _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None Jul 10 17:57:15 managed-node2 sshd-session[10079]: Accepted publickey for root from 10.31.41.91 port 51686 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE Jul 10 17:57:15 managed-node2 systemd-logind[607]: New session 9 of user root. ░░ Subject: A new session 9 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 9 has been created for the user root. ░░ ░░ The leading process of the session is 10079. Jul 10 17:57:15 managed-node2 systemd[1]: Started Session 9 of User root. ░░ Subject: A start job for unit session-9.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-9.scope has finished successfully. ░░ ░░ The job identifier is 1202. Jul 10 17:57:15 managed-node2 sshd-session[10079]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) Jul 10 17:57:15 managed-node2 sshd-session[10082]: Received disconnect from 10.31.41.91 port 51686:11: disconnected by user Jul 10 17:57:15 managed-node2 sshd-session[10082]: Disconnected from user root 10.31.41.91 port 51686 Jul 10 17:57:15 managed-node2 sshd-session[10079]: pam_unix(sshd:session): session closed for user root Jul 10 17:57:15 managed-node2 systemd[1]: session-9.scope: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit session-9.scope has successfully entered the 'dead' state. Jul 10 17:57:15 managed-node2 systemd-logind[607]: Session 9 logged out. Waiting for processes to exit. Jul 10 17:57:15 managed-node2 systemd-logind[607]: Removed session 9. ░░ Subject: Session 9 has been terminated ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A session with the ID 9 has been terminated. Jul 10 17:57:15 managed-node2 sshd-session[10107]: Accepted publickey for root from 10.31.41.91 port 51694 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE Jul 10 17:57:15 managed-node2 systemd-logind[607]: New session 10 of user root. ░░ Subject: A new session 10 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 10 has been created for the user root. ░░ ░░ The leading process of the session is 10107. Jul 10 17:57:15 managed-node2 systemd[1]: Started Session 10 of User root. ░░ Subject: A start job for unit session-10.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-10.scope has finished successfully. ░░ ░░ The job identifier is 1271. Jul 10 17:57:15 managed-node2 sshd-session[10107]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)