Closed madwort closed 2 months ago
We could try editing /etc/cloud/cloud.cfg
to remove the hosts updater from the list. Or we could keep the template file up to date in our install script. Maybe to discuss with @bloodearnest when he's back from hols.
Given that I think we have only rebooted this twice in 18mo, I don't think it's hugely urgent.
The TPP server was rebooted in https://github.com/opensafely-core/sysadmin/issues/168.
After the reboot the contents of
/etc/hosts
of the ubuntu VM were identical to the current contents of/etc/cloud/templates/hosts.debian.tmpl
- which meant that it contained an entry for github-proxy.opensafely.org but not the expected## opensafely core hosts
block that we believe was there before the reboot. This meant that Airlock returned an error 500 on attempted login as it could not communicate with (firstly) collector.opensafely.org & (secondly) jobs.opensafely.orgRunning
just install
in/srv/backend-server
fixed the issue, but we assume this will happen again if the system is rebooted.see also previous ticket and current state of install script
In particular this line suggests that
/etc/hosts
should not be overwritten (and is possibly also the default behaviour!?), so we should probably check out what's going wrong here.