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

Bug 2107516

Summary:	L2 error with ipv4 only interface with a linklocal address
Product:	OpenShift Container Platform	Reporter:	Federico Paolinelli <fpaoline>
Component:	Networking	Assignee:	Federico Paolinelli <fpaoline>
Networking sub component:	Metal LB	QA Contact:	Arti Sood <asood>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	medium
Version:	4.11
Target Milestone:	---
Target Release:	4.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-21 12:07:39 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 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 ***