Jira (FACT-1677) facter get child interfaces's ip address twice with intended for the primary interface

[clux (JIRA)]

clux updated an issue

Facter / FACT-1677 facter get child interfaces's ip address twice with intended for the primary interface Change By: clux Summary: facter get  child interfaces's  ip address twice with  a child  intended for the primary  interface  configured Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Adrien Thebo (JIRA)]

Adrien Thebo updated an issue

Facter / FACT-1677 facter get child interfaces's ip address twice with intended for the primary interface

Change By: Adrien Thebo Labels: offboarding

Add Comment

[Adrien Thebo (JIRA)]

Adrien Thebo updated an issue

Facter / FACT-1677 facter get child interfaces's ip address twice with intended for the primary interface

Change By: Adrien Thebo Team: Platform OS

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-1677 facter get child interfaces's ip address twice with intended for the primary interface

Change By: Branan Riley Component/s: CLI

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-1677 facter get child interfaces's ip address twice with intended for the primary interface

Change By: Branan Riley Labels: needs_repro networking triaged

Add Comment

[Branan Riley (JIRA)]

Branan Riley commented on FACT-1677

Re: facter get child interfaces's ip address twice with intended for the primary interface Making sure I fully understand this issue: Facter is outputting blocks for both your 'eth1' and 'eth1:1' devices, but is also listing the 'eth1:1' ip as a binding for 'eth1'? Could you provide a bit more information on how the 'eth1:1' device is set up so we can try to reproduce internally?

Add Comment

[Sebastian Bublitz (Jira)]

Sebastian Bublitz commented on FACT-1677

Re: facter get child interfaces's ip address twice with intended for the primary interface

This issue seems to still be present in recent versions of facter. We recently stumbled upon this issue and found a way to reproduce it. The IP addresses are added via `ip addr add <address> dev eth0 alias eth0:0`. This does not trigger the problem, Facter starts reporting the new addresses on the base eth0 only if you add a route with source address from the alias address. So e.g. `ip route add <target> dev eth0 source <alias ip>`.

Add Comment

This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)