Project

General

Profile

Actions

action #104112

closed

[qe-core] test fails in validate_repos - minimal+proxy_SCC-postreg_SUSEconnect seems to be redundant with offline_install+skip_registration

Added by szarate over 3 years ago. Updated about 2 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-12-16
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

https://openqa.suse.de/tests/7856015 and this test seem to be doing similar things, is this something we actually need to run? does the yast team actually need to run a full install to do the same checks?

openQA test in scenario sle-15-SP4-Full-aarch64-minimal+proxy_SCC-postreg_SUSEconnect@aarch64 fails in
validate_repos

Test suite description

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainers: riafarov.
Register modules after a system is installed using SUSEconnect.

Reproducible

Fails since (at least) Build 67.2

Expected result

Last good: 64.17 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (0 open1 closed)

Related to qe-yam - coordination #102314: [Epic] Move YaST related scenarios from functional to YaST group and use YuiRestClientResolved2021-11-12

Actions
Actions #1

Updated by szarate over 3 years ago

  • Related to coordination #102314: [Epic] Move YaST related scenarios from functional to YaST group and use YuiRestClient added
Actions #2

Updated by slo-gin over 2 years ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #3

Updated by slo-gin about 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #4

Updated by slo-gin about 2 months ago

  • Priority changed from Normal to Low

This ticket was set to Normal priority but was not updated within the SLO period. The ticket will be set to the next lower priority Low.

Actions #5

Updated by mgrifalconi about 2 months ago

  • Status changed from New to Rejected

Latest result is 3 years ago, possibly not relevant anymore

Actions

Also available in: Atom PDF