Comment 3 for bug 1441855

Thanks guys for investigation but it was our scripts fault, we changed endpoint in prepare job to be able to manipulate keystone objects from outside which isn't correct way of doing that. Since keystone/haproxy/iptables got fixed in new releases this way finaly lead as to dead end :)