Bug 1213681 - [yast2-users] Failed openQA tests with 4.6.3
Summary: [yast2-users] Failed openQA tests with 4.6.3
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-26 12:42 UTC by Ana Guerrero
Modified: 2023-08-07 13:25 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ana Guerrero 2023-07-26 12:42:00 UTC 
There a couple of issues in openQA after the upload of 4.6.3 on July 24.
Please see:

https://openqa.opensuse.org/tests/3455534#step/enable_autologin/3

https://openqa.opensuse.org/tests/3455439#step/firstrun/5

Also filed an issue in GitHub: https://github.com/yast/yast-users/issues/389
Comment 2 Ana Guerrero 2023-07-27 17:56:37 UTC 
There is a pull request for this on the works:
https://github.com/yast/yast-firstboot/pull/146

Stefan: I'm sorry this bug report wasn't helpful for you, feel free to ignore it ;)
Comment 3 Ana Guerrero 2023-07-28 11:10:55 UTC 
For the record, yast2-users was reverted in Factory to 4.6.2
Comment 4 Stefan Hundhammer 2023-08-07 13:25:36 UTC 
So it now works with Ancor's PR.

My point about this bug was that there was no useful bug subject, bug description or description of the OpenQA test case.

A good bug subject would have been something like "YaST installation internal error: require y2users/commit_config_collection".

A good bug description would have been something like "The YaST installation crashes with an internal error about require y2users/commit_config_collection", or better yet, paste the exact error.

Our problem is and has been for the past 8+ years that we typically have to reverse engineer OpenQA tests by trying to figure out screenshots and what the whole test sequence might do. More often than not, it's 200+ screenshots, frequently with dozens of screens full of shell commands; and mostly no useful description what the whole test sequence does, let alone individual steps. Hence that document from comment #1.