revert to setup_master in bvt_2 test group

[Aleksandra Fedorova]

To shorten the BVT2 run on Packaging CI we'd like to not redeploy Fuel node from scratch every time, but reuse snapshots of already deployed master node.

But in case of Packaging CI test is defined by repositories setup and custom packages are added via repo URL's.

If we reuse the same devops environment for packaging ci tests, URL's won't be updated in Fuel configs, because we revert to prepare_5_slaves snapshot. There is no step of updating repo urls there.

Thus we need to revert to the prepare_release step, where repo URLs can be updated.

[Dmitry Tyzhnenko (dtyzhnenko)]

bvt_2 aleardy use prepare_release in BVT2 [0] since 25 Fev 2015 [1]

[0] - https://github.com/openstack/fuel-qa/blob/b8871aef0845ef1c1fdcdae66ee5fca28f8a12c7/fuelweb_test/tests/test_ceph.py#L440
[1] - https://github.com/openstack/fuel-qa/commit/f75ee6796164b25497fe10010bbaa671d31d842d

[Vladimir Khlyunev (vkhlyunev)]

As I see - we can just set "REPLACE_DEFAULT_REPOS_ONLY_ONCE=false" in patching job - and repos will be updated in every run at creating of new cluster.
https://github.com/openstack/fuel-qa/blob/master/fuelweb_test/models/fuel_web_client.py#L428

[Andrey Sledzinskiy (asledzinskiy)]

Vladimir comment is absolutely valid.
You need to add just:
export REPLACE_DEFAULT_REPOS_ONLY_ONCE=false

and repos will be changed again during every cluster creation, I checked it locally