coordination #47195


[sle][migration][functional][u][epic] check for SLE installation tests

Added by maritawerner over 5 years ago. Updated over 3 years ago.

New test
Target version:
SUSE QA - Milestone 28
Start date:
Due date:
% Done:


Estimated time:
(Total: 6.00 h)


Request from Vincent M.:

For the context, this started with bsc#1116740 - kernel-default-base not
provided in online channel, which is the most critical bugs we had in JeOS yet.
Since the issue was that kernel-default-base was an orphaned package therefore
JeOS users would never received any kernel updates…

After discussion inside the JeOS team, we came up with the decision to manually
use that test to prevent such orphaned issue.

Now I wanted to bring this topic to QA and other PrjMgr/RM because:

  • is ONLY used (AFAIK) during SLE migration test but
    not during regular build test. I.E checking orphaned packages from SPX when
    migrating to SPX+1. But no check to see if SPX+1 contains orphaned packages by
    himself, if this is a relevant test. Should we change that?

  • ATM require to manually check the output, is there
    a way to automate this somehow?

  • What about other product, do they use, something
    else, or nothing?

See also:

Subtasks 4 (0 open4 closed)

action #47333: [sle][Migration][SLE15SP2] automatic check in orphaned_packages_check.pmResolvedokurz2019-02-11

action #47336: [migration] - use for other products?Resolvedokurz2019-02-11

action #47339: [functional][u][easy] Trigger as part of functional checksResolvedzluo2019-02-11

action #47342: [functional][u][easy] Consolidate scheduleResolvedzluo2019-02-11

Actions #2

Updated by okurz over 5 years ago

  • Category set to New test
  • Status changed from New to Blocked
  • Target version set to Milestone 24

-> subtickets

Actions #3

Updated by okurz about 5 years ago

  • Subject changed from [sle][functional] check for SLE installation tests to [sle][migration][functional][u][epic] check for SLE installation tests
  • Target version changed from Milestone 24 to Milestone 25
Actions #4

Updated by ccret about 5 years ago

This bug is also related to this check:

Actions #5

Updated by okurz almost 5 years ago

  • Assignee changed from okurz to mgriessmeier

Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.

Actions #6

Updated by maritawerner almost 5 years ago

Hello Matthias, any update here? I think for JeOs that is quite important.

Actions #7

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 25 to Milestone 26

maritawerner wrote:

Hello Matthias, any update here? I think for JeOs that is quite important.

from the QSF-U side, this is done as far as I can tell from the resolved subtasks - to close this epic the migration tasks needs to be finished as well

Actions #8

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 26 to Milestone 28

still waiting for migration tasks to be done

Actions #9

Updated by mgriessmeier over 4 years ago

  • Status changed from Blocked to Resolved

subtickets closed, considering resolved

Actions #10

Updated by gameboy974 over 4 years ago

I'm no openQA expert, so I would like to kindly ask to have a summary of what you did to comply to this issue. To my understanding the orphaned_packages tests was only added to the migration test cases? Links to openQA tests might be also interesting to have.
Thanks a lot.

Vincent Moutoussamy.

Actions #11

Updated by okurz over 4 years ago

The points as mentioned in the ticket description have been adressed. For example the latest task I did was in #47333 with adding two commits, adding the check to more products and also during normal build validation tests as well as making the check a proper automated test which would fail if any unexpected (not whitelisted orphans) have been found. is an example showing the test module "orphaned_packages_check" being executed during a regular build validation test scenario.

Actions #12

Updated by szarate over 3 years ago

  • Tracker changed from action to coordination
Actions #14

Updated by gameboy974 over 3 years ago

szarate wrote:

See for the reason of tracker change:

I can not access this archive since I'm not a member : ). Could you please summarize what the "Tracker changed from action to coordination" means? and what was discussed in the ML thread?



Also available in: Atom PDF