tripleo

Problem deploying single-nic-vlans custom external net range via Quickstart

Bug #1756878 reported by Jiří Stránský on 2018-03-19

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	tripleo	Fix Released	Medium	Jiří Stránský	tripleo rocky-1

Bug Description

When providing custom range for undercloud_external_network_cidr (e.g. when the default 10.0.0.x range is unsuitable), and deploying with single-nic-vlans network isolation, the overcloud controller nodes have no default route defined.

Tags:

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-03-19: Fix proposed to tripleo-quickstart-extras (master)

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

Changed in tripleo:
status:	Triaged → In Progress

Jiří Stránský (jistr) on 2018-03-19

tags:	added: netw
tags:	added: networking removed: netw

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-03-23: Change abandoned on tripleo-quickstart-extras (master)

Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/554225
Reason: clear up the gate to merge CI blockers, I'll restore the patches.

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-03-23: Fix merged to tripleo-quickstart-extras (master)

Reviewed: https://review.openstack.org/554225
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=241f2e569bd827c7a66456254404e4124cbde592
Submitter: Zuul
Branch: master

commit 241f2e569bd827c7a66456254404e4124cbde592
Author: Jiri Stransky <email address hidden>
Date: Mon Mar 19 14:15:48 2018 +0100

Set ExternalInterfaceDefaultRoute when setting ExternalNetCidr

    After change I3bdb7d00dab5a023dd8b9c94c0f89f84357ae7a4 was introduced,
    External network isn't "special" anymore in the network templates, it
    gets generated as any other network. The default IP ranges and default
    route come from network_data.yaml. Whenever we override one, we should
    also override the other, otherwise we get non-matching
    settings. E.g. my deployment with custom
    `undercloud_external_network_cidr` previously resulted in:

    (undercloud) [stack@undercloud ~]$ openstack subnet show external_subnet
    | allocation_pools | 172.20.0.4-172.20.0.250 |
    | cidr | 172.20.0.0/24 |
    | gateway_ip | 10.0.0.1 |

    ...which didn't work out, the controllers didn't have a default route
    created at all. With this patch, the default route will get
    automatically pointed to 172.20.0.1.

Change-Id: I99cbb7c652e374cb5c256a706661ba7ce5038b87
Closes-Bug: #1756878