It seems there are issues with lbaasv2 as discussed in this[1] thread.
Loadbalancer becoming ACTIVE(provisioning_status), does not mean any of other objects(ex. Listener) are not in ERROR status. As mentioned in the ML thread there is not api to check individual object provisioning_status atm(to be supported later). There is an api for loadbalancer status tree[2], but I don't see any client support for it yet.
Though I'm not sure why the test would fail at all, may be something to do with haproxy.
It seems there are issues with lbaasv2 as discussed in this[1] thread.
Loadbalancer becoming ACTIVE( provisioning_ status) , does not mean any of other objects(ex. Listener) are not in ERROR status. As mentioned in the ML thread there is not api to check individual object provisioning_status atm(to be supported later). There is an api for loadbalancer status tree[2], but I don't see any client support for it yet.
Though I'm not sure why the test would fail at all, may be something to do with haproxy.
[1] http:// lists.openstack .org/pipermail/ openstack- dev/2016- September/ 104826. html developer. openstack. org/api- ref/networking/ v2/#show- load-balancer- status- tree
[2] http://