Project

General

Profile

Actions

action #27028

closed

[sle][functional]test fails in addon_products_via_SCC_yast2 - test does not expect that the system is already registered

Added by okurz over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2017-10-25
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-Installer-DVD-ppc64le-sles+sdk+proxy_SCC_via_YaST@ppc64le fails in
addon_products_via_SCC_yast2
because the test module expects the SLE installation to be not yet registered but it is on SLE15.

Reproducible

Fails since (at least) Build 302.1

Problem

On SLE 12 SP3 the test was called on an unregistered SLES. For SLE15 we can't do that because we would not have the package available at all when booting an unregistered system ("minimal"). Instead it must be registered already in before. Originally the test module was developed to test how addons can be added from SCC fsc#321044.

Suggestion

  • Adapt the test module to also accept an already registered system as alternative and enable an additional module/addon that was not yet enabled, e.g. "legacy" (1-4h)

Further details

Always latest result in this scenario: latest


Related issues 1 (0 open1 closed)

Is duplicate of openQA Tests - action #26984: [sle][functional][y] New test scenario: minimal+proxy_SCC-postreg_yast_sccRejectedriafarov2017-10-24

Actions
Actions #1

Updated by okurz over 6 years ago

  • Related to action #26984: [sle][functional][y] New test scenario: minimal+proxy_SCC-postreg_yast_scc added
Actions #2

Updated by SLindoMansilla over 6 years ago

  • Related to deleted (action #26984: [sle][functional][y] New test scenario: minimal+proxy_SCC-postreg_yast_scc)
Actions #3

Updated by SLindoMansilla over 6 years ago

  • Is duplicate of action #26984: [sle][functional][y] New test scenario: minimal+proxy_SCC-postreg_yast_scc added
Actions #4

Updated by SLindoMansilla over 6 years ago

  • Status changed from In Progress to Resolved

Resolved as duplicate.

Actions #5

Updated by okurz over 6 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: sles+sdk+proxy_SCC_via_YaST
https://openqa.suse.de/tests/1245411

Actions #6

Updated by okurz over 6 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: sles+sdk+proxy_SCC_via_YaST
https://openqa.suse.de/tests/1268789

Actions #7

Updated by okurz over 6 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: sles+sdk+proxy_SCC_via_YaST
https://openqa.suse.de/tests/1302509

Actions

Also available in: Atom PDF