yahoo-eng-team team mailing list archive

[Abhishek Raut <abhraut@xxxxxxxxx>]

Public bug reported:

During cisco-network-profile-update, if a tenant id is being added to the network profile, the current behavior is to remove all the tenant-network profile bindings and add the new list of tenants. This works well with horizon since all the existing tenant UUIDs, along with the new tenant id, are passed during update network profile.
If you try to update a network profile and add new tenant to the network profile via CLI, this will replace the existing tenant-network profile bindings and add only the new one.

Expected behavior is to not delete the existing tenant bindings and
instead only add new tenants to the list.

** Affects: neutron
     Importance: Undecided
     Assignee: Abhishek Raut (abhraut)
         Status: New


** Tags: cisco

** Changed in: neutron
     Assignee: (unassigned) => Abhishek Raut (abhraut)

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

Title:
  Cisco N1kv: Fix add-tenant in update network profile

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  During cisco-network-profile-update, if a tenant id is being added to the network profile, the current behavior is to remove all the tenant-network profile bindings and add the new list of tenants. This works well with horizon since all the existing tenant UUIDs, along with the new tenant id, are passed during update network profile.
  If you try to update a network profile and add new tenant to the network profile via CLI, this will replace the existing tenant-network profile bindings and add only the new one.

  Expected behavior is to not delete the existing tenant bindings and
  instead only add new tenants to the list.

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