Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1388531
Summary: | [Errno 25] Inappropriate ioctl for device | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Juraci Paixão Kröhling <jcosta> |
Component: | ansible | Assignee: | Kevin Fenzi <kevin> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 24 | CC: | a.badger, athmanem, kevin, kupo, mark, maxim, toromoti |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ansible-2.2.0.0-3.fc24 ansible-2.2.0.0-3.fc25 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-07 23:27:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Juraci Paixão Kröhling
2016-10-25 14:58:40 UTC
Additional info: this was working fine until at least Sept 22nd. I cannot duplicate this here. What is 'pipelining' set to in your ansible.cfg ? If it's True, does changing it to false make it work? It was originally commented out and I changed it to False after seeing a post on Stackoverflow, with no effect. I just changed to True, ran the playbook again, and got the same failure. Can you run the module by itself with debug and attach that? ansible -vvvv -m cron -a 'name="backup emails" user=root special_time=daily job="/usr/bin/rsync -av /var/spool/mail/vhosts/ /mnt/backups/emails/ && touch /mnt/backups/emails/lastbackup"' hostname Not sure it's relevant, but the host is available behind a bastion host. The ssh_config is as follows: Host riacho Hostname bastion.domain.tld ForwardAgent yes ControlMaster auto ControlPersist yes ControlPath ~/.ssh/socket-%r@%h:%p Compression yes AddressFamily inet I am pretty sure this is related to your bastion host setup. If you disable the Control* options does it work? If you replace with: Host riacho HostName %h ProxyCommand ssh -q bastion.domain.tld /usr/bin/nc %h 22 Does it work? Sorry, it seems I was wrong: this host is one of the only ones where I don't have a bastion in front :) In any case, I removed pretty much all custom settings from ~/.ssh/config related to this host, leaving only the "Host" and "Hostname" parts, and I still have the problem. It's worth noting that there are steps happening before this, so, the SSH connection is successful for those steps. Logs for a successful scenario: https://paste.fedoraproject.org/466918/93517214/ Logs for a failure scenario: https://paste.fedoraproject.org/466919/47793520/ I also managed to get the `cron` python script that Ansible copies to the remote host, and ran it manually, getting the same error. Python script: https://paste.fedoraproject.org/466921/93570914/ Manual runs, with the same ioctl issue: https://paste.fedoraproject.org/466922/35952147/ Looks like this is https://github.com/ansible/ansible-modules-core/pull/4777 which should be fixed in 2.1.3 (which should be out very soon) and 2.2.0... +1, that's indeed the issue. Patching cron.py made it work. ansible-2.2.0.0-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e348c4e0e3 ansible-2.2.0.0-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-a5f9956e38 ansible-2.2.0.0-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e348c4e0e3 ansible-2.2.0.0-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-3113e71193 ansible-2.2.0.0-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-3ccb098630 ansible-2.2.0.0-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-3ccb098630 ansible-2.2.0.0-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-3113e71193 ansible-2.2.0.0-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report. ansible-2.2.0.0-3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. |