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

Add link to the users used to SSH into the Cloud EC2s #2392

Merged
merged 2 commits into from
Apr 20, 2022
Merged

Add link to the users used to SSH into the Cloud EC2s #2392

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
97d6289
add link to users used to SSH into the Cloud EC2s
AndersonQ Apr 19, 2022
f900d22
Update e2e/TROUBLESHOOTING.md
AndersonQ Apr 20, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion e2e/TROUBLESHOOTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,8 @@ Each test suite's documentation should contain the specifics to run the tests, b
### SSH into the Cloud machines
On CI, we are running the Elastic Stack and all test suites in AWS instances, so whenever a build failed we would need to access those machines and inspect the state of the machine: logs, files, containers... For that, we are enabling SSH access to those ephemeral machines, which will be kept for debugging purpose if and only if the DEVELOPER_MODE environment variable is set at the Jenkinsfile. In the UI of Jenkins, you can enable it using the DEVELOPMENT_MODE input argument, checking it to true (default is false). After the build finishes, the cloud instances won't be destroyed.

To access the machines, you must be allowed to do so first, and for that, please submit a PR adding your Github username in alphabetical order to [this file](../.ci/ansible/github-ssh-keys), keeping a blank line as file ending.
To access the machines, you must be allowed to do so first, and for that, please submit a PR adding your Github username in alphabetical order to [this file](../.ci/ansible/github-ssh-keys), keeping a blank line as file ending. The user to access each EC2 used on the tests can be found [here](https://github.com/elastic/e2e-testing/blob/main/.ci/.e2e-platforms.yaml
).

Copy link
Contributor

@mdelapenya mdelapenya Apr 19, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
An example of how to create a SSH connection can be found here:
> ssh -i ~/.ssh/YOUR_SSH_KEY.pub -vvvv admin@PUBLIC_IP_OF_THE_VM

### Tests fail because the product could not be configured or run correctly
This type of failure usually indicates that code for these tests itself needs to be changed. See the sections on how to run the tests locally in the specific test suite.
Expand Down