Actions
action #133514
open[qe-core] zypper lifecycle fails currently, but not seen by openqa.
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2023-07-28
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
If you enable the Livepatching extension and run
"zypper lifecycle"
it currently fails with:
Error parsing ["kernel-livepatch-5_14_21-150500_11-rt", "*", "TBD"]: no time information in "TBD"
but this was not seen by QA.
Updated by maritawerner 9 months ago
- Subject changed from zypper lifecycle fails currently, but not seen by openqa. to [qe-core] zypper lifecycle fails currently, but not seen by openqa.
Updated by MDoucha 9 months ago
- Tags set to kernel
- Subject changed from [qe-core] zypper lifecycle fails currently, but not seen by openqa. to [kernel] zypper lifecycle fails currently, but not seen by openqa.
- Category set to Enhancement to existing tests
- Assignee set to MDoucha
- Target version set to 640
Basic incident tests are not run for livepatches so we need to add the zypper_lifecycle
test to one of the kernel livepatching jobs. I'll do it today.
Updated by maritawerner 9 months ago
- Project changed from openQA Tests to 178
- Category deleted (
Enhancement to existing tests)
Updated by MDoucha 9 months ago
- Tags deleted (
kernel) - Project changed from 178 to openQA Tests
- Subject changed from [kernel] zypper lifecycle fails currently, but not seen by openqa. to [qe-core] zypper lifecycle fails currently, but not seen by openqa.
- Assignee deleted (
MDoucha) - Target version deleted (
640)
OK, never mind, running the lifecycle test on kernel-livepatch-*
package updates is pointless because lifecycle data is distributed in its own package: lifecycle-data-sle-module-live-patching
(SLE-Module-Live-Patching). This needs to be handled by qe-core.
Actions