Description of problem: os-net-config does not handle IPv6 static routes (they appear in the wrong file, so the route never gets installed). Version-Release number of selected component (if applicable): os-net-config.noarch 0.1.4-6.el7ost How reproducible: 100% Steps to Reproduce: 1. Configure a static IPv6 route in os-net-config template 2. Run os-net-config 3. Actual results: The IPv6 route gets put into /etc/syssconfig/network-scripts/route-<iface>, but it never gets installed. Expected results: The IPv6 route should be installed. Additional info: os-net-config is only capable of writing to /etc/default/sysconfig/route-<iface>, while for IPv6 routes we need to write to /etc/sysconfig/network-scripts/route6-<iface> I think we can use a basic regex to determine if we have an IPv6 or IPv4 route, and deal with it accordingly.
Upstream patch submitted for os-net-config to support IPv6 routes: https://review.openstack.org/#/c/268806/
Created downstream review for rhos-7.0-patches: https://code.engineering.redhat.com/gerrit/65764
Destination subnet is in IPv4 format: [root@overcloud-controller-0 ~]# cat /etc/sysconfig/network-scripts/route6-vlan10 0.0.0.0/0 via 2001:db8:fd00:1000:dead:beef:cafe:f00 dev vlan10 IPv6 format: [root@overcloud-controller-0 ~]# cat /etc/sysconfig/network-scripts/route6-vlan10 ::/0 via 2001:db8:fd00:1000:dead:beef:cafe:f00 dev vlan10
I've just realized that I need to adjust the nic templates with the ipv6 formatted default route. Moving this back to ON_QA.
Looks good after updating the nic templates: in controller.yaml: - type: vlan vlan_id: {get_param: ExternalNetworkVlanID} addresses: - ip_netmask: {get_param: ExternalIpSubnet} routes: - ip_netmask: ::/0 next_hop: {get_param: ExternalInterfaceDefaultRoute} [root@overcloud-controller-0 heat-admin]# ip -6 r | grep default default via 2001:db8:fd00:1000:dead:beef:cafe:f00 dev vlan10 metric 1024
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://rhn.redhat.com/errata/RHBA-2016-0264.html