Disable MongoDB in scenario002
authorMichele Baldessari <michele@acksyn.org>
Thu, 19 Oct 2017 06:12:07 +0000 (08:12 +0200)
committerEmilien Macchi <emilien@redhat.com>
Fri, 27 Oct 2017 20:42:38 +0000 (20:42 +0000)
commit6a7c88faba6462ff1d8ea50cff546c810fa1f4a3
tree4f3735521a284cdd649623dbbd16e6cf2bd20341
parent9dfec11795703b43991e06ef880b52cd0b3a5eb4
Disable MongoDB in scenario002

We have disabled mongo by default in containers via:

Id2e6550fb7c319fc52469644ea022cf35757e0ce Disable mongodb by default
Ie09ce2a52128eef157e4d768c1c4776fc49f2324 Containerized mongodb, disable by default, fix upgrade

Let's not use it in scenario002 either.

NB: Not entirely clean cherry-pick due to scenario002-multinode-containers.yaml
    having many more services in master than in pike.

Change-Id: I0d2df25ed797ffb8425ba81736526d3688e5de5c
Closes-Bug: #1724679
(cherry picked from commit 900416d9809bf4446c0c037128edb033ab9b3bcc)
ci/environments/scenario002-multinode-containers.yaml
ci/environments/scenario002-multinode.yaml