SSH auth failure in specific case #436
Comments
Also I tried to disable ssh_pipelining and comment all ssh_args, but it didn't help. |
Can you please rerun with '-e mitogen_ssh_debug_level=3', and don't bother with -vvvv output, it is far too noisy, just '-vvv' is fine. Sorry, debugging is a bit vebose at present. Would it be possible to also include the mitogen_ssh_debug_level=.. + -vvv output for a task that succeeded? I bet the difference is somewhere in the SSH command line, or if not there, somehow the process environment is varying compared to a regular Ansible run. Thanks for reporting this! |
Thank you very much for your help, I really appreciate it!
but I'm getting error:
I guess, something wrong with command line option 'mitogen_ssh_debug_level'. |
It can be a string when specified on the command line.
Whoops, it is because there was no code to convert from string to integer. You can use |
Thank you!
I'm using ssh-key auth mechanism with ssh-agent on ansible-controller.
|
I think the problem may be with Finally, would it be possible to return Just search for "cmd: ssh" in the full log, you will find all the new SSH invocations :) Sorry for the inconvenience, and thanks again for your help |
Hello! You are absolutely right, because issue happens on first mention of delegate_to option.
|
Hi! |
You said you are authenticating with SSH agent, but in the log, it does not look like ssh is using agent authentication. SSH tries to find all common key filenames and fails, that is why authentication fails. Does the same run succeed under vanilla Ansible? It is possible that Mitogen is somehow not preserving the SSH_AUTH_SOCK environment variable, which SSH depends on. Is there anything special about your configuration? For example, are you using an Ansible plug-in to manage SSH agent |
* origin/dmw: issue #415: replace default Poller with select.poll() issue #415: add IPC latency bench. issue #408: fix test fallout. issue #408: update Changelog; closes #408. issue #408: 2.4 compat: replace iter_read with explicit generator issue #408: 2.4 compat: remove ternary if use in master.py. issue #408: use compatible method to get thread ID. issue #408: fix mitogen.compat.tokenize 2.4 compatibility. issue #436: decode debug log lines on Python 3. issue #461: Ansible 2.3 placeholder modules for action plug-ins. issue #461: Ansible 2.3-compatible _get_candidate_temp_dirs(). issue #461: Ansible 2.3 did not have _load_name.
Hello, Mitogen 0.2.3 was released with a major bug in delegate_to: handling. Your original task includes "delegate_to:", therefore it is almost certainly a manifestation of this bug. Please pull latest master - the fix will be on master in around 10 minutes. Sorry for the huge delay getting around to looking at this. This should now be fixed on the master branch and will make it into the next release. To be updated when a new release is made, subscribe to https://networkgenomics.com/mail/mitogen-announce/ If you are still experiencing the problem on the current master branch, please do not hesitate to reopen this issue. Thanks for reporting this! |
I found similar issues, but due to different environment and steps to reproduce, I decided to create another issue.
I have the following code in role:
Many steps before this one and many roles running without errors. But at step "Register facts in Consul" I'm getting "SSH authentication "
This is output with -vvvv option:
log.txt
On ansible-controller and on targets running CentOS Linux release 7.5.1804 (Core), ansible and python are:
Ansible-config dump is:
Please, help with this issue, if it's possible.
The text was updated successfully, but these errors were encountered: