Bug 2107516 - L2 error with ipv4 only interface with a linklocal address
Summary: L2 error with ipv4 only interface with a linklocal address
Keywords:
Status: CLOSED DUPLICATE of bug 2109059
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.12.0
Assignee: Federico Paolinelli
QA Contact: Arti Sood
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-15 10:52 UTC by Federico Paolinelli
Modified: 2022-07-21 12:07 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-21 12:07:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Federico Paolinelli 2022-07-15 10:52:25 UTC 
Description of problem:
Found by an upstream user.

If the nodes have an interface with ipv4 only but a linklocal address attached (169.254.0.0/16) the announcer setup will fail.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Have a v4 only interface with a linklocal address attached
2. Try to advertise via l2
3.

Actual results:
Errors in the speaker, not all the interfaces are added to the arp responder (it's a loop, so it depends on the order). 

Expected results:
No errors related to trying to create an ndp responder on a v4 only interface.

Additional info:
Comment 2 Federico Paolinelli 2022-07-21 12:07:39 UTC 
Closing as dupe of 2109059

*** This bug has been marked as a duplicate of bug 2109059 ***
Note You need to log in before you can comment on or make changes to this bug.