-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
Fixing typos and Troubleshooting SSH in day 64 #530
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
base: main
Are you sure you want to change the base?
Conversation
|
Our team will soon review your PR. Thanks @DevITJAX :) |
|
Hello there, thanks for opening your first Pull Request. Someone will review it soon. Welcome to the #90DaysOfDevOps community! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR improves Day 64 of the 90DaysOfDevOps Ansible tutorial by fixing command case sensitivity and adding helpful troubleshooting guidance for a common SSH error encountered in lab environments.
Key Changes:
- Corrected
ansible Linux -m pingtoansible linux -m pingfor proper case consistency with Ansible inventory group naming conventions - Added troubleshooting section explaining SSH host key checking errors and providing the solution using
export ANSIBLE_HOST_KEY_CHECKING=False
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|  | ||
|
|
||
| I have now also started adding some additional hosts to our inventory, another name for this file as this is where you are going to define all of your devices, could be network devices, switches and routers for example also would be added here and grouped. In our hosts file though I have also added my credentials for accessing the Linux group of systems. | ||
| Troubleshooting: SSH Host Key Checking Error |
Copilot
AI
Dec 4, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The troubleshooting section needs proper markdown formatting:
- Add a blank line between line 60 and the new section
- Format the title as a heading (e.g.,
### Troubleshooting: SSH Host Key Checking Error)
This will ensure consistency with the rest of the document structure and improve readability.
| Troubleshooting: SSH Host Key Checking Error | |
| ### Troubleshooting: SSH Host Key Checking Error |
| Troubleshooting: SSH Host Key Checking Error | ||
| If Ansible fails to connect and you see an error like: | ||
|
|
||
| `Using a SSH password instead of a key is not possible because Host Key checking is enabled and sshpass does not support this. |
Copilot
AI
Dec 4, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Grammar error: "a SSH" should be "an SSH" since SSH is pronounced with a vowel sound (ess-ess-aitch).
| `Using a SSH password instead of a key is not possible because Host Key checking is enabled and sshpass does not support this. | |
| `Using an SSH password instead of a key is not possible because Host Key checking is enabled and sshpass does not support this. |
This PR fixes a small typo in Day 64 of the 90DaysOfDevOps Ansible section.
Changes:
Corrected the command
ansible Linux -m pingtoansible linux -m pinguse
[linux], so the command needed correction.Added a troubleshooting section explaining the SSH host key checking error:
"Using a SSH password instead of a key is not possible because Host Key checking is enabled…"
export ANSIBLE_HOST_KEY_CHECKING=FalseReasoning:
Thank you for the great learning material happy to contribute!