Bug 1238767 - Default route not set according to env file when using network isolation in virt env with single-nic-vlans templates
Summary: Default route not set according to env file when using network isolation in v...
Keywords:
Status: CLOSED DUPLICATE of bug 1236251
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: Director
Assignee: Dan Sneddon
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-02 14:52 UTC by Marius Cornea
Modified: 2017-03-20 09:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-02 17:33:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Marius Cornea 2015-07-02 14:52:24 UTC
Description of problem:
I'm doing a deployment with network isolation on a virt environment by using the default single-nic-with-vlan templates. I am setting up the networks subnets, allocation pools and ExternalInterfaceDefaultRoute in my network-environment.yaml but the overcloud nodes result in having the default route on the provisioning network.  

How reproducible:
100% 

Steps to Reproduce:
1. Use the following command to deploy:

openstack overcloud deploy --plan-uuid 6f328f78-1654-4a6e-92b6-3ad465926da5 --control-scale 3 --compute-scale 2 --ceph-storage-scale 0 --block-storage-scale 0 --swift-storage-scale 0 -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e /home/stack/network-environment.yaml --network-cidr 192.168.0.0/24 --floating-ip-cidr=172.16.23.0/24 --floating-ip-start=172.16.23.100 --floating-ip-end=172.16.23.150 --bm-network-gateway=172.16.23.251

2. Check routing table on the overcloud controller

Actual results:
default via 192.0.2.1 dev br-ex  proto static 
169.254.169.254 via 192.0.2.1 dev br-ex  proto static 
172.16.3.0/24 dev vlan40  proto kernel  scope link  src 172.16.3.7 
172.16.20.0/24 dev vlan20  proto kernel  scope link  src 172.16.20.15 
172.16.21.0/24 dev vlan30  proto kernel  scope link  src 172.16.21.15 
172.16.22.0/24 dev vlan50  proto kernel  scope link  src 172.16.22.14 
172.16.23.0/24 dev vlan10  proto kernel  scope link  src 172.16.23.13 
192.0.2.0/24 dev br-ex  proto kernel  scope link  src 192.0.2.20 


Expected results:
Default route would be set via 172.16.23.251 as configured in network-environment.yaml ( ExternalInterfaceDefaultRoute: 172.16.23.251 )

Additional info:

[stack@instack ~]$ cat network-environment.yaml 
parameter_defaults:
  InternalApiNetCidr: 172.16.20.0/24
  StorageNetCidr: 172.16.21.0/24
  TenantNetCidr: 172.16.22.0/24
  ExternalNetCidr: 172.16.23.0/24
  InternalApiAllocationPools: [{'start': '172.16.20.10', 'end': '172.16.20.100'}]
  StorageAllocationPools: [{'start': '172.16.21.10', 'end': '172.16.21.100'}]
  TenantAllocationPools: [{'start': '172.16.22.10', 'end': '172.16.22.100'}]
  ExternalAllocationPools: [{'start': '172.16.23.10', 'end': '172.16.23.100'}]
  ExternalInterfaceDefaultRoute: 172.16.23.251

Comment 3 chris alfonso 2015-07-02 17:11:04 UTC
Dan, is this one a dup?

Comment 5 Dan Sneddon 2015-07-02 17:33:05 UTC
This is a different manifestation of this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1236251

I'm marking this as a duplicate of 1236251, but Marius can you provide the file /usr/share/openstack-tripleo-heat-templates/network/config/single-nic-with-vlans/controller.yaml? You didn't mention which poodle/puddle you were using, and it would be helpful to tie in the controller.yaml to the results you are seeing here. I don't know if you can add it to this ticket after it gets closed as duplicate, if not you can add that to the other ticket.

*** This bug has been marked as a duplicate of bug 1236251 ***


Note You need to log in before you can comment on or make changes to this bug.