← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1552086] [NEW] LBaaS v2 updating pool clears session_persistence

 

Public bug reported:

It appears that whenever a lbaasv2 is updated, if the update does not
contain an update to the pool's session_persistence, then the pool's
session_persistence gets cleared.  Observe:

Run:

# neutron lbaas-loadbalancer-create --name lb1 private-subnet
# neutron lbaas-listener-create --name listener1 --loadbalancer lb1 --protocol HTTP --protocol-port 80
# neutron lbaas-pool-create --name pool1 --lb-algorithm ROUND_ROBIN --listener listener1 --protocol HTTP --session-persistence type=SOURCE_IP

lbaas_sessionpersistences table looks like:

mysql> select * from lbaas_sessionpersistences;
+--------------------------------------+-----------+-------------+
| pool_id                              | type      | cookie_name |
+--------------------------------------+-----------+-------------+
| faa5d800-60c1-49e6-aab7-c3d737098837 | SOURCE_IP | NULL        |
+--------------------------------------+-----------+-------------+
1 row in set (0.00 sec)

Now update something other than the session_persistence on the pool:

# neutron lbaas-pool-update --lb_algorithm=ROUND_ROBIN pool1

lbaas_sessionpersistences table looks like:

mysql> select * from lbaas_sessionpersistences;
Empty set (0.00 sec)

** Affects: neutron
     Importance: Undecided
     Assignee: Stephen Balukoff (sbalukoff)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Stephen Balukoff (sbalukoff)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1552086

Title:
  LBaaS v2 updating pool clears session_persistence

Status in neutron:
  New

Bug description:
  It appears that whenever a lbaasv2 is updated, if the update does not
  contain an update to the pool's session_persistence, then the pool's
  session_persistence gets cleared.  Observe:

  Run:

  # neutron lbaas-loadbalancer-create --name lb1 private-subnet
  # neutron lbaas-listener-create --name listener1 --loadbalancer lb1 --protocol HTTP --protocol-port 80
  # neutron lbaas-pool-create --name pool1 --lb-algorithm ROUND_ROBIN --listener listener1 --protocol HTTP --session-persistence type=SOURCE_IP

  lbaas_sessionpersistences table looks like:

  mysql> select * from lbaas_sessionpersistences;
  +--------------------------------------+-----------+-------------+
  | pool_id                              | type      | cookie_name |
  +--------------------------------------+-----------+-------------+
  | faa5d800-60c1-49e6-aab7-c3d737098837 | SOURCE_IP | NULL        |
  +--------------------------------------+-----------+-------------+
  1 row in set (0.00 sec)

  Now update something other than the session_persistence on the pool:

  # neutron lbaas-pool-update --lb_algorithm=ROUND_ROBIN pool1

  lbaas_sessionpersistences table looks like:

  mysql> select * from lbaas_sessionpersistences;
  Empty set (0.00 sec)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1552086/+subscriptions


Follow ups