I've confirmed the same bug for the master branch of OSA today. It's exposed if the haproxy host is not in the nova_all group which in my case was caused by me removing all nova services from the deployment.
I've confirmed the same bug for the master branch of OSA today. It's exposed if the haproxy host is not in the nova_all group which in my case was caused by me removing all nova services from the deployment.