The upgrade builders are handled by libvirt and everything runs on the bg-bbw5-x64 machine. So, the image for the

buildbot-ubuntu1804

needs to be updated.

The path to the install/upgrade script is here https://github.com/MariaDB/mariadb.org-tools/tree/master/buildbot.mariadb.org/scripts

danblack I have fixed the Deb installation script (MDBF-331) and partially fixed the minor upgrade script (MDBF-323). Thanks faust for the help. After looking into the details, I think that we should use the deb-minor-upgrade.sh for major upgrade as well. However, there still are some problems with it (full log):

Feb 04 14:38:46 ubuntu mariadbd[6381]: 2022-02-04 14:38:46 0 [ERROR] mariadbd: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure.  Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty.

Feb 04 14:38:46 ubuntu mariadbd[6381]: 2022-02-04 14:38:46 0 [ERROR] Plugin 'gssapi' init function returned error.

and

+ wget --timeout=20 --no-check-certificate https://raw.githubusercontent.com/MariaDB/mariadb.org-tools/master/buildbot/baselines/ldd.10.7.bionic.amd64 -O /tmp/ldd.baseline

--2022-02-04 14:38:57--  https://raw.githubusercontent.com/MariaDB/mariadb.org-tools/master/buildbot/baselines/ldd.10.7.bionic.amd64

Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.110.133, 185.199.109.133, 185.199.108.133, ...

Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.110.133|:443... connected.

HTTP request sent, awaiting response... 404 Not Found

If you solved any of these errors for the RPM scripts or you know what the solution is please share. Otherwise I can look more into this, or if you prefer you can do it.

gssapi, I haven't set up a kerberos service before, so this is a new one for me - https://mariadb.com/kb/en/authentication-plugin-gssapi/ doesn't have the full info for the server side.

baseline scripts appear to be dropped by the corp bb. There's only 10.5 and 10.6 recordings there. If the script can ignore the 404 and continue if not there that would be idea.

> After looking into the details, I think that we should use the deb-minor-upgrade.sh for major upgrade as well

Why is that? They both have a different starting point that might be hard to reset back from major to do a minor and vice versa. If its just a consolidation of the scripts that's ok.

The minor upgrade script installs the previously released version and assumes a clean VM. The only difference should be to specify the latest minor/major based on the case. I think this would be simplest scenario.