LB working while members are offline
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| octavia (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I'm using Victoria installed via kolla-ansible
Defined LBs are working correctly, but if I check related members status they are reported as "OFFLINE":
openstack loadbalancer show b82fc090-
+------
| Field | Value |
+------
| admin_state_up | True |
| created_at | 2020-12-11T12:19:45 |
| description | |
| flavor | |
| id | b82fc090-
| listeners | f2c582ba-
| name | k8s-spaceballs-
| operating_status | OFFLINE |
| pools | 248a9be0-
| project_id | 63be5b4f4d78408
| provider | amphora |
| provisioning_status | ACTIVE |
| updated_at | 2020-12-11T12:21:16 |
| vip_address | 10.0.0.23 |
| vip_network_id | 1e59822e-
| vip_port_id | 9d19dccd-
| vip_qos_policy_id | None |
| vip_subnet_id | fd3cfdeb-
+------
openstack loadbalancer listener show f2c582ba-
+------
| Field | Value |
+------
| admin_state_up | True |
| connection_limit | -1 |
| created_at | 2020-12-11T12:20:58 |
| default_pool_id | 248a9be0-
| default_
| description | |
| id | f2c582ba-
| insert_headers | None |
| l7policies | |
| loadbalancers | b82fc090-
| name | k8s-spaceballs-
| operating_status | OFFLINE |
| project_id | 63be5b4f4d78408
| protocol | TCP |
| protocol_port | 6443 |
| provisioning_status | ACTIVE |
| sni_container_refs | [] |
| updated_at | 2020-12-11T12:21:16 |
+------
openstack loadbalancer pool show 248a9be0-
+------
| Field | Value |
+------
| admin_state_up | True |
| created_at | 2020-12-11T12:21:01 |
| description | |
| healthmonitor_id | 490ea28b-
| id | 248a9be0-
| lb_algorithm | ROUND_ROBIN |
| listeners | f2c582ba-
| loadbalancers | b82fc090-
| members | 4dc0d6db-
| | 990b8f3a-
| | e61e6259-
| name | k8s-spaceballs-
| operating_status | OFFLINE |
| project_id | 63be5b4f4d78408
| protocol | TCP |
| provisioning_status | ACTIVE |
| session_persistence | None |
| updated_at | 2020-12-11T12:21:16 |
+------
openstack loadbalancer member show 248a9be0-
+------
| Field | Value |
+------
| address | 10.0.0.109 |
| admin_state_up | True |
| created_at | 2020-12-11T12:21:13 |
| id | 4dc0d6db-
| name | |
| operating_status | OFFLINE |
| project_id | 63be5b4f4d78408
| protocol_port | 6443 |
| provisioning_status | ACTIVE |
| subnet_id | fd3cfdeb-
| updated_at | 2020-12-11T12:21:14 |
| weight | 1 |
| monitor_port | None |
| monitor_address | None |
+------
openstack loadbalancer member show 248a9be0-
+------
| Field | Value |
+------
| address | 10.0.0.12 |
| admin_state_up | True |
| created_at | 2020-12-11T12:21:15 |
| id | 990b8f3a-
| name | |
| operating_status | OFFLINE |
| project_id | 63be5b4f4d78408
| protocol_port | 6443 |
| provisioning_status | ACTIVE |
| subnet_id | fd3cfdeb-
| updated_at | 2020-12-11T12:21:16 |
| weight | 1 |
| monitor_port | None |
| monitor_address | None |
+------
openstack loadbalancer member show 248a9be0-
+------
| Field | Value |
+------
| address | 10.0.0.39 |
| admin_state_up | True |
| created_at | 2020-12-11T12:21:10 |
| id | e61e6259-
| name | |
| operating_status | OFFLINE |
| project_id | 63be5b4f4d78408
| protocol_port | 6443 |
| provisioning_status | ACTIVE |
| subnet_id | fd3cfdeb-
| updated_at | 2020-12-11T12:21:11 |
| weight | 1 |
| monitor_port | None |
| monitor_address | None |
+------
A simple curl responds correctly (obviously besides the 403 application error):
curl -k https:/
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {
},
"status": "Failure",
"message": "forbidden: User \"system:
"reason": "Forbidden",
"details": {
},
"code": 403
