scenario002-multinode-oooq-container fails on mongodb

[Michele Baldessari]

Once we stop ignoring errors via https://review.openstack.org/511509 we will fail on:

http://logs.openstack.org/40/510040/2/check/legacy-tripleo-ci-centos-7-scenario002-multinode-oooq-container/51c53ce/logs/undercloud/home/zuul/failed_deployment_list.log.txt.gz

"Error: /Stage[main]/Tripleo::Profile::Base::Database::Mongodb/Mongodb_replset[tripleo]: Could not evaluate: Can't connect to any member of replicaset tripleo.",

[Michele Baldessari (michele)]

So we have disabled mongo via https://review.openstack.org/#/c/466265/ and via https://review.openstack.org/500646. So what is left here to be figured out is why scenario002 is enabling it

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/513270

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/513270
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=900416d9809bf4446c0c037128edb033ab9b3bcc
Submitter: Zuul
Branch: master

commit 900416d9809bf4446c0c037128edb033ab9b3bcc
Author: Michele Baldessari <email address hidden>
Date: Thu Oct 19 08:12:07 2017 +0200

    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.

    Change-Id: I0d2df25ed797ffb8425ba81736526d3688e5de5c
    Closes-Bug: #1724679

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/514727

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/514727
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=6a7c88faba6462ff1d8ea50cff546c810fa1f4a3
Submitter: Zuul
Branch: stable/pike

commit 6a7c88faba6462ff1d8ea50cff546c810fa1f4a3
Author: Michele Baldessari <email address hidden>
Date: Thu Oct 19 08:12:07 2017 +0200

    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)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 7.0.4 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 8.0.0.0b2 development milestone.