-
Notifications
You must be signed in to change notification settings - Fork 5
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 test doesn't work #4
Comments
Downgrading Ansible to 2.8.7 fixed the issue. |
We've updated the httpapi plugin to adjust for a connection change that was introduced in 2.9. It's on our FNDN repo for now, and is currently in PR. |
Hello @ftntcorecse |
@awuetz The PR has been approved -- it will be in version 2.10 when it is released. If you're so inclined you can also pick it up off the devel branch of the Ansible repo itself. |
After searching for some hours and not finding a single hint about what might be wrong I hope I get help here.
OS: Ubuntu 19.10
Ansible 2.9.0 installed via official PPA
FortiManager installed on KVM locally in a NATed network
JSON RPC access is enabled for the admin user
Wireshark shows that Ansible isn't even trying to connect
Setting python2 or python3 didn't change anything but the deprecation warning, the error message from the module remains the same.
And finally here the error message:
Thanks!
The text was updated successfully, but these errors were encountered: