Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1684533

Summary: net.ipv6.conf.all.forwarding disabled in qrouter causing inter-tenant to fail when neutron router does not have a gateway
Product: Red Hat OpenStack Reporter: Jaison Raju <jraju>
Component: openstack-neutronAssignee: Slawek Kaplonski <skaplons>
Status: CLOSED ERRATA QA Contact: Federico Ressi <fressi>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: amuller, ccamposr, chrisw, cmuresan, dalvarez, jraju, kmehta, psahoo, scohen, skaplons, supadhya, ykulkarn
Target Milestone: asyncKeywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-neutron-9.4.1-38.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-30 16:58:16 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 Jaison Raju 2019-03-01 13:16:28 UTC
Description of problem:
ipv6 vxlan tenant based Instance cannot ping Instance from another tenant over a neutron router.
2 tenant subnets were created with ipv6 addressing mode as 'dhcpv6-stateful' & have a port on a ha router.

Each instance was able to ping the IP of other tenant subnet's port which is on router. & the vice-versa is true.
Although instance could not ping other tenant subnet's gateway or the other guest.

We noticed that ipv6 forwarding was disabled in the qrouter namespace.
  sudo ip netns exec qrouter-3345aeb1-c4a9-4e43-b2d6-e41929d1ff6f sysctl net.ipv6.conf.all.forwarding
After enabling this, ping works well.
  sudo ip netns exec qrouter-3345aeb1-c4a9-4e43-b2d6-e41929d1ff6f sysctl -w net.ipv6.conf.all.forwarding=1


Version-Release number of selected component (if applicable):
RHOS10
neutron 9.4.1-28

How reproducible:
Always in customer environment

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 27 errata-xmlrpc 2019-04-30 16:58:16 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/RHSA-2019:0916

Comment 28 Bernard Cafarelli 2019-06-24 13:59:13 UTC
*** Bug 1694849 has been marked as a duplicate of this bug. ***