Project

General

Profile

Actions

action #14692

closed

Running zypper_lifecycle on unpatched system reveals different results

Added by coolo over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2016-11-08
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

https://openqa.suse.de/tests/629724#step/zypper_lifecycle/7 - we need to move this test after the update tests


Related issues 1 (0 open1 closed)

Blocks openQA Tests - coordination #13040: [functional][epic][u]more flexible console test selection by addons, testsuite variable, etc. (was: Run zypper lifecycle more selectively)Rejected2016-08-05

Actions
Actions #1

Updated by okurz over 7 years ago

  • Assignee set to nadvornik

@nadvornik, can you please help with this?

Actions #2

Updated by okurz over 7 years ago

  • Blocks coordination #13040: [functional][epic][u]more flexible console test selection by addons, testsuite variable, etc. (was: Run zypper lifecycle more selectively) added
Actions #3

Updated by nadvornik over 7 years ago

I think that the assertion "All packages within base distribution should have same EOL" is not correct in general. The purpose of zypper-lifecycle is to set EOL of each package individually.

I will remove it.

Actions #4

Updated by nadvornik over 7 years ago

  • Status changed from New to In Progress
Actions #5

Updated by nadvornik over 7 years ago

  • Status changed from In Progress to Resolved

fixed

Actions

Also available in: Atom PDF