SM:R3.1.1 build 38: creation of lbaas fails
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0.2.x |
Invalid
|
Undecided
|
kamlesh parmar | |||
R3.1 |
Fix Committed
|
High
|
Nitish Krishna Kaveri | |||
R3.1.1.x |
Fix Committed
|
High
|
Nitish Krishna Kaveri | |||
R3.2 |
Fix Committed
|
High
|
Nitish Krishna Kaveri | |||
Trunk |
Fix Committed
|
High
|
Nitish Krishna Kaveri |
Bug Description
SM:R3.1.1 build 38: lbaas not able to connect to VIP ip
HA setup 3.1.1 build 38 Kilo with 2 computes
root@nodeg21:~# neutron lb-vip-list
+------
| id | name | address | protocol | admin_state_up | status |
+------
| 625fd269-
+------
root@nodeg21:~# neutron lb-vip-show myvip
+------
| Field | Value |
+------
| address | 10.1.1.7 |
| admin_state_up | True |
| connection_limit | -1 |
| description | |
| id | 625fd269-
| name | myvip |
| pool_id | 987a49b2-
| port_id | fb037c55-
| protocol | HTTP |
| protocol_port | 80 |
| session_persistence | |
| status | ACTIVE |
| subnet_id | 7a12be4c-
| tenant_id | 17d16de3b1ad4c6
+------
root@nodeg21:~# neutron lb-pool-show mypool
+------
| Field | Value |
+------
| admin_state_up | True |
| custom_attributes | [] |
| description | |
| health_monitors | a310157a-
| health_
| id | 987a49b2-
| lb_method | ROUND_ROBIN |
| members | 27e8f53c-
| | 2767a76b-
| | 19c8a2d9-
| name | mypool |
| protocol | HTTP |
| provider | opencontrail |
| status | ACTIVE |
| subnet_id | 7a12be4c-
| tenant_id | 17d16de3b1ad4c6
| vip_id | 625fd269-
+------
root@nodeg21:~# nova list
+----+-
| ID | Name | Status | Task State | Power State | Networks |
+----+-
+----+-
/var/log/
11/05/2016 05:53:21 MSG Starting haproxy for Loadbalancer-ID 7ffb405d-
11/05/2016 05:53:21 MSG exec of "haproxy" failed: No such file or directory
Seen with Multi interface setup also
summary: |
- SM:HA:R3.1.1 build 38: lbaas not able to connect to VIP ip + SM:R3.1.1 build 38: lbaas not able to connect to VIP ip |
description: | updated |
tags: | added: sanity |
Seems like connectivity losss to VIP from compute node.
Please provision the cluster with required config and let me know. Need to debug on setup.