action #180866
closedhttp://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/3452/console shows error or warning(?) "404 unknown repository 'openSUSE_Leap_15.6" size:S
0%
Description
Observation¶
From http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/ (old builds get deleted apparently hence no deep link):
…
Waiting while openQA is in progress
<result project="devel:openQA:tested" repository="openSUSE_Factory" arch="x86_64" code="building" state="building">
Waiting while openQA is in progress
<result project="devel:openQA:tested" repository="openSUSE_Factory" arch="x86_64" code="building" state="building">
Waiting while openQA is in progress
created request id 1268562
<summary>unknown repository 'openSUSE_Leap_15.6'</summary>
<details>404 unknown repository 'openSUSE_Leap_15.6'</details>
<summary>unknown repository 'openSUSE_Leap_15.6'</summary>
<details>404 unknown repository 'openSUSE_Leap_15.6'</details>
Waiting while openQA is in progress
<summary>unknown repository 'openSUSE_Leap_15.6'</summary>
<details>404 unknown repository 'openSUSE_Leap_15.6'</details>
Waiting while openQA is in progress
…
Acceptance Criteria¶
- AC1: Jobs on Jenkins don't get stuck wrongly looking up e.g. openSUSE_Leap_15.6
Suggestions¶
- openSUSE_Leap_15.6 should be just "15.6" without the prefix "openSUSE_Leap_" after a change to use SLE binaries directly some years ago. Maybe we still have that setup wrongly in some OBS project or some tooling doing that?
- There is no such repo Leap 15.6
- See http://jenkins.qa.suse.de/job/trigger-openQA_in_openQA-TW/configure for the original trigger (based onhttp://download.opensuse.org/repositories/devel:/openQA/openSUSE_Tumbleweed/noarch/)
- Seems like jobs are getting stuck in a loop? Jobs seem to be running for almost 48hrs?
- Consider related work going on, maybe check with Yannis?
-
DONE Mitigate by cancelling the stuck job
- It apparently happened again after it was mitigated
- https://build.opensuse.org/requests/1271839
- Maybe see #127037 wrt Leap 15.6
- Also https://suse.slack.com/archives/C02AJ1E568M/p1744649410780819
Updated by livdywan about 2 months ago
- Related to action #127037: os-autoinst on SLE+packagehub size:M added
Updated by livdywan about 2 months ago
- Tags changed from reactive work, openqa-in-openqa, release to reactive work, openqa-in-openqa, release, infra
Updated by livdywan about 1 month ago
- Subject changed from http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/3452/console shows error or warning(?) "404 unknown repository 'openSUSE_Leap_15.6" to http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/3452/console shows error or warning(?) "404 unknown repository 'openSUSE_Leap_15.6" size:S
- Description updated (diff)
Updated by livdywan about 1 month ago
- Status changed from Workable to Feedback
- Assignee set to ybonatakis
Looked at this with @ybonatakis and aborted and re-triggered another job: http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/3561/console
[submit-openQA-TW-to-oS_Fctry] $ /bin/sh -xe /tmp/jenkins6379207212349867737.sh
+ os-autoinst-obs-auto-submit
Skipping submission, reason:
Only triggering tests from devel:openQA (not overriding devel:openQA:testing and doing a submission) because openQA-in-openQA tests or a submission is still pending (as devel:openQA:testing still contains packages: openQA
openQA-devel-container
os-autoinst
os-autoinst-distri-opensuse-deps
xterm-console)
Maybe we didn't abort it properly before?
Updated by livdywan about 1 month ago
- Assignee changed from ybonatakis to livdywan
Maybe we didn't abort it properly before?
I'm reverting the original changes to os-autoinst-obs-auto-submit
. After discussing #127037 I'm still unclear what needs to happen and in the meantime those submissions are not helpful. Maybe we need to side-by-side compare the different options and decide on one.
Updated by livdywan about 1 month ago
- Status changed from Feedback to Resolved
I assume we're good here.
Updated by ybonatakis about 1 month ago
- Status changed from Resolved to Feedback
Actual fix in https://github.com/os-autoinst/scripts/pull/393.
I will put this in feedback for you Liv, in case you want to double check
Updated by livdywan about 1 month ago
- Status changed from Feedback to Resolved
I will put this in feedback for you Liv, in case you want to double check
As far as I'm aware there is no issues with Jenkins right now, so nothing to do here. Thank you for checking, though.