Bug 1636671 - Error in Tenant network routes definition in network_data_routed.yaml
Summary: Error in Tenant network routes definition in network_data_routed.yaml
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 14.0 (Rocky)
Assignee: Harald Jensås
QA Contact: Alexander Chuzhoy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-06 14:35 UTC by Bob Fournier
Modified: 2019-01-11 11:53 UTC (History)
2 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.0.1-0.20181013060872.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:53:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 608391 0 None None None 2018-10-06 14:35:50 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:53:48 UTC

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


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