Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: In Progress
** Tags: lbaasv2
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1582874
Title:
Neutron
://review.openstack.org/#/c/311221/
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: In Progress
** Project changed: octavia => neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, wh
Public bug reported:
It appears that a python 3 unit test is failing in:
neutron_lbaas.tests.unit.db.loadbalancer.test_db_loadbalancer.TestLoadBalancer
test_check_orphan_pool_associations
from: https://review.openstack.org/#/c/164828/
see:
with secrets reference
4. Create Load Balancer and pass in Barbican TLS container reference
5. Pass SSL traffic to load balancer
6. Verify SSL traffic to node
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: In Progress
** Tags: lbaasv2
Public bug reported:
* create update and delete admin tests
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: New
** Tags: lbaasv2
** Changed in: neutron
Assignee: (unassigned) => Franklin Naval (franknaval)
--
You recei
Public bug reported:
* create admin tests around update and deleting listeners
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: In Progress
** Tags: lbaasv2
** Changed in: neutron
Assignee: (unassigned) => Franklin Na
Public bug reported:
Create the following tests:
* A battery of CRUD tests around TLS listeners
* Dependent on Barbican to generate default_tls_container_ref
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: In Progress
** Tags: lbaasv2
Public bug reported:
create the following tests:
* update and delete tests for admin
* some create tests added
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: New
** Tags: lbaasv2
** Changed in: neutron
Assignee: (unassigned
Public bug reported:
* create tests for update and deleting admin health monitors
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: In Progress
** Tags: lbaasv2
** Changed in: neutron
Assignee: (unassigned) => Franklin Na
Public bug reported:
* create admin tests around update and delete listeners
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: In Progress
** Tags: lbaasv2
** Changed in: neutron
Assignee: (unassigned) => Franklin Naval (frankna
Public bug reported:
* create tests that check ports for listener and member
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => Franklin Naval (franknaval)
--
You recei
Public bug reported:
* create data driven tests for protocols using pools and listeners
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: In Progress
** Tags: lbaasv2
--
You received this bug notification because you are a member
Public bug reported:
Create the following tests:
* checks that a member is unreachable when:
* admin_state_up is False
* weight is 0
* member is removed from the pool
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: In Progress
Public bug reported:
* check shared pools functionality using listeners and pools
** Affects: neutron
Importance: Undecided
Assignee: Franklin Naval (franknaval)
Status: In Progress
** Tags: lbaasv2
** Changed in: neutron
Assignee: (unassigned) => Franklin Na
Public bug reported:
1. Create a load balancer
2. Create a listener
3. Create a pool from listener.
4. Add a member to the pool. Specify that the weight is 0.1
5. Check the response.
Result: Request is accepted with a 201. Checking the response body shows
weight as 0
Expected: API
Public bug reported:
1. Create Load Balancer
2. Create Listener
3. Create Pool
4. Add member to Pool with a subnet_id that does not exist (but has a valid
uuid format)
5. Check Load Balancer provisioning_status
Result: Load Balancer stays in provisioning_status PENDING_UPDATE for
more
Public bug reported:
1. Create a Load Balancer.
2. Create a Listener with TCP
3. Create a Pool with HTTP
4. Observe the following error: {"NeutronError": {"message": "Listener
protocol TCP and pool protocol HTTP are not compatible.", "type":
"ListenerPoolProtocolMismatch", "detail": ""}
Public bug reported:
(This is more of a feature request than a bug.)
Examine the available protocols for Listener and Pool.
Listener: TCP, HTTP, HTTPS, TERMINATED_HTTPS
Pool: TCP, HTTP, HTTPS
This combination may be redundant:
Listener -> Pool
HTTPS -> HTTP
TERMINATED_HTTPS -> HTTP
Public bug reported:
1. Create a LB.
2. Create a Pool. (Do NOT create a listener.)
3. Add a member to the Pool.
4. Check LB status.
Result: LB is stuck in provision_status: "PENDING_UPDATE" for more than
an hour.
Expected: Either throw an error to the user when adding a member to a
pool
Public bug reported:
As an admin user:
1. Create a Load balancer.
2. Create a pool for the load balancer.
3. Add a member to the pool.
4. Delete the pool.
5. Check Load balancer status.
Result: Load balancer status will be set to "PENDING_UPDATE" for more
than 30 mins.
Expected Result:
Public bug reported:
As an admin user, perform the following for a given tenant:
1. Create Load_Balancer_1
2. Create a Pool_1 for Load_Balancer_1.
3. Add 1 member_1 to Pool_1.
4. Create Load_Balancer_2.
5. Create a Pool_2 for Load_Balancer_2.
6. Add 1 member_2 to Pool_2.
7. Delete Pool_2.
Public bug reported:
1. Create load balancer as an admin.
2. Create pool as an admin.
3. As an admin, add member to pool but using an invalid tenant id. (e.g.,
"$232!$pw" )
Result: API returns 201
Expected: API should return BadRequest 400
Log:
2016-04-19 00:51:53,500 3286 INFO
Public bug reported:
Since health monitors and members are sub-resources of pools, they
should both be created/retrieved/updated/deleted the same way.
See:
https://wiki.openstack.org/wiki/Neutron/LBaaS/API_2.0#Create_a_Health_Monitor
vs.
Public bug reported:
1. Create LB
2. Create 2 Listener's simultaneously
Result: 500 thrown
Expected: 409 conflict with an informative error message
Log: http://paste.openstack.org/show/494129/
2016-04-14 20:50:00,177 10041 INFO [tempest.lib.common.rest_client] Request
Public bug reported:
1. Create a lb.
2. Create a listener.
3. Update the listener with a large connection limit, e.g. 99
Result: 500 from the server is returned
Expected: Should return with 400 HTTPBadRequest similar to when specifying a
connection limit less than -1
(ex:
Public bug reported:
1. Create TLS Listener (i.e., create listener with valid
"default_tls_container_ref" pointed to barbican)
2. Remove TLS by updating Listener with default_tls_container_ref="" or None
Result: default_tls_container_ref still contains the original reference
Expected:
Public bug reported:
SUMMARY:
A gate job for Neutron-LBaaS failed today (20141016). It was identified that
the failure occurred due to the introduction of new operating statues; namely,
"DEGRADED".
Per the following document, we will see the following valid types for
operating_status:
Public bug reported:
Steps:
1. Pull down and run the following test code in Tempest:
https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/tests/tempest/v2/api/test_listeners_admin.py#L98
2. Examine logs for actual request/response.
Result:
The test
Public bug reported:
I'm seeing the following exception on creating a load balancer with a listener:
https://gist.github.com/fnaval/64e91dd864030b7bff71
This is running on neutron-lbaas against hash:
28b75a656be2f27807aa3d10a12b361534f84ad9
** Affects: neutron
Importance: Undecided
So this is actually working. There was some miscommunication that the
agent needed to be run automatically. However, in the newest version of
neutron_lbass, the agent will start up automatically. Having 2 agents
running was causing multiple failures.
** Changed in: neutron
Status: New =
** Changed in: neutron
Status: New = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1428774
Title:
Neutron-LBaaS: Stats Call API Spec mismatch with Actual Response
Public bug reported:
1. Create Load Balancer
2. Do a stats call
3. See response.
Result: stats response looks like this:
{stats: {bytes_in: 0, total_connections: 0, active_connections: 0,
bytes_out: 0}}
Expected: according to api spec,
32 matches
Mail list logo
