Skip to content

Conversation

@lukebakken
Copy link
Collaborator

This PR follows the same pattern as
rabbit_peer_discovery_httpc:maybe_configure_inet6/0, where inet:get_rc/0 is used to determine if we're running in an IPv6-only environment. If so, the correct IPv6 address will be used for EC2 IMDS HTTP API requests.

Fixes #14974

This PR follows the same pattern as
`rabbit_peer_discovery_httpc:maybe_configure_inet6/0`, where
`inet:get_rc/0` is used to determine if we're running in an IPv6-only
environment. If so, the correct IPv6 address will be used for EC2 IMDS
HTTP API requests.

Fixes rabbitmq#14974
@michaelklishin
Copy link
Collaborator

@lukebakken this change looks reasonable, so let's merge it so that a new OCI is produced for the reporter of #14974 to try.

@michaelklishin michaelklishin merged commit d067f1b into rabbitmq:main Nov 19, 2025
289 checks passed
@michaelklishin michaelklishin changed the title Make rabbitmq_aws IPv6-aware Make rabbitmq_aws use the IPv6 discovery endpoints if the node is configured to use IPv6 Nov 19, 2025
@the-mikedavis the-mikedavis deleted the rabbitmq-server-14974 branch November 19, 2025 23:36
@michaelklishin
Copy link
Collaborator

@Mergifyio backport v4.2.x

@mergify
Copy link

mergify bot commented Nov 20, 2025

backport v4.2.x

✅ Backports have been created

michaelklishin added a commit that referenced this pull request Nov 20, 2025
Make `rabbitmq_aws` use the IPv6 discovery endpoints if the node is configured to use IPv6 (backport #14975)
michaelklishin added a commit that referenced this pull request Nov 21, 2025
Make `rabbitmq_aws` use the IPv6 discovery endpoints if the node is configured to use IPv6 (backport #14975) (backport #14986)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AWS peer discovery tries to use an IPv4-specific API endpoint in an IPv6-only environment

2 participants