Project

General

Profile

action #95593

[qe-core] Fix zypper_lifecycle

Added by dzedro over 1 year ago. Updated 5 months ago.

Status:
Blocked
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-07-16
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP4-Server-DVD-Updates-x86_64-qam-allpatterns+addons@64bit fails in
zypper_lifecycle

https://jira.suse.com/browse/MSC-70 S:M:19740:245070

RC chat

 Morning Zsolt KALMAR S:M:19740:245070 is breaking lifecycle https://openqa.suse.de/tests/6451659 I guess before it was also not correct https://openqa.suse.de/tests/6441790#step/zypper_lifecycle/44
10:05
Hi! Actually this is an update for EOL, and I've only corrected the EOL dates.
Wait, I see now the error
This is a bit new field to me, let me discuss this with Gustavo Pichorim Boiko first, maybe he has some idea, how to fix this
13:10
trying to understand the error
13:28
I don't know what date should be there on LTSS, but e.g. SP3 does have n/a* there same as SP4 before https://openqa.suse.de/tests/6441790#step/zypper_lifecycle/44
13:29
12-SP3 is without EOL date too if I remember correctly (we are slowly starting to correct that, but it takes time)
13:42
Should I reject https://smelt.suse.de/request/245070/ ? There are no changes visible in smelt anymore, but the packages in repo which is used are still same
14:17
Jozef Pupava The update is clearly fixing the package, so I am not sure we should reject the update. I am not sure what openQA is doing there though
let's wait for someone to test the
qam-sle
part, then we can check if they see the same as openQA
14:22
Gustavo Pichorim Boiko ok when this is how it should looks like when it's correct then the test need fix https://openqa.suse.de/tests/6461978#step/zypper_lifecycle/45 I guess the test does not work properly with LTSS and until now it passed by accident
Another thing is, lets say this is correct then every other version si broken
14:25
Jozef Pupava interesting, this output, where did it come from? I mean, what packages were being used when this actually worked?
14:26
This is how it did look before when it passed https://openqa.suse.de/tests/6441790#step/zypper_lifecycle/42
I think there is no difference in packages being used just in the output of
zypper lifecycle --days 0
14:30
Jozef Pupava ah ok, so that text is how it should look like, right? I was wondering if it was using a different a different repo for having that output
14:33
Based on the test yes , that how it should look like.
Both passing and failing test make somehow sense, but the test does expects regex /No products.*before/
14:45
I will update the regex to accept
/No packages with end of support different from product/
https://openqa.suse.de/tests/6441790#step/zypper_lifecycle/42
Don't know how to express it properly, but as far as I understand it SLE Linux enterprise server 12 SP4 is EOS, but LTSS is the exntension of support which is not mentioned there, I guess it should be ?
And I will open bug for the lifecycle to clarify how should the output look like on LTSS ?
14:47
that's all a bit weird, I think I will set up a local VM of 12-SP4 and try to debug it 

At the end I realized the output is correct and other packages will be fixed too.
I created PR to update the regex.

Test suite description

All modules defined in SCC_ADDONS
#20201124: added chrony-pool-openSUSE due to 15SP1 QU5 failure https://openqa.suse.de/tests/5060854

Reproducible

Fails since (at least) Build 20210714-2

Expected result

Last good: 20210714-1 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by dzedro over 1 year ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#2 Updated by dzedro over 1 year ago

  • Description updated (diff)

#3 Updated by openqa_review over 1 year ago

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

This bug is still referenced in a failing openQA test: qam-minimal+base
https://openqa.suse.de/tests/6632602

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#5 Updated by dzedro over 1 year ago

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13019

https://chat.suse.de/channel/qem-openqa-review/thread/KLrXWR5Sy7zprLFcx?jump=ioMXF2g5gy83Cs6Qq
Morning Zsolt KALMAR Gustavo Pichorim Boiko do you know if the EOS dates of python2 and legacy module are valid ? It's failing on all 15+ versions https://openqa.suse.de/tests/6636355#step/zypper_lifecycle/48
8:18
Hello! Do we have an incident number which is producing this?
9:06
I don't think any update is causing this
10:44
I don't know if the issue is not part of https://jira.suse.com/browse/MSC-70
Gustavo will probably know

