Skip to content
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.

fix: set default region for AWS cli #2053

Merged
merged 2 commits into from
Jan 25, 2022
Merged

fix: set default region for AWS cli #2053

merged 2 commits into from
Jan 25, 2022

Conversation

mdelapenya
Copy link
Contributor

@mdelapenya mdelapenya commented Jan 25, 2022 •
edited
Loading

What does this PR do?

It passes the AWS region in which the e2e testing is creating VMs, so that the CLI is able to connect and remove the zombie instances.

Why is it important?

We'd like to remove running instances in a weekly basis, but we saw this error:

[2022-01-25T10:15:12.001Z] + aws ec2 describe-instances --filters Name=tag:ReaperMark,Values=e2e-testing-vm --query Reservations[].Instances[].InstanceId --output text
[2022-01-25T10:15:12.945Z]
[2022-01-25T10:15:12.945Z] You must specify a region. You can also configure your region by running "aws configure".
[2022-01-25T10:15:12.945Z] + aws ec2 terminate-instances --instance-ids
[2022-01-25T10:15:13.895Z]
[2022-01-25T10:15:13.895Z] You must specify a region. You can also configure your region by running "aws configure".
script returned exit code 253

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have run the Unit tests (make unit-test), and they are passing locally
  • I have run the End-2-End tests for the suite I'm working on, and they are passing locally
  • I have noticed new Go dependencies (run make notice in the proper directory)

@mdelapenya mdelapenya added the backport-skip Skip notification from the automated backport with mergify label Jan 25, 2022
@mdelapenya mdelapenya self-assigned this Jan 25, 2022
@mdelapenya mdelapenya requested a review from a team January 25, 2022 11:13
@mdelapenya @v1v
chore: simplify AWS env
62f3c0e 
Co-authored-by: Victor Martinez <[email protected]>
@mdelapenya mdelapenya changed the title fix: set degfault region for AWS cli fix: set default region for AWS cli Jan 25, 2022
@mdelapenya mdelapenya merged commit 9cdd8cd into elastic:main Jan 25, 2022
@elasticmachine
Copy link
Contributor

❕ Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Reason: Aborted from #2

  • Start Time: 2022-01-25T11:14:02.229+0000

  • Duration: 59 min 14 sec

  • Commit: 69cbc3e

Test stats 🧪

Test Results
Failed 0
Passed 151
Skipped 0
Total 151

Steps errors 17

Expand to view the steps failures

Show only the first 10 steps failures

Read yaml from files in the workspace or text.
  • Took 0 min 1 sec . View more details here
  • Description: /var/lib/jenkins/workspace/PR-2053-1-e40a1771-2214-4ff2-a0f9-f880682b9340/fleet_elastic_pkg-sshhosts
Read yaml from files in the workspace or text.
  • Took 0 min 0 sec . View more details here
  • Description: /var/lib/jenkins/workspace/PR-2053-1-c7ac3177-3f34-4069-aa6a-f187e2a7d702/fleet_arm64-sshhosts
Shell Script
  • Took 0 min 2 sec . View more details here
  • Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2053-1-96eba97a-b7d8-46c3-9136-8a76c9223b09/e2essh [email protected] -- 'sudo chown admin -R /home/admin/e2e-testing/outputs '
Shell Script
  • Took 0 min 2 sec . View more details here
  • Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2053-1-120e5e8f-68f4-4101-a536-9ebc01c46c5c/e2essh [email protected] -- 'sudo chown admin -R /home/admin/e2e-testing/outputs '
Read yaml from files in the workspace or text.
  • Took 0 min 1 sec . View more details here
  • Description: /var/lib/jenkins/workspace/PR-2053-1-b5acd9a9-af75-4312-81fd-ec9d5e5d33fe/fleet_amd64-sshhosts
