So again, I see no "mutation" or "corruption" of astute.yaml in this deployment. If you check nailgun api log, you'll see that this test did not configure interfaces on nodes (see http://paste.openstack.org/show/493936/). So Fuel assigned networks to interfaces as it wanted - it's totally ok, but it may not match with your real/virtual network setup (which is exactly the case here).
In order to avoid such errors, I suggest to add interfaces configuration to this tests case. Forwarding this to fuel-qa for review.
As for failure on 9.0: /product- ci.infra. mirantis. net/job/ 9.0.system_ test.ubuntu. command_ line/67/ artifact/ logs/fail_ error_cli_ selected_ nodes_deploy- fuel-snapshot- 2016-04- 03_22-30- 01.tar. xz
> Snapshot: https:/
I've analyzed this snapshot, here's the result: http:// paste.openstack .org/show/ 493936/
So again, I see no "mutation" or "corruption" of astute.yaml in this deployment. If you check nailgun api log, you'll see that this test did not configure interfaces on nodes (see http:// paste.openstack .org/show/ 493936/). So Fuel assigned networks to interfaces as it wanted - it's totally ok, but it may not match with your real/virtual network setup (which is exactly the case here).
In order to avoid such errors, I suggest to add interfaces configuration to this tests case. Forwarding this to fuel-qa for review.