action #48062
closed[functional][y] test fails in disable_grub_timeout - No log available
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-NET-aarch64-RAID10@aarch64 fails in
disable_grub_timeout
Triggering a restart make this go away most of the time.
This has been reported as a bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1125718 but there is no log available from openQA.
Probably because test expect to login on tty5 console, whereas there is no password prompt at this stage.
Acceptance criteria¶
- AC1: A failure in the mentioned scenario in the same test module is able to provide logs on failure
- AC2: Bug is verified (for example taking statistics) and not dialog appears.
Further details¶
logs_from_installation_system module is able to collect logs, so we can reapply the solution.
Always latest result in this scenario: latest
Updated by okurz about 5 years ago
- Subject changed from test fails in disable_grub_timeout - No log available to [functional][y] test fails in disable_grub_timeout - No log available
- Description updated (diff)
- Due date set to 2019-04-16
- Category changed from Bugs in existing tests to Enhancement to existing tests
- Status changed from New to Workable
- Target version set to Milestone 24
Updated by ggardet_arm about 5 years ago
Logs are now uploaded: https://openqa.opensuse.org/tests/869420#downloads
Updated by JERiveraMoya almost 5 years ago
- Description updated (diff)
- Estimated time set to 3.00 h
Updated by oorlov almost 5 years ago
- Status changed from Workable to In Progress
- Assignee set to oorlov
Updated by oorlov almost 5 years ago
- Status changed from In Progress to Resolved
The issue is fixed: https://openqa.opensuse.org/tests/895075. On 12 days ago build, 'disable_grub_timeout' module was failed and logs were collected properly.