AutoscalingLoadBalancerv2Test.test_autoscaling_loadbalancer_neutron fails intermittently

[Thomas Herve]

As seen here: http://logs.openstack.org/90/360990/2/gate/gate-heat-dsvm-functional-orig-mysql-lbaasv2/1377007/console.html

testtools.matchers._impl.MismatchError: 2 != 1

It fails on the scale up operation, the creation is successful though.

[Thomas Herve (therve)]

I think there is a fundamental flaw with the test.

On the given test result, we get the signal at 10:36:01. The update is complete at 10:36:09.
At that point in the client side, we start looking for URLs in the LB. We loop 20 times with 2 seconds between each, so 40 seconds, then stop and look for 2 different URLs. I think it's a little bit too fast to expect the instance to be booted and added to the health monitor. We should loop a tiny bit more.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/362054

[Thomas Herve (therve)]

I was wrong.

[Rabi Mishra (rabi)]

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
[2] http://developer.openstack.org/api-ref/networking/v2/#show-load-balancer-status-tree

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/362054
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=96faa97db38ab8de90425080383b2adaa24fb087
Submitter: Jenkins
Branch: master

commit 96faa97db38ab8de90425080383b2adaa24fb087
Author: Thomas Herve <email address hidden>
Date: Mon Aug 29 14:08:15 2016 +0200

    Speed up lbaasv2 test

    If we reached the number of expected responses, return in the loop that
    check for lbaas.

    Change-Id: Ic18e5589a70b10aefabe22cb51891478500e8128
    Related-Bug: #1617992