action #125099
closedcoordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Update cases to use RMT server instead of SMT server to do register at milestone job group
Description
Motivation¶
SMT server has an error: Bug 1205411 - [Build 38.1] SMT self-signed certs not compatible with 15SP5 (relies on legacy Common Name field instead of SANs)
As comment: It's not clear if the SSL cert generation on SMT is going to get fixed, so I suggest to unblock the migration test, to switch it to RMT.
We need update cases to use RMT server instead of SMT server to do register.
Related test cases:
x86_64:
online_sled15sp4_smt_basesys-desk-we-phub-python3_def_full_y
online_sles15sp3_smt_basesys-srv-desk_def_full_zypp
online_sles15sp3_smt_basesys-srv-live-tsm_def_full_y
online_sles15sp4_smt_basesys-srv-live-tsm_all_full_y
s390x:
online_sles15sp3_smt_basesys-srv_all_full_zypp
online_sles15sp4_smt_basesys-srv_def_full_zypp
Aarch64:
online_sles15sp2_ltss_smt_base_all_minimal_zypp
online_sles15sp3_smt_basesys-srv-desk-pcm_all_full_zypp
online_sles15sp4_smt_basesys-srv-desk_def_full_zypp
Filter showing some of the failures:
https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=&modules=register_system&module_re=&modules_result=failed&distri=sle&version=15-SP5&build=72.4&groupid=266#
Acceptance criteria¶
AC1: Use RMT for the test cases listed above
Additional information¶
https://trello.com/c/bk5CJtv0/4670-smt-self-signed-certs-not-compatible-with-15sp5
Updated by JERiveraMoya about 1 year ago
- Description updated (diff)
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version set to Current
- Parent task set to #121876
Updated by JRivrain about 1 year ago
- Status changed from Workable to In Progress
- Assignee set to JRivrain
Updated by JRivrain about 1 year ago
Updated by JRivrain about 1 year ago
I disabled those test suites for now, we are not getting any response in the bug report.
Updated by rainerkoenig about 1 year ago
Got this automatic comment this morining in one of my resolved tickets that I resovled because this ticket exists:
https://progress.opensuse.org/issues/124916#note-6
Updated by JERiveraMoya about 1 year ago
@JRivrain could you please share the status here?
last thing discussed was that we didn't want to remove (or migrate to RMT) all the SMT test coverage, because there were still some test suite that were working and doing migration, but were failing later, and in those cases we will just unschedule that part that was failing.
Updated by JERiveraMoya about 1 year ago
- Status changed from In Progress to Workable
- Assignee deleted (
JRivrain)
Updated by leli about 1 year ago
- Status changed from Workable to In Progress
- Assignee set to leli
Updated by leli about 1 year ago
For online_sles15sp2_ltss_smt_base_all_minimal_zypp and online_sles15sp3_smt_basesys-srv-desk-pcm_all_full_zypp, we will unschedule check_system_info#1.
Updated by leli about 1 year ago
leli wrote:
For online_sles15sp2_ltss_smt_base_all_minimal_zypp and online_sles15sp3_smt_basesys-srv-desk-pcm_all_full_zypp, we will unschedule check_system_info#1.
Run VR but the two cases still fail for the bug, so we need move the two cases from smt to rmt also. https://openqa.suse.de/tests/10826017#step/welcome/7
Updated by leli about 1 year ago
Updated by JERiveraMoya about 1 year ago
- Status changed from In Progress to Resolved
ok, so in conclusion all smt scenarios are affected in different ways with bsc#1205411 and it not something that is going to be fixed any time soon and the recommendation from scc is to move to rmt.
Updated by JRivrain 12 months ago
Hi, the status of this is still the same, waiting for the bug to be resolved, what we discussed 2 months ago was that no, the suggestion to just remove all SMT tests is not what we want: we need that test coverage, we had discussed about that with Marita if I remember well. Switching to RMT was just a temporary solution. I tried some workaround back then -use http instead of https- but that did not work, and I got no response about it either in the bug report, see https://bugzilla.suse.com/show_bug.cgi?id=1205411#c8. We can't test SMT until the bug is resolved unless we find a different workaround. I think we need to keep track of that bug report and re-enable SMT tests when possible.