yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #88107
[Bug 1958561] [NEW] [ovn-octavia-provider] Listner/Pool Stuck in PENDING_CREATE Using Fully Populated LB API
Public bug reported:
When using creating a fully populated LB with ovn as provider, the
listener/pools will stuck in PENDING_CREATE STATE.
I Haven't tested what the result for other Octavia provider as I only
have OVN in my environment.
Steps to reproduce:
Create a fully populated LB with API (only includes listener in this
example):
curl -i -X POST -H "Content-Type: application/json" -H "X-Auth-Token:
$OS_TOKEN" -d
'{"loadbalancer":{"admin_state_up":true,"listeners":[{"name":"http_listener","protocol":"TCP","protocol_port":80}],"vip_subnet_id":"SUBNET_ID","provider":"ovn","name":"best_load_balancer","tags":["test_tag"]}}'
https://XXXXXXXXXXXXX:9876/v2.0/lbaas/loadbalancers
openstack loadbalancer listener show http_listener
+-----------------------------+--------------------------------------+
| Field | Value |
+-----------------------------+--------------------------------------+
| admin_state_up | True |
| connection_limit | -1 |
| created_at | 2022-01-20T16:37:58 |
| default_pool_id | None |
| default_tls_container_ref | None |
| description | |
| id | de2bbd23-ca08-445f-b58b-e36c8ea709ad |
| insert_headers | None |
| l7policies | |
| loadbalancers | 467846cf-7b1a-49f8-ae2f-398da103e6e4 |
| name | http_listener |
| operating_status | OFFLINE |
| project_id | 76235f59db4f4b289513b08c3739d2d6 |
| protocol | TCP |
| protocol_port | 80 |
| provisioning_status | PENDING_CREATE |
| sni_container_refs | [] |
| timeout_client_data | 50000 |
| timeout_member_connect | 5000 |
| timeout_member_data | 50000 |
| timeout_tcp_inspect | 0 |
| updated_at | None |
| client_ca_tls_container_ref | None |
| client_authentication | NONE |
| client_crl_container_ref | None |
| allowed_cidrs | None |
| tls_ciphers | None |
| tls_versions | None |
| alpn_protocols | None |
| tags | |
+-----------------------------+--------------------------------------+
The listener will remain in PENDING_CREATE state forever.
OpenStack Version: stabe/xena
Found this issue while using cloud-provider-openstack with K8S to create
LB, as it create LB with fully populated request, it will have listeners
and pools in PENDING_CREATE status.
** Affects: neutron
Importance: Undecided
Status: New
** Description changed:
When using creating a fully populated LB with ovn as provider, the
listener/pools will stuck in PENDING_CREATE STATE.
I Haven't tested what the result for other Octavia provider as I only
have OVN in my environment.
Steps to reproduce:
- ```
- curl -i -X POST -H "Content-Type: application/json" -H "X-Auth-Token: $OS_TOKEN" -d '{"loadbalancer":{"admin_state_up":true,"listeners":[{"name":"http_listener","protocol":"TCP","protocol_port":80}],"vip_subnet_id":"SUBNET_ID","provider":"ovn","name":"best_load_balancer","tags":["test_tag"]}}' https://XXXXXXXXXXXXX:9876/v2.0/lbaas/loadbalancers
- ```
- ```
+ Create a fully populated LB with API (only includes listener in this example):
+
+ curl -i -X POST -H "Content-Type: application/json" -H "X-Auth-Token:
+ $OS_TOKEN" -d
+ '{"loadbalancer":{"admin_state_up":true,"listeners":[{"name":"http_listener","protocol":"TCP","protocol_port":80}],"vip_subnet_id":"SUBNET_ID","provider":"ovn","name":"best_load_balancer","tags":["test_tag"]}}'
+ https://XXXXXXXXXXXXX:9876/v2.0/lbaas/loadbalancers
+
+
openstack loadbalancer listener show http_listener
+-----------------------------+--------------------------------------+
| Field | Value |
+-----------------------------+--------------------------------------+
| admin_state_up | True |
| connection_limit | -1 |
| created_at | 2022-01-20T16:37:58 |
| default_pool_id | None |
| default_tls_container_ref | None |
| description | |
| id | de2bbd23-ca08-445f-b58b-e36c8ea709ad |
| insert_headers | None |
| l7policies | |
| loadbalancers | 467846cf-7b1a-49f8-ae2f-398da103e6e4 |
| name | http_listener |
| operating_status | OFFLINE |
| project_id | 76235f59db4f4b289513b08c3739d2d6 |
| protocol | TCP |
| protocol_port | 80 |
| provisioning_status | PENDING_CREATE |
| sni_container_refs | [] |
| timeout_client_data | 50000 |
| timeout_member_connect | 5000 |
| timeout_member_data | 50000 |
| timeout_tcp_inspect | 0 |
| updated_at | None |
| client_ca_tls_container_ref | None |
| client_authentication | NONE |
| client_crl_container_ref | None |
| allowed_cidrs | None |
| tls_ciphers | None |
| tls_versions | None |
| alpn_protocols | None |
| tags | |
+-----------------------------+--------------------------------------+
- ```
The listener will remain in PENDING_CREATE state forever.
** Description changed:
When using creating a fully populated LB with ovn as provider, the
listener/pools will stuck in PENDING_CREATE STATE.
I Haven't tested what the result for other Octavia provider as I only
have OVN in my environment.
Steps to reproduce:
-
- Create a fully populated LB with API (only includes listener in this example):
+ Create a fully populated LB with API (only includes listener in this
+ example):
curl -i -X POST -H "Content-Type: application/json" -H "X-Auth-Token:
$OS_TOKEN" -d
'{"loadbalancer":{"admin_state_up":true,"listeners":[{"name":"http_listener","protocol":"TCP","protocol_port":80}],"vip_subnet_id":"SUBNET_ID","provider":"ovn","name":"best_load_balancer","tags":["test_tag"]}}'
https://XXXXXXXXXXXXX:9876/v2.0/lbaas/loadbalancers
-
openstack loadbalancer listener show http_listener
+-----------------------------+--------------------------------------+
| Field | Value |
+-----------------------------+--------------------------------------+
| admin_state_up | True |
| connection_limit | -1 |
| created_at | 2022-01-20T16:37:58 |
| default_pool_id | None |
| default_tls_container_ref | None |
| description | |
| id | de2bbd23-ca08-445f-b58b-e36c8ea709ad |
| insert_headers | None |
| l7policies | |
| loadbalancers | 467846cf-7b1a-49f8-ae2f-398da103e6e4 |
| name | http_listener |
| operating_status | OFFLINE |
| project_id | 76235f59db4f4b289513b08c3739d2d6 |
| protocol | TCP |
| protocol_port | 80 |
| provisioning_status | PENDING_CREATE |
| sni_container_refs | [] |
| timeout_client_data | 50000 |
| timeout_member_connect | 5000 |
| timeout_member_data | 50000 |
| timeout_tcp_inspect | 0 |
| updated_at | None |
| client_ca_tls_container_ref | None |
| client_authentication | NONE |
| client_crl_container_ref | None |
| allowed_cidrs | None |
| tls_ciphers | None |
| tls_versions | None |
| alpn_protocols | None |
| tags | |
+-----------------------------+--------------------------------------+
The listener will remain in PENDING_CREATE state forever.
+
+ Found this issue while using cloud-provider-openstack with K8S to create
+ LB, as it create LB with fully populated request, it will have listeners
+ and pools in PENDING_CREATE status.
** Description changed:
When using creating a fully populated LB with ovn as provider, the
listener/pools will stuck in PENDING_CREATE STATE.
I Haven't tested what the result for other Octavia provider as I only
have OVN in my environment.
Steps to reproduce:
Create a fully populated LB with API (only includes listener in this
example):
curl -i -X POST -H "Content-Type: application/json" -H "X-Auth-Token:
$OS_TOKEN" -d
'{"loadbalancer":{"admin_state_up":true,"listeners":[{"name":"http_listener","protocol":"TCP","protocol_port":80}],"vip_subnet_id":"SUBNET_ID","provider":"ovn","name":"best_load_balancer","tags":["test_tag"]}}'
https://XXXXXXXXXXXXX:9876/v2.0/lbaas/loadbalancers
openstack loadbalancer listener show http_listener
+-----------------------------+--------------------------------------+
| Field | Value |
+-----------------------------+--------------------------------------+
| admin_state_up | True |
| connection_limit | -1 |
| created_at | 2022-01-20T16:37:58 |
| default_pool_id | None |
| default_tls_container_ref | None |
| description | |
| id | de2bbd23-ca08-445f-b58b-e36c8ea709ad |
| insert_headers | None |
| l7policies | |
| loadbalancers | 467846cf-7b1a-49f8-ae2f-398da103e6e4 |
| name | http_listener |
| operating_status | OFFLINE |
| project_id | 76235f59db4f4b289513b08c3739d2d6 |
| protocol | TCP |
| protocol_port | 80 |
| provisioning_status | PENDING_CREATE |
| sni_container_refs | [] |
| timeout_client_data | 50000 |
| timeout_member_connect | 5000 |
| timeout_member_data | 50000 |
| timeout_tcp_inspect | 0 |
| updated_at | None |
| client_ca_tls_container_ref | None |
| client_authentication | NONE |
| client_crl_container_ref | None |
| allowed_cidrs | None |
| tls_ciphers | None |
| tls_versions | None |
| alpn_protocols | None |
| tags | |
+-----------------------------+--------------------------------------+
The listener will remain in PENDING_CREATE state forever.
+ OpenStack Version: stabe/xena
+
Found this issue while using cloud-provider-openstack with K8S to create
LB, as it create LB with fully populated request, it will have listeners
and pools in PENDING_CREATE status.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1958561
Title:
[ovn-octavia-provider] Listner/Pool Stuck in PENDING_CREATE Using
Fully Populated LB API
Status in neutron:
New
Bug description:
When using creating a fully populated LB with ovn as provider, the
listener/pools will stuck in PENDING_CREATE STATE.
I Haven't tested what the result for other Octavia provider as I only
have OVN in my environment.
Steps to reproduce:
Create a fully populated LB with API (only includes listener in this
example):
curl -i -X POST -H "Content-Type: application/json" -H "X-Auth-Token:
$OS_TOKEN" -d
'{"loadbalancer":{"admin_state_up":true,"listeners":[{"name":"http_listener","protocol":"TCP","protocol_port":80}],"vip_subnet_id":"SUBNET_ID","provider":"ovn","name":"best_load_balancer","tags":["test_tag"]}}'
https://XXXXXXXXXXXXX:9876/v2.0/lbaas/loadbalancers
openstack loadbalancer listener show http_listener
+-----------------------------+--------------------------------------+
| Field | Value |
+-----------------------------+--------------------------------------+
| admin_state_up | True |
| connection_limit | -1 |
| created_at | 2022-01-20T16:37:58 |
| default_pool_id | None |
| default_tls_container_ref | None |
| description | |
| id | de2bbd23-ca08-445f-b58b-e36c8ea709ad |
| insert_headers | None |
| l7policies | |
| loadbalancers | 467846cf-7b1a-49f8-ae2f-398da103e6e4 |
| name | http_listener |
| operating_status | OFFLINE |
| project_id | 76235f59db4f4b289513b08c3739d2d6 |
| protocol | TCP |
| protocol_port | 80 |
| provisioning_status | PENDING_CREATE |
| sni_container_refs | [] |
| timeout_client_data | 50000 |
| timeout_member_connect | 5000 |
| timeout_member_data | 50000 |
| timeout_tcp_inspect | 0 |
| updated_at | None |
| client_ca_tls_container_ref | None |
| client_authentication | NONE |
| client_crl_container_ref | None |
| allowed_cidrs | None |
| tls_ciphers | None |
| tls_versions | None |
| alpn_protocols | None |
| tags | |
+-----------------------------+--------------------------------------+
The listener will remain in PENDING_CREATE state forever.
OpenStack Version: stabe/xena
Found this issue while using cloud-provider-openstack with K8S to
create LB, as it create LB with fully populated request, it will have
listeners and pools in PENDING_CREATE status.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1958561/+subscriptions
Follow ups
