Project

General

Profile

Actions
Copy link

action #163622

closed

Scripts CI pipeline failing with invalid numeric literal error size:S

Added by livdywan 17 days ago. Updated 1 day ago.

Status:
Resolved
Priority:
Normal
Assignee:
jbaier_cz
Category:
Regressions/Crashes
Target version:
openQA Project - Ready
Start date:
Due date:
% Done:

0%

Estimated time:
Tags:
alert, infra, reactive work

Description

Observation

Scripts CI pipeline on GitLab is failing with an error:

++ openqa-cli api --host http://openqa.suse.de jobs version=15-SP5 scope=relevant arch=x86_64 flavor=Server-DVD-Updates test=ovs-client latest=1
++ jq -r '.jobs | map(select(.result == "passed")) | max_by(.settings.BUILD) .settings.HDD_1'
jq: parse error: Invalid numeric literal at line 1, column 8

Acceptance Criteria

  • AC1: Scripts CI pipeline consistently passes
  • AC2: We have access to the input of jq and know the the HTTP error code

Suggestions

  • Print the api output before passing it to jq to see what we actually got
  • Consider other potentially related issues explaining the root cause triggering the problem, e.g. see #163592
  • Ensure that openqa-cli api actually returns an error if the response is not something usable, e.g. an error and not JSON
  • Check how we invoke jq in the scripts repo and maybe reuse the _common file as we already download a file from that repo but should clone the repo or something

Related issues 1 (0 open — 1 closed)

Related to openQA Infrastructure - action #163592: [alert] (HTTP Response alert Salt tm0h5mf4k) size:MResolvedokurz2024-07-10

Actions
Actions
Copy link
 #1

Updated by okurz 17 days ago

  • Related to action #163592: [alert] (HTTP Response alert Salt tm0h5mf4k) size:M added
Actions
Copy link
 #2

Updated by okurz 17 days ago

I am surprised you don't mention the relation to #163592

Actions
Copy link
 #3

Updated by livdywan 17 days ago

okurz wrote in #note-2:

I am surprised you don't mention the relation to #163592

I might have if I understood the error.

Actions
Copy link
 #4

Updated by tinita 17 days ago

It ran at 4:13 GMT+2 so it doesn't seem related. We had already disabled the streaming route then, right?

Actions
Copy link
 #5

Updated by tinita 17 days ago

  • Description updated (diff)
Actions
Copy link
 #6

Updated by okurz 17 days ago

  • Target version set to Ready
Actions
Copy link
 #7

Updated by okurz 15 days ago

  • Subject changed from Scripts CI pipeline failing with invalid numeric literal error to Scripts CI pipeline failing with invalid numeric literal error size:S
  • Description updated (diff)
  • Status changed from New to Workable
Actions
Copy link
 #8

Updated by jbaier_cz 5 days ago

  • Status changed from Workable to In Progress
  • Assignee set to jbaier_cz
Actions
Copy link
 #9

Updated by jbaier_cz 5 days ago

Better logging should be handled by https://github.com/os-autoinst/scripts/pull/329

Actions
Copy link
 #10

Updated by jbaier_cz 5 days ago

Meh.. now we have too much information: Job's log exceeded limit of 4194304 bytes.

Actions
Copy link
 #11

Updated by openqa_review 5 days ago

  • Due date set to 2024-08-06

Setting due date based on mean cycle time of SUSE QE Tools

Actions
Copy link
 #12

Updated by jbaier_cz 2 days ago

  • Status changed from In Progress to Feedback

Printing API output everytime is not an option here (the output is too long), so I re-used the runjq wrapper from the _common which should output some details in case of failure. So far all pipelines succeeded (or failed due to other reasons), so I cannot reliably say if AC2 was fulfiled.

I will put this on feedback for a while to monitor the impact of the change.

Actions
Copy link
 #13

Updated by jbaier_cz 1 day ago

  • Status changed from Feedback to Resolved

I guess it is OK

Actions
Copy link
 #14

Updated by jbaier_cz 1 day ago

  • Due date deleted (2024-08-06)
Actions
Copy link

Also available in: Atom PDF