Public bug reported: When a tag's added to (or removed from) a resource, no notification is generated indicating that the network (or port or whatever) has changed, although tags *are* included in notification and API data for those resources. It'd be more consistent if attaching a tag to a network generated a notification in the same way as if it were renamed.
My use case is that Searchlight would really like to index tags attached to networks, routers, etc since it's a very powerful feature but we can't provide up to date information unless a notification's sent. Tested on neutron mitaka rc1. ** 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/1560226 Title: No notifications on tag operations Status in neutron: New Bug description: When a tag's added to (or removed from) a resource, no notification is generated indicating that the network (or port or whatever) has changed, although tags *are* included in notification and API data for those resources. It'd be more consistent if attaching a tag to a network generated a notification in the same way as if it were renamed. My use case is that Searchlight would really like to index tags attached to networks, routers, etc since it's a very powerful feature but we can't provide up to date information unless a notification's sent. Tested on neutron mitaka rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1560226/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp