Magnum

Wrong usage of MagnumService object

Bug #1539438 reported by yangly
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
yangly

Bug Description

Some of MagnumService's function doesn't require context at all, we should clear document these and correct some of wrong usage.

yangly (6618225-t)
Changed in magnum:
assignee: nobody → yangly (6618225-t)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

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

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

Reviewed: https://review.openstack.org/273927
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=28f7f0bbd1a6751b557e58e5783d445d6142538e
Submitter: Jenkins
Branch: master

commit 28f7f0bbd1a6751b557e58e5783d445d6142538e
Author: YangLiYun <email address hidden>
Date: Fri Jan 29 15:34:24 2016 +0800

    Cleanup MagnumService Object usage

    Some of MagnumService's function doesn't require context at all, we
    should clear document these and correct some of wrong usage.

    Closes-Bug: #1539438
    Change-Id: I2b576e8e7fa0b048f022940dc23422d822b68681

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 2.0.0

This issue was fixed in the openstack/magnum 2.0.0 release.

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

Other bug subscribers

Remote bug watches

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