Re-applying module after remove causes no-show in module-query

Bug #1571799 reported by Peter Stachowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
Medium
Peter Stachowski
Mitaka
Fix Committed
Medium
Peter Stachowski

Bug Description

If you apply a module, remove it and then apply it again it will no longer show up in the module-query command.

Changed in trove:
importance: Undecided → Medium
assignee: nobody → Peter Stachowski (peterstac)
milestone: none → newton-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

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

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

Reviewed: https://review.openstack.org/307418
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=0c506cb404b72a9956718a64640f7389adbe0098
Submitter: Jenkins
Branch: master

commit 0c506cb404b72a9956718a64640f7389adbe0098
Author: Peter Stachowski <email address hidden>
Date: Mon Apr 18 14:56:59 2016 -0400

    Fixed module-apply on removed module

    If you apply a module, remove it and then apply it again it would
    no longer show up in the module-query command. This has been fixed
    and corresponding tests added to the module scenario run.

    Also added missing 'object' to ModuleManager class

    Change-Id: I3302a2547cf88f1da1ba4abca6617981572782d4
    Closes-Bug: #1571799

Changed in trove:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/319326

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (stable/mitaka)

Reviewed: https://review.openstack.org/319326
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=e135bfb38a0abde0ad7183a592233fdc581de5df
Submitter: Jenkins
Branch: stable/mitaka

commit e135bfb38a0abde0ad7183a592233fdc581de5df
Author: Peter Stachowski <email address hidden>
Date: Mon Apr 18 14:56:59 2016 -0400

    Fixed module-apply on removed module

    If you apply a module, remove it and then apply it again it would
    no longer show up in the module-query command. This has been fixed
    and corresponding tests added to the module scenario run.

    Also added missing 'object' to ModuleManager class

    Closes-Bug: #1571799
    (cherry picked from commit I3302a2547cf88f1da1ba4abca6617981572782d4)

    Change-Id: Idecead4b9f021da16bf1b138718b5169bce01205

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/trove 6.0.0.0b2

This issue was fixed in the openstack/trove 6.0.0.0b2 development milestone.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/trove 5.1.0

This issue was fixed in the openstack/trove 5.1.0 release.

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.