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

Stale Ansible SSH control master failures in securedrop-admin install #4364

Closed
rmol opened this issue Apr 23, 2019 · 1 comment · Fixed by #4366
Closed

Stale Ansible SSH control master failures in securedrop-admin install #4364

rmol opened this issue Apr 23, 2019 · 1 comment · Fixed by #4366

Comments

@rmol
Copy link
Contributor

rmol commented Apr 23, 2019

Description

When running securedrop-admin install, steps immediately after reboots of the servers can fail with errors like Timeout (62s) waiting for privilege escalating prompt, as Ansible's SSH control masters are stale.

This might be related to #4358, though it's not clear if all SSH failures happen after reboots.

Steps to Reproduce

I was able to reliably induce this problem with a clean install of the 0.12.2 RC, at Set sysctl flags for grsecurity, which happens immediately after a reboot.

Expected Behavior

That the Ansible playbook could still connect to the servers after they've been rebooted.

Actual Behavior

Instead, it fails as it tries to use the stale SSH control masters.

Comments

An effective fix is already used in restart-tor-carefully.yml: the Ansible control path directory is simply removed, preventing communication with the old master processes.
@rmol rmol mentioned this issue Apr 24, 2019
Merged
2 tasks
eloquence added a commit that referenced this issue Apr 25, 2019
@eloquence
Add instructions for deleting ~/.ansible/cp to work around #4364
581c6cd 
These instructions should be removed once #4364 is reliably
resolved.
@eloquence eloquence mentioned this issue Apr 25, 2019
Merged
1 task
emkll pushed a commit that referenced this issue Apr 25, 2019
@eloquence @emkll
Add instructions for deleting ~/.ansible/cp to work around #4364
8ad7dad 
These instructions should be removed once #4364 is reliably
resolved.

(cherry picked from commit 581c6cd)
emkll added a commit that referenced this issue Apr 25, 2019
@emkll
Merge pull request #4378 from freedomofpress/docs-ansible-workaround
64e6f06 
[docs] Add instructions for deleting ~/.ansible/cp to work around #4364
emkll pushed a commit that referenced this issue Apr 25, 2019
@eloquence @emkll
Add instructions for deleting ~/.ansible/cp to work around #4364
f7fbf1e 
These instructions should be removed once #4364 is reliably
resolved.

(cherry picked from commit 581c6cd)
@emkll emkll mentioned this issue Sep 12, 2019
Closed
2 tasks
kushaldas pushed a commit that referenced this issue Sep 25, 2019
@eloquence @kushaldas
Add instructions for deleting ~/.ansible/cp to work around #4364
c3a7e17 
These instructions should be removed once #4364 is reliably
resolved.
@eloquence eloquence mentioned this issue Dec 3, 2019
Closed
@sssoleileraaa
Copy link
Contributor

I ran into this a while back, see #5042 (comment)

@emkll emkll mentioned this issue Apr 14, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Clear Ansible SSH control path on reboot rmol/securedrop
2 participants
@sssoleileraaa @rmol