Comment 25 for bug 1532823

Timur, yes, I did. Here's what is stored in network transformation in astute.yaml for the problem node-4:
http://paste.openstack.org/show/486682/
As you can networks are assigned correctly so deployment is correct.

From the other hand, if we hit such bug on environment and then try to add/remove nodes, this could possible break the deployment because in DB we have wrong network assignments. So I'll rise priority of this bug to critical.

Timur, access to the environment could be really helpful, I did not manage to reproduce this bug to troubleshoot it on a live env.