searchlight-manage index sync output doesn't tell why more than one type selected

Bug #1557303 reported by Travis Tripp
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Searchlight
Fix Released
High
Rick Aulino

Bug Description

The fact that we added resource groups with zero downtime re-indexing doesn't get reflected in the output from the CLI when indexing. Making it confusing as to why when I only specified a single type, they all show up. This needs to be fixed:

ttripp@ubuntu:/opt/stack/searchlight$ searchlight-manage index sync --type OS::Cinder::Volume

Resource types (and indices) matching selection:
  OS::Neutron::Net (searchlight)
    --> OS::Neutron::Port (searchlight)
  OS::Cinder::Volume (searchlight)
    --> OS::Cinder::Snapshot (searchlight)
  OS::Nova::Server (searchlight)
  OS::Cinder::Snapshot (searchlight)
  OS::Neutron::Port (searchlight)
  OS::Glance::Image (searchlight)
  OS::Designate::Zone (searchlight)
    --> OS::Designate::RecordSet (searchlight)
  OS::Designate::RecordSet (searchlight)
  OS::Glance::Metadef (searchlight)

Indexing will NOT delete existing data or mapping(s). It will reindex all resources.
Use '--force' to suppress this message.
OK to continue? [y/n]:

*******************************
IN ADDITION: things get listed twice.

ttripp@ubuntu:/opt/stack/searchlight$ searchlight-manage index sync
Resource types (and indices) matching selection:
  OS::Neutron::Net (searchlight)
    --> OS::Neutron::Port (searchlight)
  OS::Cinder::Volume (searchlight)
    --> OS::Cinder::Snapshot (searchlight)
  OS::Swift::Object (searchlight-swift)
  OS::Nova::Server (searchlight)
  OS::Cinder::Snapshot (searchlight)
  OS::Neutron::Port (searchlight)
  OS::Glance::Image (searchlight)
  OS::Designate::Zone (searchlight)
    --> OS::Designate::RecordSet (searchlight)
  OS::Designate::RecordSet (searchlight)
  OS::Swift::Container (searchlight)
    --> OS::Swift::Object (searchlight-swift)
  OS::Glance::Metadef (searchlight)
  OS::Swift::Account (searchlight-swift)
    --> OS::Swift::Container (searchlight)
        --> OS::Swift::Object (searchlight-swift)
Show less
object is listed twice

ttripp@ubuntu:/opt/stack/searchlight$ searchlight-manage index sync --type OS::Swift::Account
Resource types (and indices) matching selection:
  OS::Swift::Object (searchlight-swift)
  OS::Swift::Account (searchlight-swift)
    --> OS::Swift::Container (searchlight)
        --> OS::Swift::Object (searchlight-swift)

Changed in searchlight:
milestone: none → mitaka-rc1
importance: Undecided → Medium
description: updated
Changed in searchlight:
status: New → Triaged
Changed in searchlight:
importance: Medium → High
Changed in searchlight:
assignee: nobody → Rick Aulino (rick-aulino)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to searchlight (master)

Fix proposed to branch: master
Review: https://review.openstack.org/294168

Changed in searchlight:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to searchlight (master)

Reviewed: https://review.openstack.org/294168
Committed: https://git.openstack.org/cgit/openstack/searchlight/commit/?id=8be07dd8598b412250c6350bb72dc50989209e54
Submitter: Jenkins
Branch: master

commit 8be07dd8598b412250c6350bb72dc50989209e54
Author: Rick Aulino <email address hidden>
Date: Thu Mar 17 10:49:47 2016 -0600

    Fix duplicate entries displayed w/"index sync".

    The "index sync" command will list the set of plugins to be
    re-synced for the user. When we switched over to the Resource
    Group Model, the code to display the plugins was based on the
    older index model and implicitly relied on the child-parent
    relationship to control what got displayed. We need to make this
    relationship more explicit in determining the plugins to display.

    Change-Id: I88af5e7a6837ea7529b487ee1f8fabeb2b783958
    Closes-Bug: #1557303

Changed in searchlight:
status: In Progress → Fix Released
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/searchlight 0.2.0.0rc1

This issue was fixed in the openstack/searchlight 0.2.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.