Magnum

retrieving external-network-id is redundant

Bug #1491273 reported by yuanying
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Low
yuanying
Magnum mitaka-1

Bug Description

Currently, external-network-id can accept network name,
so we can set external-network name to baymodel.

yuanying (yuanying)
Changed in magnum:
assignee: nobody → yuanying (ootsuka)
importance: Undecided → Low
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/219592

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

commit fe0417589d2812ed0d7e3fa636b418ec97f8e91a
Author: OTSUKA, Yuanying <email address hidden>
Date: Wed Sep 2 16:52:17 2015 +0900

    Remove retrieving external-network-id

    Currently, external-network-id can accept network name,
    so we can set external-network name to baymodel.
    Previously change `I0d2be33723817c604c6cab704d2efcbd1e4cc79f`
    already removed the same for kubernates baymodel.

    This patch remove from mesos/swarm baymodel.

    Change-Id: Ia9276c75932483b244efe4c8f2eef5c9684128e8
    Closes-Bug: #1491273

Changed in magnum:
status: In Progress → Fix Committed
Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
status: Fix Committed → Fix Released
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.