Project

General

Profile

Actions
Copy link

Bug #51903

closed

tests: destroying OSDs fails because osd not yet marked as down

Added by Guillaume Abrioux over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Guillaume Abrioux
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
pacific,octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
42524
Crash signature (v1):
Crash signature (v2):

Description

For some reason, it can happen that osds are not yet marked down when the test playbooks try to destroy osds.
This makes the ci fail for nothing.

Related issues 2 (0 open — 2 closed)

Copied to ceph-volume - Backport #51958: pacific: tests: destroying OSDs fails because osd not yet marked as downResolvedDimitri SavineauActions
Copied to ceph-volume - Backport #51959: octopus: tests: destroying OSDs fails because osd not yet marked as downResolvedDimitri SavineauActions
Actions
Copy link
 #1

Updated by Guillaume Abrioux over 2 years ago

  • Pull request ID set to 42524
Actions
Copy link
 #2

Updated by Dimitri Savineau over 2 years ago

  • Status changed from In Progress to Pending Backport
  • Backport set to pacific,octopus
Actions
Copy link
 #3

Updated by Backport Bot over 2 years ago

  • Copied to Backport #51958: pacific: tests: destroying OSDs fails because osd not yet marked as down added
Actions
Copy link
 #4

Updated by Backport Bot over 2 years ago

  • Copied to Backport #51959: octopus: tests: destroying OSDs fails because osd not yet marked as down added
Actions
Copy link
 #5

Updated by Dimitri Savineau over 2 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF