Skip to content
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

ansible_default_ipv4.address cant detect public ip for build-scaleway-ubuntu1604-armv7-1 and -2 #1994

Closed
Haroon-Khel opened this issue Mar 2, 2021 · 3 comments

Comments

@Haroon-Khel
Copy link
Contributor

Haroon-Khel commented Mar 2, 2021

Ansible isnt able to detect the public ip address for the machines build-scaleway-ubuntu1604-armv7-1 and -2.

On other machines, the ansible variable ansible_default_ipv4.address is equal to the public/external ip address, but for these two machines, it is equal to the private ip adresses

On -1 for example
"ansible_default_ipv4.address: 10.1.14.2",

This causes hosts_file tasks in the adopt_etc role to enter this address in /etc/hosts, causing an improper entry, causing errors such as #1907

@Haroon-Khel Haroon-Khel added this to the March 2021 milestone Mar 2, 2021
@Haroon-Khel Haroon-Khel self-assigned this Mar 2, 2021
@Haroon-Khel
Copy link
Contributor Author

Haroon-Khel commented Mar 2, 2021

ansible_ssh_host is another ansible variable for a machine's public ip. Could use this instead of ansible_default_ipv4.address, but would like to better understand why ansible isnt able to detect the public ip using ansible_default_ipv4.address

@Haroon-Khel
Copy link
Contributor Author

Haroon-Khel commented Mar 3, 2021

build and test-alibaba-ubuntu1804-armv8-1 and build-scaleway-ubuntu1604-x64-1 are experiencing the same issue

@Haroon-Khel
Copy link
Contributor Author

Closed as #1996 is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant