Skip to content

PR #23959 breaks consul ipv6 registration address #25627

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

Open
42wim opened this issue Apr 9, 2025 · 2 comments · May be fixed by #25632
Open

PR #23959 breaks consul ipv6 registration address #25627

42wim opened this issue Apr 9, 2025 · 2 comments · May be fixed by #25632
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/cni theme/consul theme/networking type/bug

Comments

@42wim
Copy link
Contributor

42wim commented Apr 9, 2025

Nomad version

Nomad v1.9.7
BuildDate 2025-03-11T09:07:15Z
Revision f869597+CHANGES

Operating system and Environment details

Linux 4.18.0-553.46.1.el8_10.x86_64

Issue

After an upgrade from 1.7.7 to 1.9.7 we got an issue with our CNI containers and consul address registration.

#23959 changes the content of netstatus.Address, in our setup this was an IPv6 address inside the CNI bridge and it got registered correctly in consul.

Now this is an IPv4 address as the PR has split it into a netstatus.Address and netstatus.AddressIPv6.

And GetAddress with AddressModeAlloc now returns the ipv4 address

return netStatus.Address, 0, nil

Maybe there should be an option to specify to only use the IPv6 Address like with the docker driver

@jrasell
Copy link
Member

jrasell commented Apr 28, 2025

Hi @42wim and thanks for raising this issue and the linked PR. I'll get this and the PR onto our backlog for review.

@jrasell jrasell added theme/networking theme/consul theme/cni stage/accepted Confirmed, and intend to work on. No timeline committment though. labels Apr 28, 2025
@jrasell jrasell moved this from Needs Triage to Needs Roadmapping in Nomad - Community Issues Triage Apr 28, 2025
@jrasell
Copy link
Member

jrasell commented Apr 28, 2025

Hi @42wim would it be possible to share the configuration you are using to generate the issue you're seeing (CNI plugins, client relevant config)? We had a quick internal chat about this and there was a question of whether client.preferred_address_family= ipv6 would achieve what you're looking for?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/cni theme/consul theme/networking type/bug
Projects
Status: Needs Roadmapping
Development

Successfully merging a pull request may close this issue.

2 participants