I asked one of the SUSE systemd/udev maintainers and he confirmed it: Since SLE12, devtmpfs pseudo filesystem is used. Therefore the kernel creates the device nodes and udev is simply running the rules to set, amongst others, device permissions. I told him that one same code in "rear"...
ACTION=add) [ 17.086407] localhost systemd-udevd[399]: ttyS0: /usr/lib/udev/rules.d/50-udev-default.rules:29 GROUP 18 [ 17.094999] localhost systemd-udevd[399]: ttyS0: Setting permissions /dev/ttyS0, uid=0, gid=18, mode=0660 [ 17.100594] localhost systemd-udevd[399]: ttyS0: Successf...
At that time kthreadd that was responsible for creating workers was busy isolating the pages for the zone compaction. Raw [1140818.459880] CPU: 5 PID: 813 Comm: systemd-udevd Kdump: loaded Tainted: P OE --- 3.10.0-1160.36.2.el7.x86_64 #1 [1140818.459881] Hardware name: VMware, Inc. VMw...
2024/07/30 11:34:22 [INFO] [planner] rkecluster fleet-default/hta-test: configuring bootstrap node(s) hta-test-hta-test-6ff7c77d6bxnsbhc-zrl45: waiting for cluster agent to connect 2024/07/30 11:34:22 [INFO] [planner] rkecluster fleet-default/hta-test: configuring bootstrap node(...
As Michael mentioned, this really looks more like a system that is under load and not responding well to all the systemd services that are being run during the install process. The time values I'm seeing in comment #18 from systemd-analyze are 10 times greater than what I typically see ...