Running with sudo says "SSH password was requested, but none specified" #434
Comments
|
This line in the log output, YAML-ified for readability:: Does that I checked with Mitogen 0.2.2, and I see this in the log: YAML-ified: Looks identical except for |
|
Apologies for the insane delay on this! Would it be possible to capture the run with Of particular interest is whether SSH is logging debug about trying to use its authentication socket |
|
Sure thing, attaching a log of that here. I see some
in there -- is that what you're looking for? |
Yes, it absolutely does :) Apologies, slightly swamped in these and it's making me miss obvious stuff! Adding a bunch of tests, its clear it only happens for delegate_to. The root cause appears to be the overzealous reworking in 3d58832, it introduced a completely different way to load configs for delegate_to hosts. |
This refactors connection.py to pull the two huge dict-building functions out into new transport_transport_config.PlayContextSpec and MitogenViaSpec classes, leaving a lot more room to breath in both files to figure out exactly how connection configuration should work. The changes made in 1f21a30 / 3d58832 are updated or completely removed, the original change was misguided, in a bid to fix connection delegation taking variables from the wrong place when delegate_to was active. The Python path no longer defaults to '/usr/bin/python', this does not appear to be Ansible's normal behaviour. This has changed several times, so it may have to change again, and it may cause breakage after release. Connection delegation respects the c.DEFAULT_REMOTE_USER whereas the previous version simply tried to fetch whatever was in the 'ansible_user' hostvar. Many more connection delegation variables closer match vanilla's handling, but this still requires more work. Some of the variables need access to the command line, and upstream are in the process of changing all that stuff around.
* origin/dmw: issue #404: add to Changelog. issue #251: readd to Changelog. tests: add exact test for issue 251; closes #251. issue #412: pad out debugging docs, add get_stack to changelog. issue #412: force-verbose output for mitogen_get_stack. issue #412: promote "mitogen_get_stack" to the main extension. issue #412: add docstrings/boilerplate to transport_config.py. issue #251, #412, #434: fix connection configuration brainwrong issue #434: tests: set a default remote_user in ansible.cfg. tests: CI should symlink all contents of ansible/hosts/ ansible: fix test failure during process exit. tests: use assert_equal in more places. tests: make assert_equal work on newer Ansibles. tests: convert stack_construction.yml to assert_equal. tests: make fork_histogram optional tests: use assert_equal in delegate_to_template.yml. tests: import assert_equal action. tests: rename 'delegation/' to 'connection_delegation/' core: replace ancient YOLO loop in fire(). tests: some more utility function tests + flake8. tests: clean up / deduplicate Ansible inventory. tests: add some more helper function tests.
|
Hi Josh, sorry for the huge delay on this. I believe the work done in #412 covers your issue too, and the tests have been updated to set a non-default ansible_user cfg variable to catch a recurrence. Thanks a million! 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! |
When we run Ansible with
sudoon the control host, to run as a different user, we get this error:This happens with Mitogen 0.2.3, and the latest master version from Git (df3a418 right now), and does not happen with Mitogen 0.2.2. Amazon Linux 18.03 and Python 2.7.14 on both control and target hosts.
-vvvoutput:Config changes:
The text was updated successfully, but these errors were encountered: