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
'dict object' has no attribute 'ansible_default_ipv4' #769
Comments
(similar error: #212, but doesnt look related) can you show at which tasks it failed. It should not look at the default_ipv4 at all with the |
|
Any progress or workaround here? This still blocks me. |
@mzylowski Please include complete ansible-playbook output and the command specified to run ansible. Also, please try this: |
Sorry for the late answer (holidays etc..) Inventory:
Deployment:
Debug:
So it looks like |
@mzylowski please try with the patch |
problem exists on ansible 2.0.0.2. with fresh ansible 2.2.0.0 that works fine. |
You need Ansible 2.1.0 or newer to use Kargo |
Provisioning node in this network was miss-configured and indeed the problem was in ansible version. After upgrading to 2.2.0 I finished my deployment. Thanks @mattymo and @theundefined, I forgot to check this simple thing in new environment, sorry.. |
@mzylowski : We are having same issue with ansible 2.3.1.0. Do you know what exactly was miss-configured during node provisioning? |
I am facing the same error with a fresh install of Ansible 2.3. But the variable is in fact set, I can confirm with the following command:
|
Be sure to check all nodes can access internet as well so they can install packages, even though you can ssh to it. |
I can't deploy simple cluster (1 master, 2 minions) via current kargo master (commit ea87489).
OS: Ubuntu 16.04
Inventory:
Errors:
@pskrzyns @bogdando @dkrzyszczyk
The text was updated successfully, but these errors were encountered: