From e68ed6f7cc5e2b0039015dfa9d63c14ccd908c44 Mon Sep 17 00:00:00 2001
From: Francesco Pantano <fpantano@redhat.com>
Date: Mon, 29 Mar 2021 21:20:32 +0200
Subject: [PATCH] Remove CrushRules coverage from scenario001

We see many issues in CI due to the missing hdd device class.
This is something that can be related to the fact that only
1 OSD in this job is built on top of a loop device.
For this reason, and in order to keep the CI healthy, it's
safe removing the device classes coverage.
In addition, since there is only 1 osd, add and configure
tiering in this context makes no sense.

Change-Id: I4638b9badd17a7a75642895623a63753534fd341
---
 ci/environments/scenario001-standalone.yaml | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/ci/environments/scenario001-standalone.yaml b/ci/environments/scenario001-standalone.yaml
index a839ebaf03..96e751910f 100644
--- a/ci/environments/scenario001-standalone.yaml
+++ b/ci/environments/scenario001-standalone.yaml
@@ -55,7 +55,6 @@ parameter_defaults:
   CeilometerQdrPublishMetrics: true
   ManageEventPipeline: true
   ManagePipeline: true
-
   Debug: true
   CephSpecFqdn: true
   CephOsdSpec:
@@ -65,16 +64,10 @@ parameter_defaults:
   CephPoolDefaultPgNum: 8
   CephPoolDefaultSize: 1
   CinderRbdExtraPools: altrbd,pool2,pool3
-  CephCrushRules:
-    - name: HDD
-      root: default
-      type: host
-      class: hdd
-      default: true
   CephPools:
     - name: altrbd
       pg_num: 8
-      rule_name: HDD
+      rule_name: replicated_rule
   #NOTE: These ID's and keys should be regenerated for
   # a production deployment. What is here is suitable for
   # developer and CI testing only.