That's actually side-tracking development each time we re-encounter it.
Instead of proper internal.admin.swh.network (or .staging.):
root@rp1:~# puppet facts | grep fqdn
"fqdn": "rp1.internal.softwareheritage.org",
"fqdn": "rp1.internal.softwareheritage.org",
"fqdn": "rp1.internal.softwareheritage.org",
"internal_fqdn": "rp1.internal.softwareheritage.org"
root@riverside:~# puppet facts | grep fqdn
"fqdn": "riverside.internal.softwareheritage.org",
"fqdn": "riverside.internal.softwareheritage.org",
"fqdn": "riverside.internal.softwareheritage.org",
"internal_fqdn": "riverside.internal.softwareheritage.org"Modifying /etc/resolv.conf fixes it partially:
root@rp1:~# cat /etc/resolv.conf
# File managed by puppet
# search internal.softwareheritage.org softwareheritage.org
search internal.admin.swh.network # respectively staging
nameserver 127.0.0.1
root@rp1:~# chattr +i /etc/resolv.conf
root@rp1:~# puppet facts | grep fqdn
"fqdn": "rp1.internal.admin.swh.network",
"fqdn": "rp1.internal.admin.swh.network",
"fqdn": "rp1.internal.admin.swh.network",
"internal_fqdn": "rp1.internal.softwareheritage.org"Note: internal_fqdn is not fixed either by this... it's used in manifest so it's
important as well
Most likely something is off somewhere in the Vagrantfile declaration.
We need to investigate and fix.