You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2023. It is now read-only.
I'm getting "AnsibleUndefinedVariable: list object has no element 1" when trying to freshly provision the VM. This is happening in the dashboard copy task, and I'm guessing it's the use of "ansible_all_ipv4_addresses[1]". Switching this to "ansible_all_ipv4_addresses[0]" appears to solve the problem. Did ansible switch how they index arrays?
The text was updated successfully, but these errors were encountered:
And... now it seems to work just fine with "ansible_all_ipv4_addresses[1]". Must have been some issue with vagrant-auto_network. Not sure why it would suddenly be ok now.
FWIW, I did encounter this too, on a Win7 install with cmder using the latest (3c3dd93) on ansible 2.2. Changing the Dashboard template as per @rwohleb suggestion fixed the problem.
I also experienced this today on my rebuilt Mac so just installed everything fresh this last week and hit this issue. Changing "ansible_all_ipv4_addresses[1]" to "ansible_all_ipv4_addresses[0]" does fix this.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Type
Your Environment
Your OS
Full console output
https://gist.github.com/rwohleb/5abb678a3da4dc83622c4f3ef7a662b9
Summary
I'm getting "AnsibleUndefinedVariable: list object has no element 1" when trying to freshly provision the VM. This is happening in the dashboard copy task, and I'm guessing it's the use of "ansible_all_ipv4_addresses[1]". Switching this to "ansible_all_ipv4_addresses[0]" appears to solve the problem. Did ansible switch how they index arrays?
The text was updated successfully, but these errors were encountered: