Public bug reported:

When LBaaSv2 times out waiting to delete a load balancer, it will report:
Exception: Wait for load balancer ran for 600 seconds and did not observe 
cf48a82a-ed9f-4c81-b76b-9b897c095f88 reach ACTIVE provisioning status and 
ONLINE operating status.

This log entry is incorrect.  The code is actually doing the right thing
in waiting for the load balancer to disappear, but the log message
incorrectly states that it was looking for "ACTIVE" and "ONLINE".

Full error logged:
Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File 
"neutron_lbaas/tests/tempest/v2/api/test_load_balancers_non_admin.py", line 
433, in test_delete_load_balancer
        self._delete_load_balancer(new_load_balancer_id)
      File "neutron_lbaas/tests/tempest/v2/api/base.py", line 138, in 
_delete_load_balancer
        load_balancer_id, delete=True)
      File "neutron_lbaas/tests/tempest/v2/api/base.py", line 191, in 
_wait_for_load_balancer_status
        operating_status=operating_status))
    Exception: Wait for load balancer ran for 600 seconds and did not observe 
cf48a82a-ed9f-4c81-b76b-9b897c095f88 reach ACTIVE provisioning status and 
ONLINE operating status.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: lbaas

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1498173

Title:
  LBaaSv2 reports timeout waiting for ACTIVE on delete operation

Status in neutron:
  New

Bug description:
  When LBaaSv2 times out waiting to delete a load balancer, it will report:
  Exception: Wait for load balancer ran for 600 seconds and did not observe 
cf48a82a-ed9f-4c81-b76b-9b897c095f88 reach ACTIVE provisioning status and 
ONLINE operating status.

  This log entry is incorrect.  The code is actually doing the right
  thing in waiting for the load balancer to disappear, but the log
  message incorrectly states that it was looking for "ACTIVE" and
  "ONLINE".

  Full error logged:
  Captured traceback:
  ~~~~~~~~~~~~~~~~~~~
      Traceback (most recent call last):
        File 
"neutron_lbaas/tests/tempest/v2/api/test_load_balancers_non_admin.py", line 
433, in test_delete_load_balancer
          self._delete_load_balancer(new_load_balancer_id)
        File "neutron_lbaas/tests/tempest/v2/api/base.py", line 138, in 
_delete_load_balancer
          load_balancer_id, delete=True)
        File "neutron_lbaas/tests/tempest/v2/api/base.py", line 191, in 
_wait_for_load_balancer_status
          operating_status=operating_status))
      Exception: Wait for load balancer ran for 600 seconds and did not observe 
cf48a82a-ed9f-4c81-b76b-9b897c095f88 reach ACTIVE provisioning status and 
ONLINE operating status.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1498173/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to