Read yaml from files in the workspace or text.
  • Took 0 min 1 sec . View more details here
  • Description: /var/lib/jenkins/workspace/PR-2053-1-42c7fd8d-9c4d-4702-9e87-43a6cb5e474a/fleet_arm64-sshhosts
Read yaml from files in the workspace or text.
  • Took 0 min 1 sec . View more details here
  • Description: /var/lib/jenkins/workspace/PR-2053-1-7fdb5309-90ea-4fe6-a7a3-e8616dec18b8/fleet_amd64-sshhosts
Read yaml from files in the workspace or text.
  • Took 0 min 1 sec . View more details here
  • Description: /var/lib/jenkins/workspace/PR-2053-1-8cf0a6da-be32-45b0-9f32-60f9feb16438/kubernetes_autodiscover-sshhosts
Read yaml from files in the workspace or text.
  • Took 0 min 1 sec . View more details here
  • Description: /var/lib/jenkins/workspace/PR-2053-1-4e8d2cc5-0dc3-4b91-8a5a-552663a2cdb8/kubernetes_autodiscover-sshhosts
Read yaml from files in the workspace or text.
  • Took 0 min 1 sec . View more details here
  • Description: /var/lib/jenkins/workspace/PR-2053-1-0c1103e2-41b3-40f9-91c5-4c196a14ff7d/kubernetes_autodiscover-sshhosts

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link
Contributor

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-01-25T11:30:02.391+0000

  • Duration: 46 min 11 sec

  • Commit: 62f3c0e

Test stats 🧪

Test Results
Failed 44
Passed 173
Skipped 0
Total 217

Test errors 44

Expand to view the tests failures

> Show only the first 10 test failures

Initializing / End-To-End Tests / fleet_amd64_linux_integration / Adding the Linux Integration to an Agent ... – Linux Integration
    Expand to view the error details

     Step the agent is listed in Fleet as "online"

  • no stacktrace
Initializing / End-To-End Tests / fleet_arm64_linux_integration / Adding the Linux Integration to an Agent ... – Linux Integration
    Expand to view the error details

     Step the agent is listed in Fleet as "online"

  • no stacktrace
Initializing / End-To-End Tests / fleet_amd64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of filebeat #1 – Running on top of Beats
    Expand to view the error details

     Step the "elastic-agent" process is in the "started" state on the host

  • no stacktrace
Initializing / End-To-End Tests / fleet_amd64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of metricbeat #1 – Running on top of Beats
    Expand to view the error details

     Step the "elastic-agent" process is in the "started" state on the host

  • no stacktrace
Initializing / End-To-End Tests / fleet_amd64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of filebeat #2 – Running on top of Beats
    Expand to view the error details

     Step the "elastic-agent" process is in the "started" state on the host

  • no stacktrace
Initializing / End-To-End Tests / fleet_amd64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of metricbeat #2 – Running on top of Beats
    Expand to view the error details

     Step the "elastic-agent" process is in the "started" state on the host

  • no stacktrace
Initializing / End-To-End Tests / fleet_arm64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of filebeat #1 – Running on top of Beats
    Expand to view the error details

     Step the "elastic-agent" process is in the "started" state on the host

  • no stacktrace
Initializing / End-To-End Tests / fleet_arm64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of metricbeat #1 – Running on top of Beats
    Expand to view the error details

     Step the "elastic-agent" process is in the "started" state on the host

  • no stacktrace
Initializing / End-To-End Tests / fleet_arm64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of filebeat #2 – Running on top of Beats
    Expand to view the error details

     Step the "elastic-agent" process is in the "started" state on the host

  • no stacktrace
Initializing / End-To-End Tests / fleet_arm64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of metricbeat #2 – Running on top of Beats
    Expand to view the error details

     Step the "elastic-agent" process is in the "started" state on the host

  • no stacktrace

Steps errors 20

Expand to view the steps failures

Show only the first 10 steps failures

