action #99672
closed
[openqa][tools] Non-existing `…-uefi-vars.qcow2` asset disturbs openqa-clone-job workflow
Added by zluo about 3 years ago.
Updated about 3 years ago.
Category:
Regressions/Crashes
- Category set to Regressions/Crashes
- Priority changed from Normal to High
- Target version set to Ready
uefi-vars.qcow2 is a common problem. It's one of the dreaded consequences of the os-autoinst commit
commit c670720d
Author: Richard Palethorpe rpalethorpe@suse.com
Date: Thu Mar 8 15:16:39 2018 +0100
The Great QEMU Rewrite of 2018
See #98388 for a related issue.
What we should focus on really quick is a feasible workaround.
- Related to action #98388: Non-existing asset "uefi-vars" is still shown up on #downloads added
It is basically the same as #98388. There's also a PR to be able to ignore missing assets when cloning a job to mitigate the issue: https://github.com/os-autoinst/openQA/pull/4214
It hasn't been merged yet, I suppose mainly because tests were missing. I'll re-review it.
- Subject changed from [openqa][tools] assert is missing to [openqa][tools] Non-existing `…-uefi-vars.qcow2` asset disturbs openqa-clone-job workflow
- Status changed from New to In Progress
- Assignee set to mkittler
I've been adding tests for https://github.com/os-autoinst/openQA/pull/4214 so it can hopefully be merged soon.
I'm assigning this to myself for now but it would be great to know whether this workaround is good enough for you.
Maybe we should also ignore missing …-uefi-vars.qcow2-assets by default in openqa-clone-job. That would be yet another place where we treat this kind of asset in a special way.
- Status changed from In Progress to Feedback
- Status changed from Feedback to In Progress
- Due date set to 2021-10-20
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Resolved
The PR has been merged so cloning jobs like the one mentioned in the PR description works now out of the box.
Also available in: Atom
PDF