Project

General

Profile

action #35631

action #34411: [sle][migration] Bsc#1086818 Migration: new modules not correctly added

[sle][functional][u] Check that SLE modules are correctly registered after installation with SUSEConnect

Added by okurz over 3 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
Low
Assignee:
Category:
New test
Target version:
SUSE QA - Milestone 22
Start date:
2018-04-27
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

As was discovered in bsc#1086818 it can happen that modules are not properly registered after migration. For installation AFAIK we also do not check this after installation for a registered system.

Acceptance criteria

  • AC1: At least the SLE15 basesystem module is checked for proper registration after a registered installation

Suggestions

  • Check existing test modules doing something with SUSEConnect, e.g. git grep -i suseconnect in os-autoinst-distri-opensuse
  • Ensure that there is a corresponding test that checks for a registered SLE15 basesystem module on a registered installation
  • Prevent new duplication and cleanup existing duplication

History

#1 Updated by okurz over 3 years ago

  • Status changed from New to Workable

#2 Updated by okurz over 3 years ago

  • Target version changed from Milestone 19 to Milestone 19

#3 Updated by okurz about 3 years ago

  • Target version changed from Milestone 19 to Milestone 22

#4 Updated by okurz about 3 years ago

  • Status changed from Workable to Rejected
  • Assignee set to okurz

Currently I do not see the need for this. I mean: If all our tests pass but the repos are not registered, what is the problem for us? :) I see the need for migration and qam tests but this is out of scope for us.

Also available in: Atom PDF