| 2016-06-22 23:55:16 |
KRISHNA MOULI. TANKALA |
description |
Unable to delete loadbalancer even in ERROR state.
Octavia Load balancer is allowing to delete only in ACTIVE state, it is NOT allowing to delete it even in ERROR state.
When a load balancer is created it will go into PENDING_CREATE. after that if it is successful in spawning Amphora then it may go into ACTIVE state.
But due to some reasons like wrong subnet for amphora, or because some other network issue amphora may become unreachable to octavia controller. In such cases load balancer goes to ERROR state.
When a load balancer is in ERROR state we can issue delete of it.
stack@MouliDev:~$ neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+------+-------------+---------------------+----------+
| 4d616fe9-bdb0-49bb-a6c8-eee3317b3f24 | lb1 | 10.0.0.3 | ERROR | octavia |
| 99226592-2381-4b0a-895d-a00f9624b570 | lb2 | 10.0.0.11 | ERROR | octavia |
+--------------------------------------+------+-------------+---------------------+----------+
stack@MouliDev:~$ neutron lbaas-loadbalancer-delete lb2
Deleted loadbalancer: lb2
Though it says deleted we can see error in log as below.
2016-06-21 20:06:31.016 24901 INFO octavia.api.v1.controllers.load_balancer [req-e9254006-ac19-4eba-b54f-a878267eb13e - - - - -] Load Balancer 99226592-2381-4b0a-895d-a00f9624b570 is immutable.
127.0.0.1 - - [21/Jun/2016 20:06:31] "DELETE /v1/loadbalancers/99226592-2381-4b0a-895d-a00f9624b570 HTTP/1.1" 409 147
stack@MouliDev:~$ neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+------+-------------+---------------------+----------+
| 4d616fe9-bdb0-49bb-a6c8-eee3317b3f24 | lb1 | 10.0.0.3 | ERROR | octavia |
| 99226592-2381-4b0a-895d-a00f9624b570 | lb2 | 10.0.0.11 | PENDING_DELETE | octavia |
+--------------------------------------+------+-------------+---------------------+----------+
then load balancer will never be deleted as it is immutable in ERROR state.
Expected results:
User should be able to delete a load balancer when it is ERROR state.
By mistake user would have given wrong subnet which caused this issue, but user should be able to recover from his mistake. |
Unable to delete loadbalancer even in ERROR state.
Octavia Load balancer is allowing to delete only in ACTIVE state, it is NOT allowing to delete it even in ERROR state.
When a load balancer is created it will go into PENDING_CREATE. after that if it is successful in spawning Amphora then it may go into ACTIVE state.
But due to some reasons like wrong subnet for amphora, or because some other network issue amphora may become unreachable to octavia controller. In such cases load balancer goes to ERROR state.
When a load balancer is in ERROR state we can issue delete of it.
stack@MouliDev:~$ neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+------+-------------+---------------------+----------+
| 4d616fe9-bdb0-49bb-a6c8-eee3317b3f24 | lb1 | 10.0.0.3 | ERROR | octavia |
| 99226592-2381-4b0a-895d-a00f9624b570 | lb2 | 10.0.0.11 | ERROR | octavia |
+--------------------------------------+------+-------------+---------------------+----------+
stack@MouliDev:~$ neutron lbaas-loadbalancer-delete lb2
Deleted loadbalancer: lb2
Though it says deleted we can see error in log as below.
2016-06-21 20:06:31.016 24901 INFO octavia.api.v1.controllers.load_balancer [req-e9254006-ac19-4eba-b54f-a878267eb13e - - - - -] Load Balancer 99226592-2381-4b0a-895d-a00f9624b570 is immutable.
127.0.0.1 - - [21/Jun/2016 20:06:31] "DELETE /v1/loadbalancers/99226592-2381-4b0a-895d-a00f9624b570 HTTP/1.1" 409 147
stack@MouliDev:~$ neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+------+-------------+---------------------+----------+
| 4d616fe9-bdb0-49bb-a6c8-eee3317b3f24 | lb1 | 10.0.0.3 | ERROR | octavia |
| 99226592-2381-4b0a-895d-a00f9624b570 | lb2 | 10.0.0.11 | PENDING_DELETE | octavia |
+--------------------------------------+------+-------------+---------------------+----------+
then load balancer will never be deleted as it is immutable in ERROR state.
after some time load balancer goes back to ERROR state again.
stack@MouliDev:~$ neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+------+-------------+---------------------+----------+
| 4d616fe9-bdb0-49bb-a6c8-eee3317b3f24 | lb1 | 10.0.0.3 | ERROR | octavia |
| 99226592-2381-4b0a-895d-a00f9624b570 | lb2 | 10.0.0.11 | ERROR | octavia |
+--------------------------------------+------+-------------+---------------------+----------+
Expected results:
User should be able to delete a load balancer when it is ERROR state.
By mistake user would have given wrong subnet which caused this issue, but user should be able to recover from his mistake. |
|
| 2016-06-23 00:06:37 |
KRISHNA MOULI. TANKALA |
description |
Unable to delete loadbalancer even in ERROR state.
Octavia Load balancer is allowing to delete only in ACTIVE state, it is NOT allowing to delete it even in ERROR state.
When a load balancer is created it will go into PENDING_CREATE. after that if it is successful in spawning Amphora then it may go into ACTIVE state.
But due to some reasons like wrong subnet for amphora, or because some other network issue amphora may become unreachable to octavia controller. In such cases load balancer goes to ERROR state.
When a load balancer is in ERROR state we can issue delete of it.
stack@MouliDev:~$ neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+------+-------------+---------------------+----------+
| 4d616fe9-bdb0-49bb-a6c8-eee3317b3f24 | lb1 | 10.0.0.3 | ERROR | octavia |
| 99226592-2381-4b0a-895d-a00f9624b570 | lb2 | 10.0.0.11 | ERROR | octavia |
+--------------------------------------+------+-------------+---------------------+----------+
stack@MouliDev:~$ neutron lbaas-loadbalancer-delete lb2
Deleted loadbalancer: lb2
Though it says deleted we can see error in log as below.
2016-06-21 20:06:31.016 24901 INFO octavia.api.v1.controllers.load_balancer [req-e9254006-ac19-4eba-b54f-a878267eb13e - - - - -] Load Balancer 99226592-2381-4b0a-895d-a00f9624b570 is immutable.
127.0.0.1 - - [21/Jun/2016 20:06:31] "DELETE /v1/loadbalancers/99226592-2381-4b0a-895d-a00f9624b570 HTTP/1.1" 409 147
stack@MouliDev:~$ neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+------+-------------+---------------------+----------+
| 4d616fe9-bdb0-49bb-a6c8-eee3317b3f24 | lb1 | 10.0.0.3 | ERROR | octavia |
| 99226592-2381-4b0a-895d-a00f9624b570 | lb2 | 10.0.0.11 | PENDING_DELETE | octavia |
+--------------------------------------+------+-------------+---------------------+----------+
then load balancer will never be deleted as it is immutable in ERROR state.
after some time load balancer goes back to ERROR state again.
stack@MouliDev:~$ neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+------+-------------+---------------------+----------+
| 4d616fe9-bdb0-49bb-a6c8-eee3317b3f24 | lb1 | 10.0.0.3 | ERROR | octavia |
| 99226592-2381-4b0a-895d-a00f9624b570 | lb2 | 10.0.0.11 | ERROR | octavia |
+--------------------------------------+------+-------------+---------------------+----------+
Expected results:
User should be able to delete a load balancer when it is ERROR state.
By mistake user would have given wrong subnet which caused this issue, but user should be able to recover from his mistake. |
Unable to delete loadbalancer even in ERROR state.
Octavia Load balancer is allowing to delete only in ACTIVE state, it is NOT allowing to delete it even in ERROR state.
When a load balancer is created it will go into PENDING_CREATE. after that if it is successful in spawning Amphora then it may go into ACTIVE state.
But due to some reasons like wrong subnet for amphora, or because some other network issue amphora may become unreachable to octavia controller. In such cases load balancer goes to ERROR state.
When a load balancer is in ERROR state we can issue delete of it.
stack@MouliDev:~$ neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+------+-------------+---------------------+----------+
| 4d616fe9-bdb0-49bb-a6c8-eee3317b3f24 | lb1 | 10.0.0.3 | ERROR | octavia |
| 99226592-2381-4b0a-895d-a00f9624b570 | lb2 | 10.0.0.11 | ERROR | octavia |
+--------------------------------------+------+-------------+---------------------+----------+
stack@MouliDev:~$ neutron lbaas-loadbalancer-delete lb2
Deleted loadbalancer: lb2
Though it says deleted we can see error in log as below.
2016-06-21 20:06:31.016 24901 INFO octavia.api.v1.controllers.load_balancer [req-e9254006-ac19-4eba-b54f-a878267eb13e - - - - -] Load Balancer 99226592-2381-4b0a-895d-a00f9624b570 is immutable.
127.0.0.1 - - [21/Jun/2016 20:06:31] "DELETE /v1/loadbalancers/99226592-2381-4b0a-895d-a00f9624b570 HTTP/1.1" 409 147
stack@MouliDev:~$ neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+------+-------------+---------------------+----------+
| 4d616fe9-bdb0-49bb-a6c8-eee3317b3f24 | lb1 | 10.0.0.3 | ERROR | octavia |
| 99226592-2381-4b0a-895d-a00f9624b570 | lb2 | 10.0.0.11 | PENDING_DELETE | octavia |
+--------------------------------------+------+-------------+---------------------+----------+
then load balancer will never be deleted as it is immutable in ERROR state.
after some time load balancer goes back to ERROR state again.
stack@MouliDev:~$ neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+------+-------------+---------------------+----------+
| 4d616fe9-bdb0-49bb-a6c8-eee3317b3f24 | lb1 | 10.0.0.3 | ERROR | octavia |
| 99226592-2381-4b0a-895d-a00f9624b570 | lb2 | 10.0.0.11 | ERROR | octavia |
+--------------------------------------+------+-------------+---------------------+----------+
Before proceeding to delete a load balancer, Octavia checks the provisioning status as below. Which allows to delete only if it is in ACTIVE state, But we should delete load balancer even if it is in ERROR state as well.
def test_and_set_lb_and_listeners_prov_status(self, session, lb_id,
lb_prov_status,
listener_prov_status,
listener_ids=None):
"""Tests and sets a load balancer and listener provisioning status.
Puts a lock on the load balancer table to check the status of a
load balancer. If the status is ACTIVE then the status of the load
balancer and listener is updated and the method returns True. If the
status is not ACTIVE, then nothing is done and False is returned.
:param session: A Sql Alchemy database session.
:param lb_id: id of Load Balancer
:param lb_prov_status: Status to set Load Balancer and Listener if
check passes.
:param listener_prov_status: Status to set Listeners if check passes
:param listener_ids: List of ids of a listeners (can be empty)
:returns: bool
octavia/common/constants.py
64
PENDING_UPDATE, DELETED, ERROR)
65
MUTABLE_STATUSES = (ACTIVE,)
66
Expected results:
User should be able to delete a load balancer when it is ERROR state.
By mistake user would have given wrong subnet which caused this issue, but user should be able to recover from his mistake. |
|
