Hide Forgot
Description of problem: The gateway_ip attribute for the isolated networks are not accurate. It is always set to the first address in the cidr. In the case of external network the gateway should be set to the value specified in the ExternalInterfaceDefaultRoute parameter. ExternalInterfaceDefaultRoute: 2001:db8:fd00:1000:dead:beef:cafe:f00 stack@instack:~>>> neutron subnet-show external_subnet | egrep "allocation_pools|cidr|gateway" | allocation_pools | {"start": "2001:db8:fd00:1000::02", "end": "2001:db8:fd00:1000:ffff:ffff:ffff:fffe"} | | cidr | 2001:db8:fd00:1000::/64 | | gateway_ip | 2001:db8:fd00:1000::1 | In the case of the other isolated networks there should be no gateway_ip set: stack@instack:~>>> neutron subnet-show storage_subnet | egrep "allocation_pools|cidr|gateway" | allocation_pools | {"start": "fd00:fd00:fd00:3000::10", "end": "fd00:fd00:fd00:3000:ffff:ffff:ffff:fffe"} | | cidr | fd00:fd00:fd00:3000::/64 | | gateway_ip | fd00:fd00:fd00:3000::1 | Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-0.8.6-112.el7ost.noarch This doesn't affect functionality since we're assigning the addresses statically on the overcloud nodes.
Given that this bug doesn't affect functionality, I'm reloving it from the list of candidates to fix in 7.3.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
This is a cosmetic issue, but it will be superseded by new functionality which uses the gateway_ip more logically. Setting this to OSP 11 (Ocata) for now for tracking.
Upstream fix is https://review.openstack.org/#/c/499385/
> can you make sure this is targeted correctly? > rhos-12.0.z? but target release 11 Thanks for catching this Jon. Fixed the target release to be 12. Also fixed the Gerrit ID. This isn't planned for backporting to Ocata.
Deployed latest osp 12 2018-03-10.1 Env: openstack-tripleo-heat-templates-7.0.9-6.el7ost.noarch Checked various template and looks like new implementation in place
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/RHSA-2018:0602