Shell Script
  • Took 12 min 19 sec . View more details here
  • Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2053-2-2ea3c23d-d6aa-436b-a5ce-c48deb974c6a/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "backend_processes && ~@nightly && ~@skip:arm64" '
Archive the artifacts
  • Took 0 min 0 sec . View more details here
  • Description: [2022-01-25T12:01:06.131Z] Archiving artifacts script returned exit code 2
Shell Script
  • Took 11 min 12 sec . View more details here
  • Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2053-2-c684338d-e0e7-47e0-ad3b-fd8cf803e864/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "backend_processes && ~@nightly && ~@skip:amd64" '
Archive the artifacts
  • Took 0 min 0 sec . View more details here
  • Description: [2022-01-25T12:00:18.777Z] Archiving artifacts script returned exit code 2
Shell Script
  • Took 8 min 35 sec . View more details here
  • Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2053-2-a7d667ce-eab4-49e3-8c0f-6877fa85fd91/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "running_on_beats && ~@nightly && ~@skip:arm64" '
Archive the artifacts
  • Took 0 min 0 sec . View more details here
  • Description: [2022-01-25T11:56:33.138Z] Archiving artifacts script returned exit code 2
Shell Script
  • Took 6 min 29 sec . View more details here
  • Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2053-2-b42c5d8a-2b8f-4a74-8bca-abc8a6e10442/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "running_on_beats && ~@nightly && ~@skip:amd64" '
Archive the artifacts
  • Took 0 min 0 sec . View more details here
  • Description: [2022-01-25T11:55:56.526Z] Archiving artifacts script returned exit code 2
Shell Script
  • Took 27 min 15 sec . View more details here
  • Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2053-2-6a50c12f-12d2-464b-a135-a7b275ac50a0/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "elastic-agent && ~@nightly && ~@skip:amd64" '
Shell Script
  • Took 0 min 0 sec . View more details here
  • Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2053-2-6a50c12f-12d2-464b-a135-a7b275ac50a0/e2essh [email protected] -- 'sudo chown admin -R /home/admin/e2e-testing/outputs '

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors 44

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

  • Name: Initializing / End-To-End Tests / fleet_amd64_linux_integration / Adding the Linux Integration to an Agent ... – Linux Integration
  • Name: Initializing / End-To-End Tests / fleet_arm64_linux_integration / Adding the Linux Integration to an Agent ... – Linux Integration
  • Name: Initializing / End-To-End Tests / fleet_amd64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of filebeat #1 – Running on top of Beats
  • Name: Initializing / End-To-End Tests / fleet_amd64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of metricbeat #1 – Running on top of Beats
  • Name: Initializing / End-To-End Tests / fleet_amd64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of filebeat #2 – Running on top of Beats
  • Name: Initializing / End-To-End Tests / fleet_amd64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of metricbeat #2 – Running on top of Beats
  • Name: Initializing / End-To-End Tests / fleet_arm64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of filebeat #1 – Running on top of Beats
  • Name: Initializing / End-To-End Tests / fleet_arm64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of metricbeat #1 – Running on top of Beats
  • Name: Initializing / End-To-End Tests / fleet_arm64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of filebeat #2 – Running on top of Beats
  • Name: Initializing / End-To-End Tests / fleet_arm64_running_on_beats / Deploying the Elastic-Agent with enroll and then run on top of metricbeat #2 – Running on top of Beats
  • Name: Initializing / End-To-End Tests / fleet_amd64_fleet_mode_agent / Deploying the agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_amd64_fleet_mode_agent / Restarting the installed agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_amd64_fleet_mode_agent / Un-enrolling the agent deactivates the agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_amd64_fleet_mode_agent / Re-enrolling the agent activates the agent in Fleet – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_amd64_fleet_mode_agent / Revoking the enrollment token for the agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_amd64_fleet_mode_agent / Un-installing the installed agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_arm64_fleet_mode_agent / Deploying the agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_arm64_fleet_mode_agent / Restarting the installed agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_arm64_fleet_mode_agent / Un-enrolling the agent deactivates the agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_arm64_fleet_mode_agent / Re-enrolling the agent activates the agent in Fleet – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_arm64_fleet_mode_agent / Revoking the enrollment token for the agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_arm64_fleet_mode_agent / Un-installing the installed agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_sles15_fleet_mode_agent / Deploying the agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_sles15_fleet_mode_agent / Restarting the installed agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_sles15_fleet_mode_agent / Un-enrolling the agent deactivates the agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_sles15_fleet_mode_agent / Re-enrolling the agent activates the agent in Fleet – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_sles15_fleet_mode_agent / Revoking the enrollment token for the agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_sles15_fleet_mode_agent / Un-installing the installed agent – Fleet Mode Agent
  • Name: Initializing / End-To-End Tests / fleet_amd64_backend_processes / Deploying the agent – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_amd64_backend_processes / Stopping the agent stops backend processes – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_amd64_backend_processes / Restarting the installed agent – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_amd64_backend_processes / Un-enrolling the agent stops backend processes – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_amd64_backend_processes / Re-enrolling the agent starts the elastic-agent process – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_amd64_backend_processes / Un-installing the installed agent – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_amd64_backend_processes / Un-enrolling Elastic Agent stops Elastic Endpoint – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_amd64_backend_processes / Removing Endpoint from Agent policy stops the connected Endpoint – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_arm64_backend_processes / Deploying the agent – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_arm64_backend_processes / Stopping the agent stops backend processes – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_arm64_backend_processes / Restarting the installed agent – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_arm64_backend_processes / Un-enrolling the agent stops backend processes – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_arm64_backend_processes / Re-enrolling the agent starts the elastic-agent process – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_arm64_backend_processes / Un-installing the installed agent – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_arm64_backend_processes / Un-enrolling Elastic Agent stops Elastic Endpoint – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_arm64_backend_processes / Removing Endpoint from Agent policy stops the connected Endpoint – Backend Processes

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

