action #157411
closed
coordination #151816: [epic] Handle openQA fixes and job group setup
Import untrusted GnuPG key for online migration test
Added by leli 2 months ago.
Updated 5 days ago.
Description
Motivation¶
We filed bug 1221444, Rado added comments that is for 'Repo key changed'. We can import the untrusted GnuPG key for online migration test. This should work on both zypper migration and yast migration test.
Failed jobs: zypper migration
yast migration
Acceptance criteria¶
AC1: Import untrusted GnuPG key for online migration test
- Tags set to qe-yam-mar-sprint
- Status changed from New to Workable
- Priority changed from Normal to Urgent
- Parent task set to #151816
At the end we have to work in parallel with this (and await for answer in the bug) but functionally is correct to accept the key, so we should not loose test coverage.
- Due date set to 2024-03-27
- Status changed from Workable to In Progress
- Assignee set to tinawang123
- Tags changed from qe-yam-mar-sprint to qe-yam-apr-sprint
- Status changed from In Progress to Resolved
- Due date deleted (
2024-03-27)
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: migration_online_sle15sp3_ha_alpha_node01
https://openqa.suse.de/tests/14280842#step/zypper_migration/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
- Status changed from Feedback to Resolved
The failed job is not related with this ticket.
Close it.
Also available in: Atom
PDF