yahoo-eng-team team mailing list archive

[Aniket Dandekar <aniketad88@xxxxxxxxx>]

Public bug reported:

Neutron(happens only during recreating a LBaaS listener on the
loadbalancer) is not setting the device_owner value of the port to
'neutron:LBAASV2', but instead its ' ' i.e empty. The
lbaas_agent_callbacks during the create listener is not setting the
device_owner to 'neutron:LBAASV2' for the port.

Reproduction Steps:

1. neutron lbaas-loadbalancer-create --name l-0 s-0
2. neutron lbaas-listener-create --loadbalancer l-0 --protocol HTTP --protocol-port 80 --name ls-1
3. neutron lbaas-listener-delete ls-1
4. neutron lbaas-listener-create --loadbalancer l-0 --protocol HTTP --protocol-port 80 --name ls-1

device owner after step 4 is '' as opposed to 'neutron:LBAASV2'

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Neutron does not set the device_owner  correctly during LBaaS listener
  recreate

Status in neutron:
  New

Bug description:
  Neutron(happens only during recreating a LBaaS listener on the
  loadbalancer) is not setting the device_owner value of the port to
  'neutron:LBAASV2', but instead its ' ' i.e empty. The
  lbaas_agent_callbacks during the create listener is not setting the
  device_owner to 'neutron:LBAASV2' for the port.

  Reproduction Steps:

  1. neutron lbaas-loadbalancer-create --name l-0 s-0
  2. neutron lbaas-listener-create --loadbalancer l-0 --protocol HTTP --protocol-port 80 --name ls-1
  3. neutron lbaas-listener-delete ls-1
  4. neutron lbaas-listener-create --loadbalancer l-0 --protocol HTTP --protocol-port 80 --name ls-1

  device owner after step 4 is '' as opposed to 'neutron:LBAASV2'

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