-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 link-local address oddities on LinuxONE in CI #2368
Comments
Hmmm ... My linux laptop says the same for the loopback interface so I'm not sure this is a zLinux/Marist thing Here's the
|
Do you have a non-loopback IPv6 interface that has an address starting with Now that you mention it, though, whether or not IPv6 loopback requires an |
I have seen IPv6 related failures on zLinux elsewhere (outside Node) - I'll try and take a look at that PR in the next day and see what happens on one of my systems unless someone else gets there first :-) |
|
That is both encouraging and discouraging at the same time. I wonder why it fails consistently on LinuxONE in CI, but seemingly nowhere else. Bug in the code? Bug in the test? Bug in LinuxONE? Misconfiguration in CI? |
@sxa I would be useful if you clarified what you mean by "on my Marist system". If it passed on a different machine than the one we have in the CI we need to figure out what the difference is in terms of configuration. |
The issue is definitely with the network interface name that is selected by the test. If it has a I was initially concerned that this might be a bug in On that basis we have two options:
If I make that change to the test case then it passes on my Marist RHEL77 system (otherwise it fails in the same way as you've seen in CI). As mentioned previously, Ubuntu Marist machines do not show the problem as they have an interface name of Interestingly I tried the same change on my RHEL x64 laptop and putting a |
This turned out to be a bug in core and was fixed via nodejs/node#34364. |
I could be mistaken somewhere somehow, but I think the problem with a test on LinuxONE might be a misconfiguration on the machine. I'm not sure who to ping about this. Maybe @mhdawson knows?
IPv6 link-local addresses start with
fe80:
.Below is the output of
os.networkInterfaces()
on that machine. As you can see, thelo
interface does not have a link-local address. I believe this is a violation of RFC 4291 Section 2.8. (Wikipedia has it in more plain language: "Unlike IPv4, IPv6 requires a link-local address on every network interface on which the IPv6 protocol is enabled, even when routable addresses are also assigned.")Originally posted by @Trott in nodejs/node#14500 (comment)
The text was updated successfully, but these errors were encountered: