[edit: I removed some stuff that had nothing to do with the issue at hand. Don’t use <? tags, folks]
Hello, I’ve run into problems re-provisioning my server.
Failed to update apt cache: W:Updating from such a repository can't be done
securely, and is therefore disabled by default., W:See apt-secure(8) manpage
for repository creation and user configuration details., E:The repository
'http://nyc2.mirrors.digitalocean.com/mariadb/repo/10.5/ubuntu bionic
Release' no longer has a Release file.
fatal: [production_host]: FAILED! => {"changed": false}
Seems like Ubuntu Bionic is out of date…
Now, I’ve looked around to see if there’s any sense in upgrading Ubuntu with ‘do-release-upgrade’ like it suggests, but I have a feeling that doing so would break everything without any hope of repair.
—
I’m running trellis-cli 1.0.0 and the recommended ansible 2.9.10
The culprit seems to be /trellis/roles/mariadb/defaults/main.yml. I removed the [arch=amd64] tag like in commit 32b1b6fcec8cb9fe14c6ec43cc1fccd3851fac2f just to see if that did anything but it didn’t.
—
Actually, so it turns out that the provisioning problem and the deploy playbook problem were unrelated. Still having issues with that mariadb mirror seemingly standing in the way of provisioning but the other stuff was just… a <? tag that should have been a <?php tag instead.
The way I managed to solve this was replacing http://nyc2.mirrors.digitalocean.com/mariadb/repo/10.5/ubuntu with https://mirror.mva-n.net/mariadb/repo/10.5/ubuntu in trellis/roles/mariadb/defaults/main.yml.
It shouldn’t be considered a long-term solution, but at least it did the trick for the time being.
The PR fixes the apt source, however, running the playbook will still terminate with an ansible error as apt is apparently updated first (task Update apt packages somewhere before task Add MariaDB PPA that fixes the apt source).
Does reprovisioning fix the issue directly on an existing Trellis system?
I had to manually remove the sources and then reprovision, as an apt upate caused ansible to fail before changing the source.
I’m not sure if this is a temporary hiccup or not, but this issue resurfaced for me this evening. I was able to get things running by using the Rackspace mirror: