action #48572
closed[sle][functional][y] test fails in welcome - wrong url sent to worker because of mistyping
0%
Description
Observation¶
In vars.json we have : SCC_URL "http://Server-0126.proxy.scc.suse.de"
In autoinst-log.txt : type_string(string=' regurl=http://Server-0126.proxy.scc.suse.de'
But
In serial.txt and on video : regurl=http://Server-0126.proxysc.s.e
openQA test in scenario sle-12-SP5-Server-DVD-x86_64-RAID5@64bit fails in
welcome
We should improve our tests to detect such cases and not hide them to simplify review.
Acceptance criteria¶
- Typos in boot parameters are detected and are clearly visualized on the job page
Test suite description¶
Maintainer: slindomansilla, jrauch
Installation of RAID5 using expert partitioner
Reproducible¶
Fails since (at least) Build 0126 (current job)
Expected result¶
Last good: 0122 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 6 years ago
- Related to action #42275: [functional][u][sporadic] test fails in bootloader with mistyped/incomplete regurl on x86_64 added
Updated by okurz almost 6 years ago
- Related to action #46190: [functional][u] test fails in user_settings - mistyping in Username (lowercase instead of uppercase) added
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional][y] test fails in welcome - wrong url sent to worker. to [sle][functional][y] test fails in welcome - wrong url sent to worker because of mistyping
- Due date set to 2019-03-26
- Status changed from New to Workable
- Target version set to Milestone 23
Pretty sure this is a sporadic issue and the workaround of "retriggering" should work. Please crosscheck that during the next sprint.
Updated by riafarov almost 6 years ago
- Description updated (diff)
- Priority changed from High to Normal
Lowering the priority as re-triggering works, refine to do assert, so it's clear from the first sight if we have a typo.
Updated by oorlov almost 6 years ago
- Status changed from Workable to In Progress
Updated by JERiveraMoya over 5 years ago
- Due date changed from 2019-03-26 to 2019-04-09
It was evaluated that a most robust solution is required. Moving to next sprint.
Updated by riafarov over 5 years ago
- Target version changed from Milestone 23 to Milestone 24
Updated by oorlov over 5 years ago
- Status changed from In Progress to Feedback
Updated by JERiveraMoya over 5 years ago
- Status changed from Feedback to In Progress
Updated by oorlov over 5 years ago
- Status changed from In Progress to Resolved
Verification Run: https://openqa.opensuse.org/tests/900852