-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Flaky Test]: Failed to prepare an instance – could not run "unzip agent-repo.zip -d agent" though SSH: wait: remote command exited without exit status or exit signal #4810
Comments
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
Should be fixed by addressing #4794 |
This is an interesting one for trying to solve with retries, the actual failing command is an unzip which should never fail. It is potentially resource intensive on the host machine, and could take longer than other commands. I went looking for patterns and I see that every single failure here is on a Are they in a different region? Are they a weaker instance type? Can changing these things help? Here are some snippets before I grabbed showing the instance type and timestamp showing this pattern:
|
The amd64 machines are elastic-agent/pkg/testing/ogc/supported.go Lines 23 to 35 in 0b99ccb
The arm64 machines are elastic-agent/pkg/testing/ogc/supported.go Lines 49 to 61 in 0b99ccb
|
Reading https://cloud.google.com/compute/docs/general-purpose-machines#t2a_machines this jumped out:
The T2A's have half the effective cores that the E2's do (which presumably support SMT/hyperthreading). I wonder if bumping up to |
Should be fixed by #4852 for now following with the full resolution in https://github.com/elastic/ingest-dev/issues/3439 later. |
Failing test case
Multiple upgrade tests
Error message
could not run "unzip agent-repo.zip -d agent" though SSH: wait: remote command exited without exit status or exit signal
Build
OS
Linux
Stacktrace and notes
The text was updated successfully, but these errors were encountered: