Support full BVT for Astute in case of change /magent folder

[Vladimir Sharshov]

Detailed bug description:

Changes in /magent https://github.com/openstack/fuel-astute/tree/master/mcagents folder can be very dangerous. It can not be catch by standard jobs because it build as separate package and build in bootstrap and install separately from local master repository on installed nodes. Also it should be install on master node.

Steps to reproduce:

Make logical mistake in any mcagents folder and push review.
Expected results:

It should catch such updates and mark review with -1.

Actual result:

It will pass all tests without any errors.

Reproducibility:

Always

Workaround:

Core-review should require BVT or QA +1 test in case of magents updates.

Impact:

It can raise critical errors.

Additional information:

Check history of this bug: https://bugs.launchpad.net/fuel/+bug/1569325

[Vladimir Sharshov (vsharshov)]

Fast solution: run full BVT test on every Astute request. Special care for depends on parameters, because mostly times such change in magent connected with some change in Fuel-web and without it will fail

[Dmitry Kaigarodеsev (dkaiharodsev)]

we've already got a deployment tests for astute package:

https://ci.fuel-infra.org/job/master.fuel-astute.pkgs.ubuntu.review_astute_patched/
https://ci.fuel-infra.org/job/mitaka.fuel-astute.pkgs.ubuntu.review_astute_patched/

please clarify if existing tests are not cover this bug request

[Vladimir Sharshov (vsharshov)]

Hi, my option about currents tests: "It can not be catch by standard jobs because it build as separate package and build in bootstrap and install separately from local master repository on installed nodes. Also it should be install on master node."

So i ask to modify this job to support scenario with updates in case of magents.