mon: crush_ruleset_create_erasure set ruleset

Use get_rule_id() instead of rule_exists() to test the existence of a
ruleset and preserve the ruleset.

Signed-off-by: Loic Dachary <loic@dachary.org>

diff --git a/src/mon/OSDMonitor.cc b/src/mon/OSDMonitor.cc
index 7654000e621eb6f4f168bc0a3b717feaaa657537..7a7f731cab4b4cc01ab7e9be04d812e228ba66bd 100644 (file)
--- a/src/mon/OSDMonitor.cc
+++ b/src/mon/OSDMonitor.cc
@@ -2812,13 +2812,15 @@ int OSDMonitor::crush_ruleset_create_erasure(const string &name,
                                             int *ruleset,
                                             stringstream &ss)
 {
-    if (osdmap.crush->rule_exists(name))
+    *ruleset = osdmap.crush->get_rule_id(name);
+    if (*ruleset != -ENOENT)
       return -EEXIST;
 
     CrushWrapper newcrush;
     _get_pending_crush(newcrush);
 
-    if (newcrush.rule_exists(name)) {
+    *ruleset = newcrush.get_rule_id(name);
+    if (*ruleset != -ENOENT) {
       return -EALREADY;
     } else {
       ErasureCodeInterfaceRef erasure_code;
@@ -2832,6 +2834,7 @@ int OSDMonitor::crush_ruleset_create_erasure(const string &name,
       erasure_code.reset();
       if (rule < 0)
        return rule;
+      *ruleset = rule;
       pending_inc.crush.clear();
       newcrush.encode(pending_inc.crush);
       return 0;