Project

General

Profile

Actions

Fix #51580

closed

qa/standalone: Add missing teardowns at the end of a subset of osd and scrub tests

Added by Sridhar Seshasayee almost 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
pacific
Reviewed:
Affected Versions:
ceph-qa-suite:
rados
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

A subset of osd and scrub standalone tests are not properly cleaning up after
completion.

  1. osd/osd-force-create.sh - all tests
  2. osd/osd-reuse-id.sh - all tests
  3. osd/pg-split-merge.sh - all tests
  4. scrub/osd-scrub-repair.sh
    • TEST_periodic_scrub_replicated()
    • TEST_scrub_warning()
    • TEST_request_scrub_priority()

Running the tests individually wouldn't cause issues. But when
running all the tests in a file, it could introduce unexpected test
failures down the line. For e.g., multiple tests may create pools with same
name and if they are not cleaned up properly, it could result in
unexpected results in a subsequent test.


Related issues 1 (0 open1 closed)

Copied to RADOS - Backport #51603: pacific: qa/standalone: Add missing teardowns at the end of a subset of osd and scrub testsResolvedSridhar SeshasayeeActions
Actions #1

Updated by Sridhar Seshasayee almost 3 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 42234
Actions #2

Updated by Sridhar Seshasayee almost 3 years ago

  • Project changed from Ceph to RADOS
  • Category deleted (qa)
Actions #3

Updated by Sridhar Seshasayee almost 3 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to pacific
Actions #4

Updated by Backport Bot almost 3 years ago

  • Copied to Backport #51603: pacific: qa/standalone: Add missing teardowns at the end of a subset of osd and scrub tests added
Actions #5

Updated by Loïc Dachary almost 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF