Bug 1636671

Summary: Error in Tenant network routes definition in network_data_routed.yaml
Product: Red Hat OpenStack Reporter: Bob Fournier <bfournie>
Component: openstack-tripleo-heat-templatesAssignee: Harald Jensås <hjensas>
Status: CLOSED ERRATA QA Contact: Alexander Chuzhoy <sasha>
Severity: medium Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: mburns, mlammon
Target Milestone: betaKeywords: Triaged
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-9.0.1-0.20181013060872.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:53:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bob Fournier 2018-10-06 14:35:50 UTC 
Description of problem:

Deploying with network_data_routed.yaml is throwing
'Unknown Property ip_netmask' for the Tenant network routes.
Fix the network_data_routed.yaml definition to use the
right keys for the route definition.
Comment 4 mlammon 2018-11-15 19:38:00 UTC 
installed latest osp14 undercloud and doing a template verification on patch
https://review.openstack.org/#/c/608391/

Build:
14   -p 2018-11-13.1

Environment:
openstack-tripleo-heat-templates-9.0.1-0.20181013060879.el7ost.noarch

grep -A2 -B2 "routes: \[{'destination'" /usr/share/openstack-tripleo-heat-templates/network_data_routed.yaml
..
..
..


  ip_subnet: '172.16.1.0/24'
  gateway_ip: '172.16.1.1'
  routes: [{'destination':'172.16.0.0/20', 'nexthop':'172.16.1.1'}]          <---------- fix in place
  allocation_pools: [{'start': '172.16.1.4', 'end': '172.16.1.250'}]
  # Note that tenant tunneling is only compatible with IPv4 addressing at this time.
Comment 6 errata-xmlrpc 2019-01-11 11:53:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045