Comment 2 for bug 1263895

So, I looked at logs. Problem is that we don't handle case when you have redefined deployment data which were getting not from default handler of this cluster.
I can suggest half-working workaround, just make
curl http://0.0.0.0:8000/api/v1/clusters/1/orchestrator/deployment/defaults?nodes=1,2,3
And maybe you will get ip address which will be assigned in right order for nodes.

But right usage is
1. get default deployment settings
2. change default deployment setting
3. upload them

When you use such functional as deployment data redefinition it's very easy to shot in leg.