Solved Azure Linux v18 upgrade failed - suggestions

Status
Not open for further replies.

DavidA

Premier Customer
Joined
Sep 22, 2017
Messages
44
Reaction score
3
Hello,

I tried to do the upgrade on my Azure VM from v16 Ent to v18 Ent. I did backups in 3cx and VM backups in Azure. Rebooted the VM and then clicked upgrade.

It failed with this error:

[33m====== [23:25:32] Preparation: Script path is /tmp/update.sh[39m
[33m====== [23:25:32] Starting: Backup script /tmp/update.sh[39m
[33m====== [23:25:32] Starting: Current directory: /tmp[39m
[33m====== [23:25:32] Starting: Current user: root[39m
[33m====== [23:25:32] Starting: Current date: Fri Aug 13 23:25:32 -07 2021[39m
[33m====== [23:25:32] Starting: Current version: 9.11[39m
[33m====== [23:25:32] Starting: Architecture: amd64[39m
[33m====== [23:25:32] Preparation: Checking locales[39m
[33m====== [23:25:32] Preparation: Common list 3cxpbx-testing.list found but it seems to be OK[39m
[33m====== [23:25:32] Preparation: Common list 3cxpbx.list found but it seems to be OK[39m
[31m[23:25] Preparation: Found an uncommon source list in /etc/apt/sources.list.d/: microsoft-prod.list - 0[39m
::FAIL::
[33m====== [23:25:32] Failed: Output of journalctl

I am assuming the Microsoft entry is from the Call control modules from the apps we've deployed. Nothing except whats included in the packages. No 3rd party modules. I restored and tried again just for giggles with the same result. I don't see much else in the way of failures in the rest of the log.

Anything i can look into? I restored my old vm again and will use that for the time being but i want to upgrade as soon as is feasible.

thanks
 
Hi @DavidA,

Not sure why you restored your VM as in the case of "uncommon" source list the upgrade script exits at a very early stage thus not affecting your installation in any way.

For the upgrade to proceed, as the error indicates, you need to remove microsoft-prod.list source list which is under /etc/apt/sources.list.d/ directory. Once you do that, the upgrade will proceed/complete successfully. (the chance of an error occurring is very low when a system has no third party software installed - the overall success rate of the upgrade script is over 95%)

P.S: If for any reason you must restore the microsoft-prod.list souce list post-upgrade, you may do so but make sure it contains Buster repositories and not Stretch.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet