action #51629: [functional][u] SES6: bring back BETA=1 param - openQA Tests - openSUSE Project Management Tool

Actions

Copy link

action #51629

closed

[functional][u] SES6: bring back BETA=1 param

Added by SShyukriev almost 5 years ago. Updated almost 5 years ago.

Status:

Resolved

Priority:

Urgent

Assignee:

dzedro

Category:

Bugs in existing tests

Target version:

SUSE QA - Milestone 25

Start date:

2019-05-20

Due date:

% Done:

100%

Estimated time:

Difficulty:

Description

Observation¶

SES6 is still in Beta phase. But, since the setting BETA=1 was removed from medium SLE15-SP1, it is affecting SES tests.

Reproducible¶

Since Build 58.3
Last reproducer: create_hdd_ses_textmode
in sle-15-SP1-Installer-DVD-SES-x86_64-create_hdd_ses_textmode@64bit

Expected result¶

Last good: 58.2

Suggestions¶

Use a different medium for SES so that BETA setting can be configured separately?

Further details¶

Always latest result in this scenario: latest

Actions

Copy link

Updated by SLindoMansilla almost 5 years ago

Subject changed from SES6: bring back BETA=1 param to [functional][u] SES6: bring back BETA=1 param
Description updated (diff)
Priority changed from Normal to Immediate

Actions

Copy link

Updated by mgriessmeier almost 5 years ago

Status changed from New to Feedback
Assignee set to SLindoMansilla
Priority changed from Immediate to Urgent
Target version set to Milestone 25

sorry, but the only way I see here is to use your own medium for SES - we do that for example as well for caasp or jeos.
Products with different schedules should not use the same medium because it will always conflict.

If you need help with creating it, let us know.

Actions

Copy link

Updated by riafarov almost 5 years ago

So, actual issue is that SES6 has different release schedule than SLES, but seems to be triggered by SLES build which was not in the beta phase anymore. This is one of the issues we have during GMC phase, which is not easy to solve and which got postponed last time as happens once per release. I believe we should address it this time.

UPD: I haven't seen comment from Matthias when was writing mine, but consider it as +1 to the comment above.

Actions

Copy link