Project

General

Profile

Actions
Copy link

Bug #9858

closed

osd crush rule create-erasure idempotency failure

Added by Loïc Dachary over 9 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
High
Assignee:
Loïc Dachary
Category:
Monitor
Target version:
-
% Done:

0%

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

Description

The ./ceph osd crush rule create-erasure ruleset3 command run by test/mon/osd-crush.sh sometime fails to notice the rule already exists.

TEST_crush_rule_create_erasure: 85: ./ceph osd crush rule create-erasure ruleset3
*** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
created ruleset ruleset3 at 1
TEST_crush_rule_create_erasure: 86: ./ceph osd crush rule create-erasure ruleset3
TEST_crush_rule_create_erasure: 87: grep 'ruleset3 already exists'
TEST_crush_rule_create_erasure: 87: return 1

Files

Download all files
good.log.gz (25.7 KB) good.log.gz successful run Loïc Dachary, 10/21/2014 05:03 PM
bad.log.gz (24.2 KB) bad.log.gz failed run Loïc Dachary, 10/21/2014 05:03 PM
bad2.log.gz (20.8 KB) bad2.log.gz Loïc Dachary, 10/21/2014 05:23 PM

Related issues 1 (0 open — 1 closed)

Related to Ceph - Bug #9826: ceph osd crush rule ls should use the pending crush, if anyRejectedLoïc Dachary10/19/2014

Actions
Actions
Copy link
 #1

Updated by Loïc Dachary over 9 years ago

reproduced with while make -j8 check ; do : ; done after ~30 minutes (i.e. ~15 runs).

Actions
Copy link
 #2

Updated by Loïc Dachary over 9 years ago

  • Status changed from New to Rejected

This was a side effect of process being killed at random. It was possible to reproduce it consistently until https://github.com/dachary/ceph/commit/6e6ddfbdc0a178a6318a86fd9984265bbe40ca3d was added and it made it go away.

Actions
Copy link

Also available in: Atom PDF