Ben Nguyen 4a324706a4 AWS peer discovery: ensure consistent hostname path ordering (#14557) ... * AWS peer discovery: ensure consistent hostname path ordering AWS EC2 API returns networkInterfaceSet and privateIpAddressesSet in arbitrary order, causing non-deterministic hostname resolution during peer discovery. This leads to inconsistent cluster formation. Changes: - Sort network interfaces by deviceIndex (0 first for primary ENI) - Sort private IP addresses by primary flag (primary=true first) - Add debug logging to show hostname path selection and sorting results - Add comprehensive unit tests for sorting behavior The sorting ensures deviceIndex=0 and primary=true IPs are consistently selected first, making peer discovery deterministic across deployments. * AWS peer discovery: ensure consistent hostname path ordering (address feedback on debug logs and sorting helper functions)		2025-09-23 14:19:07 -07:00
..
config_schema_SUITE_data	add hostname path override	2023-12-12 14:50:38 -08:00
integration_SUITE_data	Capture container logs in rabbitmq_peer_discovery_aws suite	2023-12-04 12:12:56 +01:00
aws_ecs_util.erl	Bump (c) line year	2025-01-01 17:54:10 -05:00
config_schema_SUITE.erl	Bump (c) line year	2025-01-01 17:54:10 -05:00
integration_SUITE.erl	Bump (c) line year	2025-01-01 17:54:10 -05:00
unit_SUITE.erl	AWS peer discovery: ensure consistent hostname path ordering (#14557)	2025-09-23 14:19:07 -07:00