coordination #47195
closed
[sle][migration][functional][u][epic] check orphaned_packages_check.pm for SLE installation tests
Added by maritawerner over 5 years ago.
Updated over 3 years ago.
Target version:
SUSE QA - Milestone 28
Estimated time:
(Total: 6.00 h)
Description
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 orphaned_packages_check.pm test to prevent such orphaned issue.
Now I wanted to bring this topic to QA and other PrjMgr/RM because:
orphaned_packages_check.pm 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 orphaned_packages_check.pm require to manually check the output, is there
a way to automate this somehow?
What about other product, do they use orphaned_packages_check.pm, something
else, or nothing?
See also:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/console/orphaned_packages_check.pm
- Category set to New test
- Status changed from New to Blocked
- Target version set to Milestone 24
- Subject changed from [sle][functional] check orphaned_packages_check.pm for SLE installation tests to [sle][migration][functional][u][epic] check orphaned_packages_check.pm for SLE installation tests
- Target version changed from Milestone 24 to Milestone 25
- 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.
Hello Matthias, any update here? I think for JeOs that is quite important.
- 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
- Target version changed from Milestone 26 to Milestone 28
still waiting for migration tasks to be done
- Status changed from Blocked to Resolved
subtickets closed, considering resolved
Hi,
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.
- Tracker changed from action to coordination
Also available in: Atom
PDF