[new-e2e] Check empty instance reservations condition for dumpKindClusterState

[fanny-jiang]

What does this PR do?

Fixes a panic/index out of range error in AWS kind provisioner's dumpKindClusterState function that occurs when instancesDescription is not nil but instancesDescription.Reservations = [].

Print statements while debugging:

INSTANCES DESCRIPTION:  &{<nil> [] {map[{}:-718501000 {}:0x140001b47f8 {}:088289ef-7e83-415d-9120-49e8ab06b72e {}:{13967045742491301000 44903162001 0x112b22d60} {}:{0 63871199208 <nil>} {}:{[{<nil> false false {map[{}:-718501000 {}:0x140001b47f8 {}:088289ef-7e83-415d-9120-49e8ab06b72e {}:{13967045742491301000 44903162001 0x112b22d60} {}:{0 63871199208 <nil>}]}}]}]} {}}
INSTANCES DESCRIPTION.RESERVATIONS:  []
=== NAME  TestAWSKindSuite
    panic.go:115: test panicked: runtime error: index out of range [0] with length 0

Motivation

bugfix

Describe how you validated your changes

Possible Drawbacks / Trade-offs

Additional Notes

[agent-platform-auto-pr]

[Fast Unit Tests Report]

On pipeline 52025066 (CI Visibility). The following jobs did not run any unit tests:

Jobs:

• tests_deb-arm64-py3
• tests_deb-x64-py3
• tests_flavor_dogstatsd_deb-x64
• tests_flavor_heroku_deb-x64
• tests_flavor_iot_deb-x64
• tests_rpm-arm64-py3
• tests_rpm-x64-py3
• tests_windows-x64

If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor ed913b5cc2e01e214d62458352085f69a70c9215

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.00MB	✅	1197.91MB	1197.91MB	140.00MB
datadog-agent-x86_64-rpm	0.00MB	✅	1207.22MB	1207.22MB	140.00MB
datadog-agent-x86_64-suse	0.00MB	✅	1207.22MB	1207.22MB	140.00MB
datadog-agent-arm64-deb	0.00MB	✅	940.27MB	940.27MB	140.00MB
datadog-agent-aarch64-rpm	0.00MB	✅	949.57MB	949.57MB	140.00MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	79.00MB	79.00MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	79.08MB	79.08MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	79.08MB	79.08MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	56.10MB	56.10MB	10.00MB
datadog-heroku-agent-amd64-deb	0.00MB	✅	506.09MB	506.09MB	70.00MB
datadog-iot-agent-amd64-deb	0.00MB	✅	113.76MB	113.76MB	10.00MB
datadog-iot-agent-x86_64-rpm	0.00MB	✅	113.83MB	113.83MB	10.00MB
datadog-iot-agent-x86_64-suse	0.00MB	✅	113.83MB	113.83MB	10.00MB
datadog-iot-agent-arm64-deb	0.00MB	✅	109.21MB	109.21MB	10.00MB
datadog-iot-agent-aarch64-rpm	0.00MB	✅	109.28MB	109.28MB	10.00MB

Decision

✅ Passed

[agent-platform-auto-pr]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv aws.create-vm --pipeline-id=52025066 --os-family=ubuntu

Note: This applies to commit 6c674ae

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: aadfcaaa-091b-4cd1-8553-74f90603cace

Baseline: ed913b5
Comparison: 6c674ae
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.16	[-0.31, +0.63]	1	Logs
➖	quality_gate_idle	memory utilization	+0.11	[+0.08, +0.14]	1	Logs bounds checks dashboard
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.11	[-0.75, +0.97]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.09	[-0.75, +0.93]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.01	[-0.87, +0.90]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	+0.01	[-0.64, +0.65]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.01	[-0.11, +0.13]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.02	[-0.75, +0.71]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.09	[-0.85, +0.67]	1	Logs
➖	file_tree	memory utilization	-0.15	[-0.27, -0.03]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.20	[-0.89, +0.48]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.31	[-1.09, +0.47]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.66	[-0.72, -0.60]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.67	[-0.75, -0.59]	1	Logs bounds checks dashboard
➖	quality_gate_logs	% cpu utilization	-0.84	[-4.07, +2.40]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http1	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http1	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http2	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http2	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency_linear_load	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	lost_bytes	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_300ms_latency	lost_bytes	10/10
✅	file_to_blackhole_300ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10
✅	quality_gate_logs	memory_usage	10/10

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.