Project

General

Profile

Actions

action #153328

closed

jenkins fails in submit-openQA-TW-to-oS_Fctry, Server returned an error: HTTP Error 400: Bad Request size:M

Added by nicksinger 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
Start date:
2024-01-10
Due date:
% Done:

0%

Estimated time:

Description

Observation

http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/975 fails with:

+ curl -sS 'https://api.opensuse.org/public/build/devel:openQA:tested/_result?repository=openSUSE_Factory&package=os-autoinst'
+ grep -e '\(unknown\|blocked\|scheduled\|dispatching\|building\|signing\|finished\)'
curl: (28) Failed to connect to api.opensuse.org port 443 after 129973 ms: Couldn't connect to server
…
+ osc service wait devel:openQA os-autoinst-distri-opensuse-deps
Server returned an error: HTTP Error 400: Bad Request
The service for project 'devel:openQA' package 'os-autoinst-distri-opensuse-deps' failed
service error: '
+ rm -rf /tmp/os-autoinst-obs-auto-submit-vn8K

The error message unfortunately doesn't tell us much. Maybe this can be improved for the future? Error 400 indicates we're using the API wrong, did something change we didn't notice?

Suggestions

  • Check the jenkins job if error output can be fixed
  • Check if something with OBS changed and we need to update the client or might have to adapt our script(s)
  • Run the failing command manually, find out if it's reproducible/sporadic?
    • It works locally on TW and Leap 15.5
  • jenkins.qe.nue2.suse.org has the same osc package version as other hosts so it's not an outdated package
  • Ask for help in OBS related channels
  • Improve the error handling in the pipleine script

Related issues 1 (0 open1 closed)

Related to openQA Infrastructure - action #153325: osd-deployment | Failed pipeline, Digest verification failed for openQA-common size:MResolvednicksinger2024-01-10

Actions
Actions

Also available in: Atom PDF