action #62249
closed[functional][y][aarch64] Wrong chain of workarounds, first_boot tries to log twice.
0%
Description
Observation¶
wait_boot_past_bootloader is calling handle_displaymanager_login which calls handle_login, and then calls handle_broken_autologin_boo1102563 which then calls handle_login again. For some reason, only happens on aarch64.
Similar thing seems to happen with shutdown https://openqa.suse.de/tests/3803686#step/shutdown/15 on hyperv.
openQA test in scenario sle-15-SP2-Online-aarch64-btrfs_libstorage-ng@aarch64 fails in
first_boot See also See also https://openqa.suse.de/tests/3804489#step/first_boot/71 for slightly different symptom
Test suite description¶
Maintainers: QSF-y.
Test installation with btrfs filesystem and libstorage-ng.
Validates no_COW attributes on subvolumes, file system on partitions, checks whether /home is on separate partition or not (depending on the system).
Reproducible¶
Fails since (at least) Build 126.1
Expected result¶
Last good: 122.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by JRivrain over 4 years ago
- Subject changed from [functional][y] Same workaround called twice, boot fails to [functional][y] Same workaround called twice, first_boot fails
Updated by JRivrain over 4 years ago
- Subject changed from [functional][y] Same workaround called twice, first_boot fails to [functional][y] Wrong chain of workarounds, first_boot tries to boot twice.
- Description updated (diff)
Updated by JRivrain over 4 years ago
- Subject changed from [functional][y] Wrong chain of workarounds, first_boot tries to boot twice. to [functional][y] Wrong chain of workarounds, first_boot tries to log twice.
Updated by SLindoMansilla over 4 years ago
- Subject changed from [functional][y] Wrong chain of workarounds, first_boot tries to log twice. to [functional][y][u] Wrong chain of workarounds, first_boot tries to log twice.
Functional job group is also affected by this: https://progress.opensuse.org/issues/59014
Updated by SLindoMansilla over 4 years ago
- Related to action #62366: [functional][u][svirt-xen-pv] test fails in shutdown - Misfunction of workaround to login in GDM with unselected user item added
Updated by SLindoMansilla over 4 years ago
- Subject changed from [functional][y][u] Wrong chain of workarounds, first_boot tries to log twice. to [functional][y][u][aarch64] Wrong chain of workarounds, first_boot tries to log twice.
Updated by riafarov over 4 years ago
- Subject changed from [functional][y][u][aarch64] Wrong chain of workarounds, first_boot tries to log twice. to [functional][y][aarch64] Wrong chain of workarounds, first_boot tries to log twice.
- Status changed from New to Feedback
- Assignee set to riafarov
Seems that the needle I've created for yast first boot has introduced this behavior, as I've selected slightly smaller area which doesn't cover password field.
Checking if my fix worked: https://openqa.suse.de/tests/3814697#
Updated by riafarov over 4 years ago
- Status changed from Feedback to Resolved
This is fixed now: https://openqa.suse.de/tests/3815139
Updated by okurz about 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: btrfs_libstorage-ng
https://openqa.suse.de/tests/3864852
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed