Bug 1212273 - [Build 20230612-1] 15-SP5 & 15-SP4 openQA test fails in scc_registration - file is not digitally signed
Summary: [Build 20230612-1] 15-SP5 & 15-SP4 openQA test fails in scc_registration - fi...
Status: RESOLVED FIXED
Alias: None
Product: PUBLIC SUSE Linux Enterprise Server 15 SP5
Classification: openSUSE
Component: Registration (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: SCC Bugs
QA Contact: Hernan Schmidt
URL: https://openqa.suse.de/tests/11329226...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-13 13:29 UTC by Timo Jyrinki
Modified: 2023-06-16 13:08 UTC (History)
2 users (show)

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Timo Jyrinki 2023-06-13 13:29:12 UTC 
## Observation

openQA test in scenario sle-15-SP5-Server-DVD-Updates-aarch64-mru-install-minimal-with-addons-cc@aarch64-virtio fails in
[scc_registration](https://openqa.suse.de/tests/11329226/modules/scc_registration/steps/35)

Fails adding SLE-Module-Server-Applications/15-SP5. Last passed June 8th at https://openqa.suse.de/tests/11282500 - after that always failing, first with "cannot access" at https://openqa.suse.de/tests/11289882#step/scc_registration/8 and then this cited in this bug report for example at https://openqa.suse.de/tests/11292084#step/scc_registration/7

There is no such problem on x86_64: https://openqa.suse.de/tests/11323341#step/scc_registration/6

15-SP4 fails similarly https://openqa.suse.de/tests/11329116#step/scc_registration/30 , this example from s390x (another s390x example https://openqa.suse.de/tests/11329144#step/accept_license/1) while aarch64 over there succeeded: https://openqa.suse.de/tests/11323205#step/scc_registration/6

These problems all around (but not on every arch/product combination) is maybe related to bsc#1212134 that started around the same time.
Comment 1 Timo Jyrinki 2023-06-13 13:37:32 UTC 
(or: is this bsc#1212187 ie CDN update.suse.com problem?)
Comment 2 Thomas Schmidt 2023-06-13 14:50:35 UTC 
I suspect this to be caused by bsc#1212134. 
Let's wait if this works again when the signing keys are fixed.
Comment 3 Thomas Schmidt 2023-06-16 11:58:09 UTC 
Could you please retry?
Comment 4 Timo Jyrinki 2023-06-16 13:08:56 UTC 
Seems passing now, hopefully it will stay this way!

https://openqa.suse.de/tests/11364799