Network create does not return variables in response

Bug #1674815 reported by Thomas Maddox
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
craton
Fix Released
Critical
Thomas Maddox

Bug Description

Same problem as in #1648437. We need to return variables in the response on Network create. https://bugs.launchpad.net/craton/+bug/1648437

Changed in craton:
importance: Undecided → Critical
assignee: nobody → Thomas Maddox (thomas-maddox)
milestone: none → v0.1.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to craton (master)

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

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

Reviewed: https://review.openstack.org/448285
Committed: https://git.openstack.org/cgit/openstack/craton/commit/?id=5852565dcdb7ee86465b9714b1dd706812820130
Submitter: Jenkins
Branch: master

commit 5852565dcdb7ee86465b9714b1dd706812820130
Author: Thomas Maddox <email address hidden>
Date: Tue Mar 21 21:21:13 2017 +0000

    Return variables in response on Network create

    If a user creates a network and also passes variables
    during the create process the variables get created
    but are not present in the response.

    This patch fixes that by adding variables in response
    for a create calls on networks when variable was in
    the create request body.

    Change-Id: I2320f5b07d3544286234ecc5b1cee4eea999b59e
    Closes-Bug: 1674815

Changed in craton:
status: In Progress → Fix Released
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.