jira.suse.com
Log in - SUSE Jira

10:46
ok, let's wait until he's online
12:19
the EOL of these modules is set to July 31st.... I think there are MSC tickets already to extend the lifdetimes
the current EOL is not valid, it will be longer
13:04
Thank you Marcus, I guess it will be not fixed so soon, will prepare change to ignore this failure until fixed.
13:05
i think this should be urgent on the maintenance side ... it could irritate customers
but it will take some days i expect
13:45
Indeed, we have an MSC ticket already with number of products, where we have to set/correct the end date

#6 Updated by dzedro over 1 year ago

  • Status changed from Resolved to Blocked

#7 Updated by openqa_review over 1 year ago

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

This bug is still referenced in a failing openQA test: qam-minimal+base
https://openqa.suse.de/tests/6866301

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#8 Updated by dzedro over 1 year ago

  • Status changed from Blocked to In Progress

#9 Updated by dzedro over 1 year ago

  • Status changed from In Progress to Blocked

#10 Updated by openqa_review over 1 year ago

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

This bug is still referenced in a failing openQA test: offline_sles15sp1_ltss_pscc_basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm_all_full
https://openqa.suse.de/tests/7038034

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#11 Updated by openqa_review over 1 year ago

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

This bug is still referenced in a failing openQA test: qam-minimal+base
https://openqa.suse.de/tests/7249044

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#12 Updated by openqa_review over 1 year ago

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

This bug is still referenced in a failing openQA test: qam-minimal+base
https://openqa.suse.de/tests/7388174

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#13 Updated by openqa_review over 1 year ago

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

This bug is still referenced in a failing openQA test: qam-minimal+base
https://openqa.suse.de/tests/7534925

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#14 Updated by openqa_review about 1 year ago

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

This bug is still referenced in a failing openQA test: qam-minimal+base
https://openqa.suse.de/tests/7641433

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#15 Updated by openqa_review about 1 year ago

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

This bug is still referenced in a failing openQA test: offline_sles15sp1_ltss_media_basesys-srv-desk-dev-contm-lgm-py2-wsm_all_full
https://openqa.suse.de/tests/7728899

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#16 Updated by openqa_review about 1 year ago

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

This bug is still referenced in a failing openQA test: qam-minimal+base
https://openqa.suse.de/tests/7814149

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#17 Updated by openqa_review about 1 year ago

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

This bug is still referenced in a failing openQA test: qam-minimal+base
https://openqa.suse.de/tests/7885338

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#19 Updated by openqa_review about 1 year ago

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

This bug is still referenced in a failing openQA test: qam-minimal+base
https://openqa.suse.de/tests/7987725

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#20 Updated by openqa_review about 1 year ago

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

This bug is still referenced in a failing openQA test: qam-minimal+base
https://openqa.suse.de/tests/8024220

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#21 Updated by openqa_review 12 months ago

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

This bug is still referenced in a failing openQA test: qam-gnome
https://openqa.suse.de/tests/8025242

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#22 Updated by openqa_review 11 months ago

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

This bug is still referenced in a failing openQA test: offline_sles15sp1_ltss_media_basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm-pcm_all_full
https://openqa.suse.de/tests/8280868

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.

#23 Updated by openqa_review 9 months ago

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

This bug is still referenced in a failing openQA test: mau-webserver
https://openqa.suse.de/tests/8735767

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 112 days if nothing changes in this ticket.

#24 Updated by openqa_review 5 months ago

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

This bug is still referenced in a failing openQA test: jeos-main
https://openqa.suse.de/tests/9267229

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 224 days if nothing changes in this ticket.

Also available in: Atom PDF