-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Solaris hosts can't be pinged #13410
Comments
Changing to next as the code we think is causing this is only in devel, not in stable-2.0 |
Confirmed that it works in stable-2.0:
|
Turning off pipelining gives a different error:
|
@fboender could you please post the full output of |
With pipelining enabled again:
|
Reverting the commit in devel for now as @amenonsen will be busy for a few days and others are busy with the 2.0 release. I'll leave this open for now as we'll want to remerge once the problems with the code are fixed. |
The latest develop branch is now working again with Solaris 10.1:
|
Also confirmed to work with both pipelining enabled and disabled. |
No no, devel isn't what you should be testing. I'm afraid you will need to apply the change from PR #13487 on top of devel and test that. devel works only because the pipelining+requiretty change was reverted. The new change has not yet been merged into devel. |
Whoops, sorry, didn't read it properly. Just to make sure I'm doing this right: I applied the PR
Ran ansible:
Checked against stable-2.0 to see if it's a problem with my setup:
Output of verbose:
If I manually run the listed SSH command:
If I remove the remote argument (everything from
Again with ANSIBLE_DEBUG=1:
|
At 2015-12-10 00:51:04 -0800, notifications@github.com wrote:
(This is normal. The entire command is passed as a single string to Looking at the command that is being executed:
I notice it says 'python' in one place and '/usr/bin/python' in another. -- Abhijit |
Both work:
|
There is some update in this issue? Also, there is some alternative/workaround at this moment? |
@cristianoliveira this issue should not be happening to you unless you are running the PR linked above. |
Anyone know how to avoid/fix this issue ? I also has this one when running on CentOS 6.5 and Ansible 2.0.1.0, Python 2.6.6. This issue happens some times, when the network is good, it looks like it has lower possibilities come out. |
👍 hotfix is install older version :( |
@fboender Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information. Here are the items we could not find in your description:
Please set the description of this issue with this template: |
@fboender You have not responded to information requests in this issue so we will assume it no longer affects you. If you are still interested in this, please create a new issue with the requested information. |
I'm running into an issue with the latest (commit 9bf1aaf; Wed Dec 2 12:11:16 2015) ansible code from github. When trying to ping (or really any ansible action) solaris 10 hosts, the following error is shown:
However, an older version of Ansibe (v1.9.1) works fine:
The sol.local machine is: SunOS unknown 5.10 Generic_147148-26 i86pc i386 i86pc (python v 2.6.4)
Output of -vvvvv:
Output of only the 'ssh' part without running any remote commands:
So it doesn't seem to be a connection problem.
This part may help (some output removed for brevity; I can provide a full dump):
Details:
Ansible version:
Host / Master OS: Linux Mint 17 Qiana (Ubuntu 14.04) with Python 2.7.6
Guest OS: SunOS unknown 5.10 Generic_147148-26 i86pc i386 i86pc with python v2.6.4
The text was updated successfully, but these errors were encountered: