Magnum

Incorrect Arguments passed when raising MagnumServiceNotFound exception.

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

Bug Description

Message in MagnumServiceNotFound exception expect key value pair to correctly print the message for the exception. But arguments are not passed in key value format.

rajiv (rajiv-kumar)
Changed in magnum:
assignee: nobody → rajiv (rajiv-kumar)
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/364219

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/364219
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=b60c447d9101ad75b741da3917eab4d21df1929d
Submitter: Jenkins
Branch: master

commit b60c447d9101ad75b741da3917eab4d21df1929d
Author: Rajiv Kumar <email address hidden>
Date: Thu Sep 1 15:53:53 2016 +0530

    Correctly raising MagnumServiceNotFound exception

    Passed arguments in key value form, while raising
    MagnumServiceNotFound exception, as expected by the exception
    message.

    Change-Id: Iae767db0bbd264bb668b2845284fc5d876f7025d
    Closes-Bug: #1619225

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

This issue was fixed in the openstack/magnum 3.1.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.