action #151891
closedcoordination #151822: [epic] Soft-fails mitigation
Revisit soft-failure bsc#1189543
Added by JERiveraMoya 7 months ago. Updated about 1 month ago.
0%
Description
Motivation¶
See parent epic.
https://openqa.suse.de/tests/13959334#step/scc_deregistration/11
https://openqa.suse.de/tests/13959334#step/patch_sle/97
-> bsc#1189543
Acceptance criteria¶
AC1: Revisit soft-failure bsc#1189543
Updated by JERiveraMoya 6 months ago
- Tags changed from qe-yam-dec-sprint, qe-yam-jan-sprint to qe-yam-jan-sprint
Updated by JERiveraMoya 5 months ago
- Tags changed from qe-yam-jan-sprint to qe-yam-feb-sprint
Updated by JERiveraMoya 5 months ago
- Tags changed from qe-yam-feb-sprint to qe-yam-mar-sprint
Updated by JERiveraMoya 3 months ago
- Tags changed from qe-yam-mar-sprint to qe-yam-apr-sprint
Updated by JERiveraMoya 2 months ago
- Tags changed from qe-yam-apr-sprint to qe-yam-may-sprint
Updated by leli about 2 months ago
- Status changed from Workable to In Progress
- Assignee set to leli
Updated by leli about 2 months ago
If we removed the softfail the test passed, http://openqa.suse.de/tests/14297018#step/scc_deregistration/12, so that means the workaround is not needed for installation process.
Updated by JERiveraMoya about 2 months ago
leli wrote in #note-10:
If we removed the softfail the test passed, http://openqa.suse.de/tests/14297018#step/scc_deregistration/12, so that means the workaround is not needed for installation process.
There were plenty of occurrences of this one iirc, could you please check?
Updated by leli about 2 months ago
JERiveraMoya wrote in #note-11:
leli wrote in #note-10:
If we removed the softfail the test passed, http://openqa.suse.de/tests/14297018#step/scc_deregistration/12, so that means the workaround is not needed for installation process.
There were plenty of occurrences of this one iirc, could you please check?
Ok, I will check these installation process and migration process also.
Updated by leli about 2 months ago
For installation process, it is not needed to have the workaround for python2, all test passed without the workaround http://openqa.suse.de/tests/overview?version=15-SP6&build=lemon-suse%2Fos-autoinst-distri-opensuse%23revisit-bsc%231189543&distri=sle
Now we haven't such test scenarios that migration from <15SP3 to 15SP3, we should reserve this workaround and correct the condition to make it only work for migration process while not installation.
Updated by JERiveraMoya about 2 months ago
leli wrote in #note-13:
For installation process, it is not needed to have the workaround for python2, all test passed without the workaround http://openqa.suse.de/tests/overview?version=15-SP6&build=lemon-suse%2Fos-autoinst-distri-opensuse%23revisit-bsc%231189543&distri=sle
Now we haven't such test scenarios that migration from <15SP3 to 15SP3, we should reserve this workaround and correct the condition to make it only work for migration process while not installation.
so you mean that it might be useful to have it for the moment we add some migration in maintenance If I understand correctly, then yes, let's update the condition, sounds like a plan.
Updated by leli about 2 months ago
JERiveraMoya wrote in #note-14:
leli wrote in #note-13:
For installation process, it is not needed to have the workaround for python2, all test passed without the workaround http://openqa.suse.de/tests/overview?version=15-SP6&build=lemon-suse%2Fos-autoinst-distri-opensuse%23revisit-bsc%231189543&distri=sle
Now we haven't such test scenarios that migration from <15SP3 to 15SP3, we should reserve this workaround and correct the condition to make it only work for migration process while not installation.
so you mean that it might be useful to have it for the moment we add some migration in maintenance If I understand correctly, then yes, let's update the condition, sounds like a plan.
No such migration scenario caused we can't confirm whether the workaround still needed for migration process, I will add a such migration test (SP2 to SP3) in development group to check this. If confirmed still need the workaround then file PR to update condition.
I'm not sure whether we need add such migration scenarios in maintenance, even we already have a sp2 to sp3 migration test(migr_sles15sp2_sp3) in maintenance but that test won't test this since haven't run same de-register cmd there.
Updated by leli about 2 months ago
The migration test for sp2 to sp3 passed without the workaround, http://openqa.suse.de/tests/14310970#step/scc_deregistration/11
Updated by leli about 2 months ago
Updated by leli about 1 month ago
- Status changed from In Progress to Resolved
Verified on OSD, https://openqa.suse.de/tests/14369193