mdelapenya added a commit to mdelapenya/e2e-testing that referenced this pull request Jan 26, 2022
@mdelapenya
Merge branch 'main' into 1781-rename-to-aarch64
7ecd99f 
* main: (45 commits)
  feat: add CentOS 8 support (elastic#2034)
  fix: set default region for AWS cli (elastic#2053)
  chore: use Ansible's built-in replace instead of sed (elastic#2048)
  chore: split stack configuration and start into two tasks (elastic#2044)
  feat: enable SSH access to users for debugging cloud instances (elastic#2001)
  fix: use the right branch for 7.17 backports (elastic#2025)
  SLES15 enablement (elastic#2007)
  chore: bump stale agent for main (elastic#2014)
  Update `fetchBeatsBinary` to be reused in elastic-agent-poc (elastic#1984)
  chore: add resiliency when provisioning the stack (elastic#1990)
  chore: bump elastic-package to v0.32.1 (elastic#1959)
  feat: export Fetch&Download methods in the /pkg directory (elastic#1943)
  bump stack version 8.1.0-dbc834fd (elastic#1948)
  bump stack version 8.1.0-76902d39 (elastic#1946)
  chore: retire 7.15 adding 7.17 (elastic#1938)
  ci: use withAPMEnv (elastic#1917)
  Update main branch (elastic#1928)
  bump stack version 8.1.0-befff95a (elastic#1929)
  chore: properly evaluate how tests are skipped on CI when checking modified files (elastic#1924)
  bump stack version 8.1.0-60bffc32 (elastic#1921)
  ...
@mdelapenya mdelapenya deleted the fix-with-aws branch March 9, 2022 06:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@v1v v1v v1v approved these changes

Assignees

@mdelapenya mdelapenya

Labels
backport-skip Skip notification from the automated backport with mergify
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@mdelapenya @elasticmachine @v1v