From 8afc1332ea7f0697e27b0830b0f6758c3d6d7eb2 Mon Sep 17 00:00:00 2001 From: Sage Weil Date: Wed, 13 Mar 2019 12:46:50 -0500 Subject: [PATCH] qa/standalone/erasure-code/test-erasure-code: adjust test to avoid m=0 _DD is k=2 m=0, which we don't allow. Switch it to cDD. I confess I don't fully understand why this was _DD to begin with, but I'm pretty sure mapping is there to control the order of results so that it can be mapped to the CRUSH rule output sanely, and the coding portion is not relevant to the test. Signed-off-by: Sage Weil (cherry picked from commit 52d5797c3d3d74dd88664cfe85e5d551e7b334a6) --- qa/standalone/erasure-code/test-erasure-code.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qa/standalone/erasure-code/test-erasure-code.sh b/qa/standalone/erasure-code/test-erasure-code.sh index ecdc25421ca7e..fb522bbd5b7c1 100755 --- a/qa/standalone/erasure-code/test-erasure-code.sh +++ b/qa/standalone/erasure-code/test-erasure-code.sh @@ -308,7 +308,7 @@ function TEST_chunk_mapping() { ceph osd erasure-code-profile set remap-profile \ plugin=lrc \ - layers='[ [ "_DD", "" ] ]' \ + layers='[ [ "cDD", "" ] ]' \ mapping='_DD' \ crush-steps='[ [ "choose", "osd", 0 ] ]' || return 1 ceph osd erasure-code-profile get remap-profile -- 2.39.5