Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 1692800

Summary: Include prefixes in all router advertisements
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Mark Michelson <mmichels>
Component: OVNAssignee: Mark Michelson <mmichels>
Status: CLOSED CURRENTRELEASE QA Contact: Jianlin Shi <jishi>
Severity: low Docs Contact:
Priority: low    
Version: FDP 19.ACC: ctrautma, jiji, jishi, nusiddiq, rkhan
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-21 15:00:49 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 Mark Michelson 2019-03-26 13:27:39 UTC 
Description of problem:
When using the dhcp_stateful address mode for DHCPv6, OVN does not send prefix information in its router advertisements. This was being done to prevent clients from attempting auto-configuration of its addresses.

The problem is that when using stateful DHCP configuration, there is no way for clients to learn what their IPv6 prefix is if we don't send it in the RA.

The fix for this is to always send IPv6 prefix information. However, do not set the "autonomous address" flag if the address mode is dhcp_stateful.



This issue has already been fixed upstream and backported to fast datapath and will be available in release 19.B. This issue is being opened because the issue was discovered and fixed via IRC discussions, and QE should have a record of the change so they are able to test it. If QE has existing IPv6 RA tests that rely on prefix information not being present when the address mode is dhcp_stateful, this may also require changing of existing tests.
Comment 1 Mark Michelson 2019-03-26 13:28:15 UTC 
Changing status to MODIFIED since it has been accepted upstream and backported downstream as well.
Comment 3 Numan Siddique 2020-08-21 15:00:33 UTC 
20.C has the fix for this, but this BZ was not included in the 20.C errata.
Closing the BZ.