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.

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

Playbook is not running - ERROR! Cannot reset connection #39

Closed
Vad1mo opened this issue Nov 8, 2017 · 8 comments
Closed

Playbook is not running - ERROR! Cannot reset connection #39

Vad1mo opened this issue Nov 8, 2017 · 8 comments

Comments

@Vad1mo
Copy link
Contributor

Vad1mo commented Nov 8, 2017

I have difficulties applying the latest playbook from latest master. I always get a ERROR! Cannot reset connection error message. I am not able to figure out what exactly is wrong with it.

First there are this warning messages, which are not directly related to the problem I think.

TASK [ansible-dockerswarm : Kill the ansible_user active SSH connections] ********************************************************
 [WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: ansible_user is
defined and ansible_user in docker_admin_users and ansible_user in "{{ addtogroup.results | selectattr('changed') |
map(attribute='item') | list }}" and ansible_version.major <= 2 and ansible_version.minor <3

 [WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: ansible_user is
defined and ansible_user in docker_admin_users and ansible_user in "{{ addtogroup.results | selectattr('changed') |
map(attribute='item') | list }}" and ansible_version.major <= 2 and ansible_version.minor <3

skipping: [cluser-node-1]
skipping: [cluser-node-2]
 [WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: ansible_user is
defined and ansible_user in docker_admin_users and ansible_user in "{{ addtogroup.results | selectattr('changed') |
map(attribute='item') | list }}" and ansible_version.major <= 2 and ansible_version.minor <3

skipping: [cluser-node-3]
ERROR! Cannot reset connection:
Control socket connect(/Users/v/.ansible/cp/none): No such file or directory
@atosatto
Copy link
Owner

atosatto commented Nov 8, 2017

Ehi @Vad1mo, thanks for reporting this issue.
Is this still the case with the latest master release?

@Vad1mo
Copy link
Contributor Author

Vad1mo commented Nov 8, 2017

Yes its on that latest master, I force installed the latest master this morning .

ansible-galaxy install --force git+https://github.com/atosatto/ansible-dockerswarm.git,master
- changing role ansible-dockerswarm from None to master
- extracting ansible-dockerswarm to /Users/v/.ansible/roles/ansible-dockerswarm
- ansible-dockerswarm (master) was installed successfully
➜  clusteros git:(master) ✗ ansible-galaxy list
- ansible-dockerswarm, master

@Vad1mo
Copy link
Contributor Author

Vad1mo commented Nov 8, 2017

I dug bit into the topic and it is related to the PR #34

if I uncommend

# See https://stackoverflow.com/a/44753457
# - name: Reset ansible connection after group changes
#   meta: reset_connection
#   when: ansible_version.major = 2
#     and ansible_version.minor >= 3

it runs

@dsander
Copy link

dsander commented Nov 11, 2017

This seems to be an issue in ansible: ansible/ansible#27520

@atosatto
Copy link
Owner

Give me the weekend to troubleshoot it. I am sure we can find a workaround
@Vad1mo what version of Ansible are you using?

@Vad1mo
Copy link
Contributor Author

Vad1mo commented Nov 15, 2017

I am on the latest ansible 2.4.1.
Right now I just disabled/removed the feature that I don't need in a fork

@pkelleratwork
Copy link

is there any new info on this issue? thx.

atosatto added a commit that referenced this issue Dec 10, 2017
jiridudekusy pushed a commit to jiridudekusy/ansible-dockerswarm that referenced this issue May 4, 2019
atosatto added a commit that referenced this issue Nov 9, 2019
@atosatto
Copy link
Owner

atosatto commented Feb 4, 2020

I believe this has been fixed with v2.0.0.
In case you find this issue still affecting your setup, feel free to re-open it!

@atosatto atosatto closed this as completed Feb 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants