Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ready.check: firewall #484

Open
ghost opened this issue Jul 21, 2017 · 1 comment
Open

ready.check: firewall #484

ghost opened this issue Jul 21, 2017 · 1 comment
Labels
question

Comments

@ghost
Copy link

ghost commented Jul 21, 2017 •
edited by ghost
Loading

If a firewall is actually running on a minion, it's possible (unless appropriate minion rules are in place), that this check will simply hang and in fact give a false result.

ses3-up-1:~ # ssh root@ses3-up-2 'SuSEfirewall2 start'
ses3-up-1:~ # salt-run populate.engulf_existing_cluster
[WARNING ] Unable to find IPv6 record for "ses3-up-1.lan" causing a 10 second timeout when rendering grains. Set the dns or /etc/hosts for IPv6 to clear this.
~~~~~~HANG~~~~~~
firewall                 : disabled
apparmor                 : disabled

Which will lead to ses3-up-2 being excluded from the cluster detection/population process.
@ghost
Copy link
Author

ghost commented Jul 25, 2017

Could add a test.ping type check to ensure the nodes are up. Then, if a node is up and not responding, we can assume it's firewall is up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@swiftgist