Project

General

Profile

Actions

action #66913

closed

[functional][y] test fails in suseconnect_scc, desktop applications module is not activated

Added by JRivrain almost 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-05-20
Due date:
2020-06-02
% Done:

0%

Estimated time:
3.00 h
Difficulty:

Description

Observation

It looks like suseconnect return code was corrected, so now our tests fails, as it should always have, on that dependency problem.

We need to enable desktop applications module before trying to enable development tools.

openQA test in scenario sle-15-SP2-Full-x86_64-allmodules+allpatterns+registration@64bit fails in
suseconnect_scc

Test suite description

Full Medium installation that covers the following cases:
1. Additional modules enabled using SCC (Legacy, Development Tools, Web and
Scripting, Containers, Desktop Applications);
2. All patterns installed;
3. System registration is skipped during installation;
4. Installation is validated by successful boot and that YaST does not
report any issues;
5. Registration is performed on the installed system.

Reproducible

Fails since (at least) Build 194.1 (current job)

Expected result

Last good: 191.1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by ybonatakis almost 4 years ago

The commit which caused this was https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10259. But there are two occasions here. One is that the Development Tools tries to be installed before the Desktop, which is a dependency on the first. When this is fixed then we encounter the issue that was introduced by the fix on the above PR

Actions #2

Updated by riafarov almost 4 years ago

  • Subject changed from [functional][y] test fails in suseconnect_scc to [functional][y] test fails in suseconnect_scc, desktop applications module is not activated
  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 3.00 h
Actions #3

Updated by ybonatakis almost 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to ybonatakis
Actions #5

Updated by ybonatakis almost 4 years ago

SCC_ADDONS=base,legacy,serverapp,sdk,script,contm ahs been added to the test_suite

Actions #6

Updated by ybonatakis almost 4 years ago

ybonatakis wrote:

SCC_ADDONS=base,legacy,serverapp,sdk,script,contm ahs been added to the test_suite

Actually base and serverapp is not needed as they are activated by SUSEConnect -r $reg_code --url SCC_URL

Actions #7

Updated by ybonatakis almost 4 years ago

  • Status changed from In Progress to Resolved

Merged and all the jobs passed

Actions #8

Updated by openqa_review over 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: allmodules+allpatterns+registration
https://openqa.suse.de/tests/4541155

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions

Also available in: Atom PDF