action #62249
closed
[functional][y][aarch64] Wrong chain of workarounds, first_boot tries to log twice.
Added by JRivrain over 4 years ago.
Updated over 4 years ago.
Category:
Bugs in existing tests
- Subject changed from [functional][y] Same workaround called twice, boot fails to [functional][y] Same workaround called twice, first_boot fails
- 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)
- 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.
- Description updated (diff)
- Description updated (diff)
- Description updated (diff)
- 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.
- 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
- 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.
- 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#
- Status changed from Feedback to Resolved
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
Also available in: Atom
PDF