yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #14288
[Bug 1317868] [NEW] LBAAS :Member with protocol port as HTTPS is not coming in active state for Lbaas site
Public bug reported:
Steps to Reproduce:
Setup onto ICEHouse GA:
Build :2014.1-0ubuntu1~cloud0
1. Create a lbaas site with one client and two web server.
2. Create pool with protocol as https
+--------------------------------------+-------+-------------+----------+----------------+--------+
| id | name | lb_method | protocol | admin_state_up | status |
+--------------------------------------+-------+-------------+----------+----------------+--------+
| aebd47e9-d125-49f6-aef2-2a97954c051a | pool1 | ROUND_ROBIN | HTTPS | True | ACTIVE |
+--------------------------------------+-------+-------------+----------+----------------+--------+
3. Create a health monitor for type https
+--------------------------------------+-------+----------------+
| id | type | admin_state_up |
+--------------------------------------+-------+----------------+
| affb69f6-e6b0-4f34-ab42-a89acecc60b3 | HTTPS | True |
+--------------------------------------+-------+----------------+
4. Create vip with protocol port as 443 and protocol as HTTPS
+--------------------------------------+------+-----------+----------+----------------+--------+
| id | name | address | protocol | admin_state_up | status |
+--------------------------------------+------+-----------+----------+----------------+--------+
| 405609a8-0e50-4d2c-a7b5-ab206290303d | | 10.10.1.6 | HTTPS | True | ACTIVE |
+--------------------------------------+------+-----------+----------+----------------+--------+
5. list the lbaas member status:
+--------------------------------------+-----------+---------------+----------------+----------+
| id | address | protocol_port | admin_state_up | status |
+--------------------------------------+-----------+---------------+----------------+----------+
| dd7a7f63-9218-4d21-b8f8-967018a3ae9f | 10.10.1.4 | 443 | True | INACTIVE |
| f844e226-4c3f-4351-9750-7cb14f614c3c | 10.10.1.5 | 443 | True | INACTIVE |
+--------------------------------------+-----------+---------------+----------------+----------+
Actual Results:
list the lbaas member status:
+--------------------------------------+-----------+---------------+----------------+----------+
| id | address | protocol_port | admin_state_up | status |
+--------------------------------------+-----------+---------------+----------------+----------+
| dd7a7f63-9218-4d21-b8f8-967018a3ae9f | 10.10.1.4 | 443 | True | INACTIVE |
| f844e226-4c3f-4351-9750-7cb14f614c3c | 10.10.1.5 | 443 | True | INACTIVE |
+--------------------------------------+-----------+---------------+----------------+----------+
Expected Results: Members should come in active state after the successfull creation of lbaas
** Affects: neutron
Importance: Undecided
Status: New
** Description changed:
- Steps to Reproduce:
- Setup onto Havana GA stable build
+ Steps to Reproduce:
+ Setup onto ICEHouse GA1:
+ Build :2014.1-0ubuntu1~cloud0
1. Create a lbaas site with one client and two web server.
2. Create pool with protocol as https
+--------------------------------------+-------+-------------+----------+----------------+--------+
| id | name | lb_method | protocol | admin_state_up | status |
+--------------------------------------+-------+-------------+----------+----------------+--------+
| aebd47e9-d125-49f6-aef2-2a97954c051a | pool1 | ROUND_ROBIN | HTTPS | True | ACTIVE |
+--------------------------------------+-------+-------------+----------+----------------+--------+
-
+
3. Create a health monitor for type https
+--------------------------------------+-------+----------------+
| id | type | admin_state_up |
+--------------------------------------+-------+----------------+
| affb69f6-e6b0-4f34-ab42-a89acecc60b3 | HTTPS | True |
+--------------------------------------+-------+----------------+
-
+
4. Create vip with protocol port as 443 and protocol as HTTPS
+--------------------------------------+------+-----------+----------+----------------+--------+
| id | name | address | protocol | admin_state_up | status |
+--------------------------------------+------+-----------+----------+----------------+--------+
| 405609a8-0e50-4d2c-a7b5-ab206290303d | | 10.10.1.6 | HTTPS | True | ACTIVE |
+--------------------------------------+------+-----------+----------+----------------+--------+
5. list the lbaas member status:
+--------------------------------------+-----------+---------------+----------------+----------+
| id | address | protocol_port | admin_state_up | status |
+--------------------------------------+-----------+---------------+----------------+----------+
| dd7a7f63-9218-4d21-b8f8-967018a3ae9f | 10.10.1.4 | 443 | True | INACTIVE |
| f844e226-4c3f-4351-9750-7cb14f614c3c | 10.10.1.5 | 443 | True | INACTIVE |
+--------------------------------------+-----------+---------------+----------------+----------+
- Actual Results:
+ Actual Results:
list the lbaas member status:
+--------------------------------------+-----------+---------------+----------------+----------+
| id | address | protocol_port | admin_state_up | status |
+--------------------------------------+-----------+---------------+----------------+----------+
| dd7a7f63-9218-4d21-b8f8-967018a3ae9f | 10.10.1.4 | 443 | True | INACTIVE |
| f844e226-4c3f-4351-9750-7cb14f614c3c | 10.10.1.5 | 443 | True | INACTIVE |
+--------------------------------------+-----------+---------------+----------------+----------+
Expected Results: Members should come in active state after the successfull creation of lbaas
** Description changed:
Steps to Reproduce:
- Setup onto ICEHouse GA1:
+ Setup onto ICEHouse GA:
Build :2014.1-0ubuntu1~cloud0
1. Create a lbaas site with one client and two web server.
2. Create pool with protocol as https
+--------------------------------------+-------+-------------+----------+----------------+--------+
| id | name | lb_method | protocol | admin_state_up | status |
+--------------------------------------+-------+-------------+----------+----------------+--------+
| aebd47e9-d125-49f6-aef2-2a97954c051a | pool1 | ROUND_ROBIN | HTTPS | True | ACTIVE |
+--------------------------------------+-------+-------------+----------+----------------+--------+
3. Create a health monitor for type https
+--------------------------------------+-------+----------------+
| id | type | admin_state_up |
+--------------------------------------+-------+----------------+
| affb69f6-e6b0-4f34-ab42-a89acecc60b3 | HTTPS | True |
+--------------------------------------+-------+----------------+
4. Create vip with protocol port as 443 and protocol as HTTPS
+--------------------------------------+------+-----------+----------+----------------+--------+
| id | name | address | protocol | admin_state_up | status |
+--------------------------------------+------+-----------+----------+----------------+--------+
| 405609a8-0e50-4d2c-a7b5-ab206290303d | | 10.10.1.6 | HTTPS | True | ACTIVE |
+--------------------------------------+------+-----------+----------+----------------+--------+
5. list the lbaas member status:
+--------------------------------------+-----------+---------------+----------------+----------+
| id | address | protocol_port | admin_state_up | status |
+--------------------------------------+-----------+---------------+----------------+----------+
| dd7a7f63-9218-4d21-b8f8-967018a3ae9f | 10.10.1.4 | 443 | True | INACTIVE |
| f844e226-4c3f-4351-9750-7cb14f614c3c | 10.10.1.5 | 443 | True | INACTIVE |
+--------------------------------------+-----------+---------------+----------------+----------+
Actual Results:
list the lbaas member status:
+--------------------------------------+-----------+---------------+----------------+----------+
| id | address | protocol_port | admin_state_up | status |
+--------------------------------------+-----------+---------------+----------------+----------+
| dd7a7f63-9218-4d21-b8f8-967018a3ae9f | 10.10.1.4 | 443 | True | INACTIVE |
| f844e226-4c3f-4351-9750-7cb14f614c3c | 10.10.1.5 | 443 | True | INACTIVE |
+--------------------------------------+-----------+---------------+----------------+----------+
Expected Results: Members should come in active state after the successfull creation of 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/1317868
Title:
LBAAS :Member with protocol port as HTTPS is not coming in active
state for Lbaas site
Status in OpenStack Neutron (virtual network service):
New
Bug description:
Steps to Reproduce:
Setup onto ICEHouse GA:
Build :2014.1-0ubuntu1~cloud0
1. Create a lbaas site with one client and two web server.
2. Create pool with protocol as https
+--------------------------------------+-------+-------------+----------+----------------+--------+
| id | name | lb_method | protocol | admin_state_up | status |
+--------------------------------------+-------+-------------+----------+----------------+--------+
| aebd47e9-d125-49f6-aef2-2a97954c051a | pool1 | ROUND_ROBIN | HTTPS | True | ACTIVE |
+--------------------------------------+-------+-------------+----------+----------------+--------+
3. Create a health monitor for type https
+--------------------------------------+-------+----------------+
| id | type | admin_state_up |
+--------------------------------------+-------+----------------+
| affb69f6-e6b0-4f34-ab42-a89acecc60b3 | HTTPS | True |
+--------------------------------------+-------+----------------+
4. Create vip with protocol port as 443 and protocol as HTTPS
+--------------------------------------+------+-----------+----------+----------------+--------+
| id | name | address | protocol | admin_state_up | status |
+--------------------------------------+------+-----------+----------+----------------+--------+
| 405609a8-0e50-4d2c-a7b5-ab206290303d | | 10.10.1.6 | HTTPS | True | ACTIVE |
+--------------------------------------+------+-----------+----------+----------------+--------+
5. list the lbaas member status:
+--------------------------------------+-----------+---------------+----------------+----------+
| id | address | protocol_port | admin_state_up | status |
+--------------------------------------+-----------+---------------+----------------+----------+
| dd7a7f63-9218-4d21-b8f8-967018a3ae9f | 10.10.1.4 | 443 | True | INACTIVE |
| f844e226-4c3f-4351-9750-7cb14f614c3c | 10.10.1.5 | 443 | True | INACTIVE |
+--------------------------------------+-----------+---------------+----------------+----------+
Actual Results:
list the lbaas member status:
+--------------------------------------+-----------+---------------+----------------+----------+
| id | address | protocol_port | admin_state_up | status |
+--------------------------------------+-----------+---------------+----------------+----------+
| dd7a7f63-9218-4d21-b8f8-967018a3ae9f | 10.10.1.4 | 443 | True | INACTIVE |
| f844e226-4c3f-4351-9750-7cb14f614c3c | 10.10.1.5 | 443 | True | INACTIVE |
+--------------------------------------+-----------+---------------+----------------+----------+
Expected Results: Members should come in active state after the successfull creation of lbaas
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1317868/+subscriptions
Follow ups
References
