V20 GCloud Update Failed | Error Unclear

[DanAntonielli]

I have a couple of instances that are failing to upgrade to v20. Can someone help me understand what the error might be?

This has all been looked at: https://www.3cx.com/blog/releases/v20-beta1-upgrade/

 

[richiewhite]

Probably shouldn't be posting your full log in the thread, but I've seen this before.

It looks to me as though you have repos in your sources that you don't want, only repo.3cx.com should be used. Debian backports has been fully depreciated, and the google repos are also causing conflicts.

The upgrade script depends on a package called "jq" which isn't installed.

E: The repository 'http://deb.debian.org/debian buster-backports Release' no longer has a Release file.
W: Conflicting distribution: http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-buster InRelease (expected google-cloud-packages-archive-keyring-buster but got google-cloud-packages-archive-keyring-buster-stable)
/tmp/update.sh: line 55: jq: command not found
[33m====== [14:38:31] Upgrade Result: *******************************************[39m
/tmp/update.sh: line 62: jq: command not found
/bin/cat: write error: Broken pipe
[31m[14:38] Upgrade: Package Update Failed - 0[39m

Officially what you're probably going to want to do is take a backup, install a fresh V20 and restore from that backup.

Another potential solution if you're a little more confident would be to remove the debian backports and google repos from your sources list, add the debian main repo, install jq via apt, then remove the debian main repo again. Once your install has the offically supported repos and that one package it should upgrade. If you don't know what you're doing, DON'T DO THIS