[AWS] - multiple interfaces cases hitting (AddressLimitExceeded)

[fruch]

Packages

Issue description

• This issue is a regression.
• It is unknown if this issue is a regression.

job is failing to allocate public address:

2024-11-30 04:15:10.564: (TestFrameworkEvent Severity.ERROR) period_type=one-time event_id=a68886dc-6201-4f92-b1d6-0bb350373c78, source=LongevityTest.SetUp()
exception=An error occurred (AddressLimitExceeded) when calling the AllocateAddress operation: The maximum number of addresses has been reached.

we should be asking for higher limits for addresses

Installation details

Cluster size: 6 nodes (i4i.4xlarge)

Scylla Nodes used in this run:

• longevity-tls-50gb-3d-master-db-node-e8dd10cf-6 (54.171.165.161 | 10.4.22.38) (shards: -1)
• longevity-tls-50gb-3d-master-db-node-e8dd10cf-5 (34.251.79.123 | 10.4.22.242) (shards: -1)
• longevity-tls-50gb-3d-master-db-node-e8dd10cf-4 (52.210.58.221 | 10.4.20.232) (shards: -1)
• longevity-tls-50gb-3d-master-db-node-e8dd10cf-3 (99.81.14.68 | 10.4.22.101) (shards: -1)
• longevity-tls-50gb-3d-master-db-node-e8dd10cf-2 (3.248.141.35 | 10.4.22.7) (shards: -1)
• longevity-tls-50gb-3d-master-db-node-e8dd10cf-1 (63.33.238.16 | 10.4.23.20) (shards: -1)

OS / Image: ami-09d8c22a0006e46a8 (aws: undefined_region)

Test: longevity-50gb-3days-test
Test id: e8dd10cf-477b-4756-8c06-2eccdb8b0d80
Test name: scylla-master/tier1/longevity-50gb-3days-test
Test method: longevity_test.LongevityTest.test_custom_time
Test config file(s):

• longevity-50GB-3days-authorization-and-tls-ssl.yaml

Logs and commands

• Restore Monitor Stack command: $ hydra investigate show-monitor e8dd10cf-477b-4756-8c06-2eccdb8b0d80
• Restore monitor on AWS instance using Jenkins job
• Show all stored logs command: $ hydra investigate show-logs e8dd10cf-477b-4756-8c06-2eccdb8b0d80

Logs:

• db-cluster-e8dd10cf.tar.gz - https://cloudius-jenkins-test.s3.amazonaws.com/e8dd10cf-477b-4756-8c06-2eccdb8b0d80/20241130_041530/db-cluster-e8dd10cf.tar.gz
• sct-runner-events-e8dd10cf.tar.gz - https://cloudius-jenkins-test.s3.amazonaws.com/e8dd10cf-477b-4756-8c06-2eccdb8b0d80/20241130_041530/sct-runner-events-e8dd10cf.tar.gz
• sct-e8dd10cf.log.tar.gz - https://cloudius-jenkins-test.s3.amazonaws.com/e8dd10cf-477b-4756-8c06-2eccdb8b0d80/20241130_041530/sct-e8dd10cf.log.tar.gz
• loader-set-e8dd10cf.tar.gz - https://cloudius-jenkins-test.s3.amazonaws.com/e8dd10cf-477b-4756-8c06-2eccdb8b0d80/20241130_041530/loader-set-e8dd10cf.tar.gz
• monitor-set-e8dd10cf.tar.gz - https://cloudius-jenkins-test.s3.amazonaws.com/e8dd10cf-477b-4756-8c06-2eccdb8b0d80/20241130_041530/monitor-set-e8dd10cf.tar.gz

Jenkins job URL
Argus

[fruch]

requested to raise the limit to 100 in this region, as we have in us-east-1

[soyacz]

also we could consider not assigning public ip's to nodes (https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/service-resource/create_instances.html#:~:text=AssociatePublicIpAddress%27%3A%20True%7CFalse%2C)

[fruch]

also we could consider not assigning public ip's to nodes (https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/service-resource/create_instances.html#:~:text=AssociatePublicIpAddress%27%3A%20True%7CFalse%2C)

that's not the limit we are hitting.

[fruch]

the request was approved by AWS

closing