Comment 9 for bug 1663187

There is presumably something more weird going on than the endpoint simply not being reachable, let's try a different one. Because the placement API only exposes itself as a wsgi application, any problems with reaching it are either with how it has been listed in keystone or how the wsgi server (in this case apache with mod wsgi) has been configured, both of which are entirely in the domain (in this case) of the puppet files. So something is weird with how the network is setup, and working around that seems like it is just hiding a bug or at least a misunderstanding of how the network is configured. Is the goal that the n-cpu and nova-scheduler hosting boxes can reach the IPV6 network?

In any case, this patch which you may already know about may be helpful: https://review.openstack.org/#/c/426163/