Project

General

Profile

Actions
Copy link

action #165405

closed

GitHub CI workflow in os-autoinst/scripts triggering openQA jobs to generate pflash images stopped working size:S

Added by livdywan 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
livdywan
Category:
Regressions/Crashes
Target version:
Ready
Start date:
Due date:
% Done:

20%

Estimated time:
Tags:
reactive work

Description

Observation

The GitHub CI workflow in os-autoinst/scripts triggering pflash jobs stopped working:

+ openqa-cli api --host https://openqa.opensuse.org -X POST jobs --apikey *** --apisecret *** TEST=ovmf-resolution@x86_64 QEMUVGA=qxl UEFI=1 UEFI_PFLASH_CODE=/usr/share/qemu/ovmf-x86_64-ms-code.bin UEFI_PFLASH_VARS=/usr/share/qemu/ovmf-x86_64-ms-vars.bin PUBLISH_PFLASH_VARS=ovmf-x86_64-ms-vars-800x600.qcow2 DISTRI=openSUSE VERSION=Tumbleweed FLAVOR=NET ARCH=x86_64 SCHEDULE=tests/boot/tianocore_set_resolution ISO=openSUSE-Tumbleweed-NET-x86_64-Snapshot20240809-Media.iso TRIGGERED_BY=https://github.com/os-autoinst/scripts/blob/master/./trigger-pflash-test
71
403 Forbidden
72
{"error":"api key expired","error_status":403}

See #113794#note-30 for the original implementation

Acceptance criteria

  • AC1: pflash images are generated on a regular schedule

Suggestions

Related issues 1 (0 open — 1 closed)

Copied from openQA Project (public) - action #113794: Use prepared OVMF image with expected settings size:MResolvedtinita2022-06-03

Actions
Actions
Copy link
 #1

Updated by livdywan 4 months ago

  • Copied from action #113794: Use prepared OVMF image with expected settings size:M added
Actions
Copy link
 #2

Updated by okurz 4 months ago

  • Target version set to Ready
Actions
Copy link
 #3

Updated by livdywan 4 months ago

  • Subject changed from GitHub CI workflow in os-autoinst/scripts triggering openQA jobs to generate pflash images stopped working to GitHub CI workflow in os-autoinst/scripts triggering openQA jobs to generate pflash images stopped working size:S
  • Description updated (diff)
  • Status changed from New to Workable
Actions
Copy link
 #4

Updated by livdywan 4 months ago ยท Edited

  • Status changed from Workable to In Progress
  • Assignee set to livdywan

It looks like there's an API key defined even though we have one of the same name in the organization? Namely OPENQA_API_KEY/OPENQA_API_SECRET. Maybe we can just re-use it? Let's see.

Actions
Copy link
 #5

Updated by livdywan 4 months ago

  • Status changed from In Progress to Resolved
Actions
Copy link

Also available in: Atom PDF