Project

General

Profile

action #17268

[sled][migration] test fails in zypper_lifecycle expected: '/ImageMagick-\S+\s+2019-10-30' but got 2024-10-30

Added by qkzhu about 5 years ago. Updated 11 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2017-02-23
Due date:
% Done:

100%

Estimated time:
4.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP3-Desktop-DVD-x86_64-migration_offline_sled12_sdk@64bit fails in
zypper_lifecycle

expected: '/ImageMagick-\S+\s+2019-10-30' but got 2014-10-30

Reproducible

Fails since (at least) Build 0120

Expected result

Last good: 0119 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by qkzhu about 5 years ago

  • Subject changed from test fails in zypper_lifecycle to test fails in zypper_lifecycle expected: '/ImageMagick-\S+\s+2019-10-30' but got 2014-10-30

#2 Updated by okurz about 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_sled12sp2_sdk
https://openqa.suse.de/tests/834582

#3 Updated by okurz about 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_sled12sp2_sdk
https://openqa.suse.de/tests/864089

#4 Updated by maritawerner about 5 years ago

  • Subject changed from test fails in zypper_lifecycle expected: '/ImageMagick-\S+\s+2019-10-30' but got 2014-10-30 to [sled][migration] test fails in zypper_lifecycle expected: '/ImageMagick-\S+\s+2019-10-30' but got 2014-10-30

#5 Updated by qkzhu about 5 years ago

  • Subject changed from [sled][migration] test fails in zypper_lifecycle expected: '/ImageMagick-\S+\s+2019-10-30' but got 2014-10-30 to [sled][migration] test fails in zypper_lifecycle expected: '/ImageMagick-\S+\s+2019-10-30' but got 2024-10-30

Currently this case failed on all migration_offline_sled+sdk scenarios:

migration_offline_sled12_sdk: https://openqa.suse.de/tests/883350#step/zypper_lifecycle/64
migration_offline_sled12sp1_sdk: https://openqa.suse.de/tests/883352#step/zypper_lifecycle/64
migration_offline_sled12sp2_sdk: https://openqa.suse.de/tests/883343#step/zypper_lifecycle/64

Test died: ImageMagick lifecycle entry incorrect:'Package end of support:
ImageMagick 2024-10-30', expected: '/ImageMagick-\S+\s+2019-10-30'

Yifan and I found that both SDK and SLED's base repo contain the package ImageMagick. We don't know
if it is intended or a packaging issue.
The eol of ImageMagick on base repo is 2019-10-30 but the eol on SDK is 2024-10-30. But if there are
the same versions of a package in multiple products, zypper lifecycle will keep the one with longest
product life.(see line 136 of /usr/lib/zypper/commands/zypper-lifecycle)

The openQA script should be updated if ImageMagick is intended to package into SDK otherwise I will
file a bug for this.

#6 Updated by qkzhu about 5 years ago

ImageMagick is available in both SLED and SDK. After some discussions with Frederic we think that the lifecycle of a duplicated packages(eg: ImageMagick) in main product and extension should follow the main product's lifecycle. But ImageMagick in this case didn't apply the main product's lifecycle, so I filed a bug for this: https://bugzilla.suse.com/show_bug.cgi?id=1035353

But we still need some voices of the developer.

#7 Updated by qkzhu about 5 years ago

As we discussed in https://bugzilla.suse.com/show_bug.cgi?id=1035353#c4 to #c8 this is not a product bug.

And Jiri told me that: if a package is provided by two products(eg main product and SDK), then it is supported as long as it is supported by one of them.
This means it is expected to return the longer eol value for the duplicate packages like ImageMagick.

So this case should be updated.

#8 Updated by okurz about 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_sled12_sdk_fullupdate
https://openqa.suse.de/tests/917938

#9 Updated by yfjiang about 5 years ago

From the comment#7, "This means it is expected to return the longer eol value for the duplicate packages like ImageMagick.",
it's expected that the script gets some update. We do not have a fast patch without looking through details of the
test script code base.

I am in contact with the major contributor of the test script figuring our the follow-up, not get a conclusion yet.

If everyone agrees, we might want to mark it as soft_failure for the time being, since this is a matter of test script
logic refining instead of a product bug.

#10 Updated by okurz almost 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_sled12_sdk_fullupdate
https://openqa.suse.de/tests/954580

#11 Updated by okurz almost 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_sled12_sdk_fullupdate
https://openqa.suse.de/tests/979265

#12 Updated by okurz almost 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_sled12sp1_sdk_fullupdate
https://openqa.suse.de/tests/1007613

#13 Updated by okurz almost 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_sled12_sdk_fullupdate
https://openqa.suse.de/tests/1039607

#14 Updated by okurz over 4 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_sled12_sdk_fullupdate
http://openqa.suse.de/tests/1057910

#15 Updated by okurz over 4 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: om_scc_sled12sp2_sdk_full_update_by_yast
https://openqa.suse.de/tests/1062653

#16 Updated by leli 11 months ago

  • Assignee set to tinawang123

#17 Updated by tinawang123 11 months ago

  • Status changed from New to Rejected
  • % Done changed from 0 to 100
  • Estimated time set to 4.00 h

Also available in: Atom PDF