[e2e] recreate stack on ssh handshake failure

[pducolin]

What does this PR do?

Recreate e2e stack on ssh handshake failure error

Motivation

ADXT-558

The following error impacted one job:

command:remote:Command remote-aws-vm-cmd-wait-cloud-init **creating failed** error: after 100 failed attempts: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
            pulumi:pulumi:Stack e2eci-ci-656730910-4670-upgrade-from-6-to-6-test-datadog-agent-debian-9-x86-64 running error: update failed
            pulumi:pulumi:Stack e2eci-ci-656730910-4670-upgrade-from-6-to-6-test-datadog-agent-debian-9-x86-64 **failed** 1 error
        Diagnostics:
          command:remote:Command (remote-aws-vm-cmd-wait-cloud-init):
            error: after 100 failed attempts: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
        
          pulumi:pulumi:Stack (e2eci-ci-656730910-4670-upgrade-from-6-to-6-test-datadog-agent-debian-9-x86-64):
            error: update failed

This is similar to another error reported on the same test, where the error happened at cloud init, with a different output

Process exited with status 2: running \" sudo cloud-init status --wait\"

Describe how to test/QA your changes

Possible Drawbacks / Trade-offs

Additional Notes

[KevinFairise2]

LGTM. debian-9 VMs can be a bit whimsical. That could help

[agent-platform-auto-pr]

[Fast Unit Tests Report]

On pipeline 46926717 (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]

Test changes on VM

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

inv create-vm --pipeline-id=46926717 --os-family=ubuntu

Note: This applies to commit 271f5fc

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Run ID: b52a3bfb-96cf-4057-9d28-0a0bcf4d944d Metrics dashboard Target profiles

Baseline: 16c16b2
Comparison: 271f5fc

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

No significant changes in experiment optimization goals

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

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	file_tree	memory utilization	+0.88	[+0.76, +1.00]	1	Logs
➖	otel_to_otel_logs	ingress throughput	+0.11	[-0.69, +0.91]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.02	[-0.32, +0.37]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.01, +0.01]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.12, +0.10]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.01	[-0.24, +0.21]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.05	[-0.24, +0.14]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.09	[-0.34, +0.16]	1	Logs
➖	idle	memory utilization	-0.13	[-0.18, -0.08]	1	Logs bounds checks dashboard
➖	idle_all_features	memory utilization	-0.15	[-0.25, -0.04]	1	Logs bounds checks dashboard
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.23	[-0.71, +0.25]	1	Logs
➖	basic_py_check	% cpu utilization	-0.28	[-3.04, +2.49]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.54	[-1.26, +0.17]	1	Logs
➖	pycheck_lots_of_tags	% cpu utilization	-0.75	[-3.24, +1.73]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-1.27	[-1.32, -1.22]	1	Logs

Bounds Checks

perf	experiment	bounds_check_name	replicates_passed
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_300ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	idle	memory_usage	10/10
✅	idle_all_features	memory_usage	10/10

Explanation

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".