Software Factory 3.8 Zuul/Nodepool Update

# Install this specific sf-config package
yum install https://softwarefactory-project.io/repos/sf-config-3.8.8.16.gc8a3619-4.el7.noarch.rpm

# Ensure to deactivate the automatic restart of Zuul and Nodepool
echo "disable_zuul_autorestart: true" >> /etc/software-factory/custom-vars.yaml
echo "disable_nodepool_autorestart: true" >> /etc/software-factory/custom-vars.yaml

# A Zuul SQL database migration need to be performed by Zuul at startup and we have noticed
# an issue with our DBs content that prevent the migration to success.
#
# First check for the issue
grep mysql_root_password /var/lib/software-factory/bootstrap-data/secrets.yaml
podman exec -it mysql mysql -uroot -p<mysql_root_password>
MariaDB> use zuul;
MariaDB [zuul]> select id, oldrev, newrev, patchset from zuul_buildset where (CHAR_LENGTH(oldrev) > 40 OR CHAR_LENGTH(newrev) > 40 OR CHAR_LENGTH(patchset) > 40);
# Important ! -> Update or remove buildset entries that are returned by that command. The new schema cannot handle oldrev, newrev or patchset values that exceed 40 chars long.

# Then run the sf-config upgrade command
sf-config --upgrade

# Stop all Zuul services (adapt the command if services are running on multiple nodes)
systemctl stop zuul-scheduler zuul-merger zuul-web zuul-executor

# Now start the zuul-scheduler and ensure that the database migration has been performed without issue.
systemctl start zuul-scheduler
tail -f /var/log/zuul/scheduler.log

# Then restart all Zuul and Nodepool services (adapt the command if services are running on multiple nodes)
systemctl start zuul-merger zuul-web zuul-executor
systemctl restart nodepool-launcher nodepool-builder