action #55253: [sle][functional][u] test fails in zypper_lifecycle_toolchain - checking toolchain module cpp8 went wrong - openQA Tests - openSUSE Project Management Tool

Custom queries

All open Feature tests
openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QAM
QE tools team - backlog (ready issues)
QE tools team - backlog (w/o infra)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
SLE15 Migration Open Tickets
SLE15 SP1 Migration Open Tickets
SLE15SP3 Migration open ticket
SLE15SP3 Security open ticket
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #55253

closed

[sle][functional][u] test fails in zypper_lifecycle_toolchain - checking toolchain module cpp8 went wrong

Added by zluo over 4 years ago. Updated over 4 years ago.

Status:

Resolved

Priority:

High

Assignee:

dheidler

Category:

Bugs in existing tests

Target version:

SUSE QA - Milestone 30

Start date:

2019-08-08

Due date:

% Done:

Estimated time:

42.00 h

Difficulty:

Description

compare with https://openqa.suse.de/tests/3174572#step/zypper_lifecycle_toolchain/15, we I that cpp8 detection went wrong for expiration date, it shows already the correct date.

Observation¶

openQA test in scenario sle-12-SP5-Server-DVD-aarch64-gnome+proxy_SCC+allmodules@aarch64 fails in
zypper_lifecycle_toolchain

Tasks¶

Implement a workaround for this bug: https://bugzilla.suse.com/show_bug.cgi?id=1143453 Show a soft-fail if the date shown by zypper lifecycle is not the expected one.

Reproducible¶

Fails since (at least) Build 0256 (current job)

Expected result¶

Last good: 0251 (or more recent)

Further details¶

Always latest result in this scenario: latest
Related bugs:

History
Notes
Property changes

Actions

Copy link

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: gnome+proxy_SCC+allmodules
https://openqa.suse.de/tests/3276012

Actions

Copy link

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: gnome+proxy_SCC+allmodules
https://openqa.suse.de/tests/3340448

Actions

Copy link

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: gnome+proxy_SCC+allmodules
https://openqa.suse.de/tests/3400342

Actions

Copy link

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: gnome+proxy_SCC+allmodules
https://openqa.suse.de/tests/3400342

Actions

Copy link

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: gnome+proxy_SCC+allmodules
https://openqa.suse.de/tests/3452610

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

The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
The openQA job group is moved to "Released"
The label in the openQA scenario is removed

Actions

Copy link

Updated by SLindoMansilla over 4 years ago

Priority changed from Normal to High

Actions

Copy link

Updated by maritawerner over 4 years ago

What is the status here? We are almost at GMC? Can we get that fixed?

Actions

Copy link

Updated by msmeissn over 4 years ago

https://bugzilla.suse.com/show_bug.cgi?id=1153883 might be a product bug though.... the openqa shows 2024-10-30 for the base product too, but sles12 sp5 seems to be set to EOL 2024-10-31

Actions

Copy link

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: gnome+proxy_SCC+allmodules
https://openqa.suse.de/tests/3553461

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

The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
The openQA job group is moved to "Released"
The label in the openQA scenario is removed

Actions

Copy link

#10

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: gnome+proxy_SCC+allmodules
https://openqa.suse.de/tests/3575766

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

The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
The openQA job group is moved to "Released"
The label in the openQA scenario is removed

Actions

Copy link

#11