Could not boot a VM in a subnet without gateway

Bug #1693446 reported by Zhiyuan Cai
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tricircle
Fix Released
High
Zhiyuan Cai

Bug Description

We can create a subnet without gateway in the central Neutron, but when we boot a VM in that subnet, the request fails since local Neutron is trying to calculate the IP allocation pool based on the central subnet gateway IP, which is None.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tricircle (master)

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

Changed in tricircle:
assignee: nobody → Zhiyuan Cai (luckyvega-g)
status: New → In Progress
Chaoyi Huang (joehuang)
Changed in tricircle:
importance: Undecided → High
milestone: none → pike-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tricircle (master)

Reviewed: https://review.openstack.org/467962
Committed: https://git.openstack.org/cgit/openstack/tricircle/commit/?id=ed79a4d738f6234557ee391097250d7f61dd6a74
Submitter: Jenkins
Branch: master

commit ed79a4d738f6234557ee391097250d7f61dd6a74
Author: zhiyuan_cai <email address hidden>
Date: Thu May 25 17:35:32 2017 +0800

    Boot a VM in a subnet without gateway

    1. What is the problem
    We can create a subnet without gateway in the central Neutron, but when
    we boot a VM in that subnet, the request fails since local Neutron is
    trying to calculate the IP allocation pool based on the central subnet
    gateway IP, which is None.

    2. What is the solution for the problem
    If a central subnet doesn't have gateway, do not re-calculate local IP
    allocation pool when creating local subnet.

    3. What features need to be implemented to the Tricircle to
    realize the solution
    Support booting a VM in a subnet that has not gateway

    Change-Id: I04f7f9f9926f22bca3490ee46e2163b9c17bb8fe
    Closes-Bug: #1693446

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

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