simulate functionality broken

Bug #1400921 reported by Tim Hinrichs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
congress
Fix Released
High
Tim Hinrichs

Bug Description

The recent changes to include multiple policies broke the simulation functionality. It does not properly insert data into the appropriate policy, so if you include say nova:servers+(1,2) in the update sequence, it will not insert it into the 'nova' policy. This means the simulation functionality will not properly answer the query.

Tim Hinrichs (thinrichs)
Changed in congress:
importance: Undecided → High
assignee: nobody → Tim Hinrichs (thinrichs)
milestone: none → kilo-1
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to congress (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to congress (master)

Reviewed: https://review.openstack.org/140542
Committed: https://git.openstack.org/cgit/stackforge/congress/commit/?id=153665c0aa083caac7166559648c2203bad5c691
Submitter: Jenkins
Branch: master

commit 153665c0aa083caac7166559648c2203bad5c691
Author: Tim Hinrichs <email address hidden>
Date: Tue Dec 9 16:39:07 2014 -0800

    Fix for simulation bug

    Previously, simulation did not properly insert data into
    policies other than the one given for the query. This led
    to incorrect results. For example nova:p+(1) did not get inserted
    into the nova policy, hence a query relying on nova:p(1) could
    fail.

    This change identifies the policy to which a data element is targeted
    and inserts/deletes it from the appropriate policy.

    Change-Id: I43a2deb346d0b2a09e59398607cd5d545b711ecc
    Closes-bug: 1400921

Changed in congress:
status: In Progress → Fix Committed
Tim Hinrichs (thinrichs)
Changed in congress:
status: Fix Committed → Fix Released
Sean Roberts (sarob)
Changed in congress:
milestone: kilo-1 → kilo-2
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.