action #168589
closed
action #166613: Yast default selected LSM changes from Apparmor to SELinux, existing openQA test fails in first_boot
[qe-core] test fails in wireguard
Added by cahu about 1 month ago.
Updated 13 days ago.
Category:
Bugs in existing tests
- Parent task set to #166613
Contact @cahu if any questions.
cc @tjyrinki_suse
Looks like for apparmor and security audit testsuites need to be reworked too. #168571 can be rejected in favor of #167662
- Subject changed from test fails in wireguard to [qe-core] test fails in wireguard
- Status changed from New to In Progress
- Assignee set to rfan1
Seems the system hang when executing the "ausearch -m avc -r" command. let me create a new iso image and test the job again.
I can catch some journal logs about /dev/hvc0
client login: Oct 28 04:26:50 localhost systemd[1]: Expecting device /dev/hvc0...
Oct 28 04:26:51 localhost systemd[1]: Condition check resulted in /dev/hvc0 being skipped.
Oct 28 04:26:54 localhost.localdomain systemd[1]: Started Serial Getty on hvc0.
Oct 28 04:29:15 localhost.localdomain login[1059]: ROOT LOGIN ON hvc0
Oct 28 04:35:59 susetest systemd[1]: Stopping Serial Getty on hvc0...
Oct 28 04:35:59 susetest systemd[1]: serial-getty@hvc0.service: Deactivated successfully.
Oct 28 04:35:59 susetest systemd[1]: Stopped Serial Getty on hvc0.
Oct 28 04:35:59 susetest systemd[1]: run-credentials-serial\x2dgetty\x40hvc0.service.mount: Deactivated successfully.
Oct 28 20:59:51 susetest systemd[1]: Expecting device /dev/hvc0...
Oct 28 20:59:51 susetest systemd[1]: Condition check resulted in /dev/hvc0 being skipped.
Oct 28 20:59:54 susetest systemd[1]: Started Serial Getty on hvc0.
Oct 28 21:00:00 susetest login[960]: ROOT LOGIN ON hvc0
**Oct 28 21:04:47 client systemd[1]: serial-getty@hvc0.service: Deactivated successfully.
Oct 28 21:04:47 client systemd[1]: run-credentials-serial\x2dgetty\x40hvc0.service.mount: Deactivated successfully.
Oct 28 21:04:47 client systemd[1]: serial-getty@hvc0.service: Scheduled restart job, restart counter is at 1.**
Oct 28 21:04:47 client systemd[1]: Started Serial Getty on hvc0.
Oct 28 22:05:57 client systemd[1]: Stopping Serial Getty on hvc0...
Oct 28 22:05:57 client systemd[1]: serial-getty@hvc0.service: Deactivated successfully.
Oct 28 22:05:57 client systemd[1]: Stopped Serial Getty on hvc0.
Oct 28 22:05:57 client systemd[1]: run-credentials-serial\x2dgetty\x40hvc0.service.mount: Deactivated successfully.
Oct 28 22:05:57 client systemd[1]: Started Serial Getty on hvc0.
enabled-runtime
● serial-getty@hvc0.service - Serial Getty on hvc0
Loaded: loaded (]8;;file://client/usr/lib/systemd/system/serial-getty@.service/usr/lib/systemd/system/serial-getty@.service]8;;; enabled-runtime; preset: 0;1;38:5:185mdisabled)]8;;\
Active: active (running) since Mon 2024-10-28 22:05:57 EDT; 3min 19s ago
Invocation: ad82ccfabe904b059fd1316d0c4a6f77
Docs: ]8;;man:agetty(8)man:agetty(8)]8;;]8;;\
]8;;man:systemd-getty-generator(8)man:systemd-getty-generator(8)]8;;]8;;\
]8;;https://0pointer.de/blog/projects/serial-console.htmlhttps://0pointer.de/blog/projects/serial-console.html]8;;]8;;\
Main PID: 10749 (agetty)
Tasks: 1 (limit: 1719)
CPU: 21ms
CGroup: /system.slice/system-serial\x2dgetty.slice/serial-getty@hvc0.service
└─10749 /sbin/agetty -o "-p -- \\u" --keep-baud 115200,57600,38400,9600 - vt220
Oct 28 22:05:57 client systemd[1]: Started Serial Getty on hvc0.
Below info interested me
Oct 28 21:04:47 client systemd[1]: serial-getty@hvc0.service: Deactivated successfully.
Oct 28 21:04:47 client systemd[1]: run-credentials-serial\x2dgetty\x40hvc0.service.mount: Deactivated successfully.
Oct 28 21:04:47 client systemd[1]: serial-getty@hvc0.service: Scheduled restart job, restart counter is at 1.
I don't know why hvc0 gets re-connected, will ask developer for this change
- Target version set to QE-Core: Ready
- Status changed from In Progress to Blocked
- Status changed from Blocked to Feedback
- Status changed from Feedback to Resolved
Also available in: Atom
PDF