Project

General

Profile

action #11462

Feature 320597 and 320699: Introduce 'zypper lifecycle' to provide information about life cycle of individual products and packages and Do not communicate End of Support dates, that change later to a previous point in time

Added by maritawerner about 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Start date:
2016-04-01
Due date:
% Done:

70%

Estimated time:
Difficulty:
Duration:

Description

For details see https://fate.suse.com/320597

First check if the Feature status is "done".


In addition please extend the Testcase to test Feature 320699: Do not communicate End of Support dates, that change later to a previous point in time.

For details see https://fate.suse.com/320699

History

#1 Updated by dzedro about 4 years ago

wrong fate link ?

#2 Updated by RBrownSUSE about 4 years ago

  • Target version set to 168

#3 Updated by maritawerner about 4 years ago

  • Description updated (diff)

#4 Updated by maritawerner about 4 years ago

dzedro wrote:

wrong fate link ?

Sorry, fixed!

#5 Updated by RBrownSUSE about 4 years ago

  • Assignee set to dmaiocchi

#6 Updated by dmaiocchi about 4 years ago

  • Status changed from New to Rejected

feature is ready, not done.

Pending. Rejected for Milestone 3, for moment.

zypper se zypper
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S Name Zusammenfassung Typ
i zypper Command line software manager using libzypp package
zypper Command line software manager using libzypp srcpackage
zypper-docker Easy patch and update solution for Docker images srcpackage
zypper-docker Easy patch and update solution for Docker images package
i zypper-log CLI for accessing the zypper logfile package
i zypper-migration-plugin Zypper subcommand for online migration package
zypper-migration-plugin Zypper subcommand for online migration srcpackage

zypper li
licenses list-patches list-updates

. Cannot do a test without the feature

#7 Updated by dmaiocchi about 4 years ago

  • Status changed from Rejected to Feedback

#8 Updated by dmaiocchi about 4 years ago

  • Status changed from Feedback to In Progress
  • % Done changed from 0 to 10

#9 Updated by dmaiocchi about 4 years ago

  • % Done changed from 10 to 90

#10 Updated by dmaiocchi about 4 years ago

Bug founded:

https://build.suse.de/package/show/home:nadvornik:zypper-lifecycle/zypper-lifecycle-plugin

  • fixed return value (bsc#979322)
  • do not ignore errors on parsing of lifecycle data (bsc#979431)

#11 Updated by dmaiocchi about 4 years ago

bug 981106

#12 Updated by dmaiocchi about 4 years ago

  • % Done changed from 90 to 100

Fate manual testing for feature done.

For the automation that in a fate-feature is not MANDATORY, "out of my task" i explained the condition how to import my testsuite. Otherwise i cannot import to your job-framework-scheduler.

For me close.

#13 Updated by dmaiocchi about 4 years ago

  • Status changed from In Progress to Resolved

#14 Updated by RBrownSUSE about 4 years ago

  • Status changed from Resolved to In Progress
  • Assignee deleted (dmaiocchi)
  • % Done changed from 100 to 70

This is the openQA test issue tracker.

The task was to implement it in openQA as part of openQA's Milestone 3

Reset % accordingly, reopened, and cleared assignment.

#15 Updated by okurz about 4 years ago

  • Target version changed from 168 to Milestone 3

#16 Updated by maritawerner almost 4 years ago

  • Subject changed from Feature 320597: Introduce 'zypper lifecycle' to provide information about life cycle of individual products and packages to Feature 320597 and 320699: Introduce 'zypper lifecycle' to provide information about life cycle of individual products and packages and Do not communicate End of Support dates, that change later to a previous point in time
  • Description updated (diff)

#17 Updated by okurz almost 4 years ago

  • Description updated (diff)
  • Status changed from In Progress to Feedback
  • Assignee set to okurz

I am deleting outdated duplicated information from FATE entry to keep the issue clean and not lead people into thinking that they don't need to look at the FATE entry.

Current state as of 2016-07-26:

I added back-links from this progress issue to both fate entries and asked for test case descriptions.

#18 Updated by okurz almost 4 years ago

  • Status changed from Feedback to In Progress

nadvornik added test case to fate.

PR ready: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1613

it's a start.

#19 Updated by okurz almost 4 years ago

#13040 is seen as followup.

Verified locally on http://lord.arch/tests/2449 on x86_64 in one SLES scenario.

Feature test: PASSED

#20 Updated by okurz almost 4 years ago

some tests failed because I was not considering timezone differences, of course. Fixed by https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1660

commit d8cda34
Author: Oliver Kurz <okurz@suse.de>
Date:   Mon Aug 8 14:04:09 2016 +0200

    zypper_lifecycle: Do not rely on date as getting date is non-atomic

    The  being evaluated on the worker and not the SUT is suspect to timezone
    differences, e.g. see
    https://openqa.suse.de/tests/506437#step/zypper_lifecycle/29, where this
    fails. But even when we would get the time from the SUT and then compare it
    against the zypper lifecycle output we could hit the day boundary. It is
    better to not try to parse the date at all.

#23 Updated by okurz almost 4 years ago

  • Status changed from In Progress to Feedback

#24 Updated by okurz over 3 years ago

  • Status changed from Feedback to Resolved

Had been very stable over the recent weeks.

Also available in: Atom PDF