Comment 3 for bug 1491725

@Andrey, thank you for confirmation, it looks like not "the same issue" but probably the root of the issues is the same, let's not mark these issues as duplicated because it is different steps to reproduce.

The priority of this issue is Critical because it affects deployment and it is Blocked for deployment of OpenStack clusters. Priority can be changed to High only if we will understand that it is very hard to fix in MOS 7.0 - this issue reproduced not in 100% of cases, so, it is Blocker, but blocker for not 100% of users.

And looks like the case with upgrade which was mentioned by Andrey will be reproduced in 100%, so, it means that we have some hidden issues in the product which will affect many users.

Important:
If user will face the issue it is not possible to avoid the issue, looks like it will require to redeploy master node to fix the issue.