Bug 1219602

Summary:	[Build 20240205] openQA test fails in apptainer: repo refresh fails (all other tests pass?)
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Dominique Leuenberger <dimstar>
Component:	Other	Assignee:	Christian Goll <cgoll>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
URL:	https://openqa.opensuse.org/tests/3918263/modules/apptainer/steps/40
Whiteboard:
Found By:	openQA	Services Priority:
Business Priority:		Blocker:	Yes
Marketing QA Status:	---	IT Deployment:	---

Description Dominique Leuenberger 2024-02-06 08:08:39 UTC

## Observation

apptainer seems to have a problem refreshing the repo and keeps on receiving invalid repo metadata. Considering all other tests work/pass, it seems unlikely that the repo is really broken.

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_hpc_apptainer@64bit fails in
[apptainer](https://openqa.opensuse.org/tests/3918263/modules/apptainer/steps/40)

## Test suite description
Maintainer: dheidler. Extra tests about CLI software in container module
2023-08-10/dimstar: added QEMURAM=2048 (boo#1212824)


## Reproducible

Fails since (at least) Build [20240204](https://openqa.opensuse.org/tests/3916487)


## Expected result

Last good: [20240202](https://openqa.opensuse.org/tests/3913568) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=containers_hpc_apptainer&version=Tumbleweed)

Comment 1 Dominique Leuenberger 2024-02-07 07:57:20 UTC

As magically as it appeared, it also vanished again:

https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=containers_hpc_apptainer&version=Tumbleweed#next_previous

Despite all other tests passing and apptainer being the only one failing, I think we still hit some infra issues in this case -the larger glibc/python312 rebuild might have made it a bit less reliable than we wished for.

Unless this shows up again in the next few days, I'll consider this bug invalid