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 <sage@redhat.com>
(cherry picked from commit 52d5797c3d3d74dd88664cfe85e5d551e7b334a6)

diff --git a/qa/standalone/erasure-code/test-erasure-code.sh b/qa/standalone/erasure-code/test-erasure-code.sh
index ecdc25421ca7e4c969e2aee837aa9d39b01c276a..fb522bbd5b7c13f8393a3f205ee617323fe45bd2 100755 (executable)
--- 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