Project

General

Profile

Actions

action #111128

closed

[qe-core] test fails in redis - Unexpected serial output for redis on Xen backend

Added by szarate over 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2022-05-16
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

For some reason, for XEN, wait_serial is not working as we expect it to, one possible mitigation is to script all of the calls, use commands instead of using the redis console, or better, run queries against the database itself.

openQA test in scenario sle-15-SP4-Online-x86_64-extra_tests_textmode@svirt-xen-hvm fails in
redis

Test suite description

Maintainer: QE Core, asmorodskyi,dheidler. Mainly console extratest

Reproducible

Fails since (at least) Build 79.1

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Suggestions

Try running the test using only a HDD from aggregates + schedule the module and investigate

Acceptance Criteria

  1. AC1: Redis test is reworked to rely less on wait_serial

Related issues 2 (1 open1 closed)

Related to openQA Tests - action #112910: [qe-core] test fails in redisNew2022-06-23

Actions
Related to openQA Tests - action #115592: [qe-core] Enhance the redis test to know the status of the replicationResolvedpdostal2022-08-22

Actions
Actions #1

Updated by openqa_review over 2 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: extra_tests_textmode@svirt-xen-hvm
https://openqa.suse.de/tests/8752656#step/redis/1

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 28 days if nothing changes in this ticket.

Actions #2

Updated by szarate about 2 years ago

  • Tags set to bugbusters
  • Description updated (diff)
  • Target version changed from future to QE-Core: Ready
Actions #3

Updated by dvenkatachala about 2 years ago

  • Assignee set to dvenkatachala
Actions #4

Updated by dvenkatachala about 2 years ago

  • Status changed from New to In Progress
Actions #5

Updated by dvenkatachala about 2 years ago

Actions #6

Updated by openqa_review about 2 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: extra_tests_textmode@svirt-xen-hvm
https://openqa.suse.de/tests/8752656#step/redis/1

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 28 days if nothing changes in this ticket.

Actions #8

Updated by dvenkatachala about 2 years ago

  • Related to action #115592: [qe-core] Enhance the redis test to know the status of the replication added
Actions #9

Updated by dvenkatachala about 2 years ago

  • Status changed from In Progress to Resolved

redis test run in latest builds after the code merged:

SLE15-SP4:
aarch64 - https://openqa.suse.de/tests/9379804
ppc64le - https://openqa.suse.de/tests/9380287
s390x - https://openqa.suse.de/tests/9379736
x86_64 - https://openqa.suse.de/tests/9380865

Actions

Also available in: Atom PDF