yahoo-eng-team team mailing list archive

[OpenStack Infra <1560226@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/298133
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0daed9ebcab7d46d066fd9d8af576d9aca0a7205
Submitter: Jenkins
Branch:    master

commit 0daed9ebcab7d46d066fd9d8af576d9aca0a7205
Author: Hirofumi Ichihara <ichihara.hirofumi@xxxxxxxxxxxxx>
Date:   Tue Nov 29 14:26:24 2016 +0900

    Add notify for tag operations
    
    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.
    This patch adds notify for tag operations.
    
    Change-Id: I4373b2220f87751a4d89462bef37d04bf9a71fe7
    Closes-Bug: #1560226


** Changed in: neutron
       Status: In Progress => 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/1560226

Title:
  No notifications on Neutron tag operations

Status in neutron:
  Fix Released
Status in OpenStack Search (Searchlight):
  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