Fix firewall playbook example to not break connection to ansible-1 #2140
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes connection error to ansible-1 due to firewalld being installed and started without proper configuration. Added when conditional to run all the firewall tasks only on the web group.
Update example playbook output to reflect playbook changes
|
Credit to @xmtrcv for identifying the fix |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
The playbook example for setting up the firewall in section 1.5 would install and enable firewalld on ansible-1 but then not configure it. This resulted in a connection error when trying to access the controller UI and VS Code. To fix this, when conditionals were added to only run the firewall related tasks against hosts in the web group.
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION
If the playbook with the code issue is run it breaks the web connection to the controller (ansible-1). SSH will continue to work allowing the connection to be restored by running
sudo systemctl stop firewalldon ansible-1.