After updating to buildbot 3.9.0, the buildbot master service would not start: 2023-09-12 05:12:05-0700 [-] Starting BuildMaster -- buildbot.version: 3.9.0 2023-09-12 05:12:05-0700 [-] Loading configuration from '/var/lib/buildbot/master/gpsii/master.cfg' 2023-09-12 05:12:05-0700 [-] Setting up database with URL 'sqlite:/state.sqlite' 2023-09-12 05:12:05-0700 [-] setting database journal mode to 'wal' 2023-09-12 05:12:05-0700 [-] The Buildmaster database needs to be upgraded before this version of 2023-09-12 05:12:05-0700 [-] buildbot can run. Use the following command-line 2023-09-12 05:12:05-0700 [-] 2023-09-12 05:12:05-0700 [-] buildbot upgrade-master /var/lib/buildbot/master/gpsii 2023-09-12 05:12:05-0700 [-] 2023-09-12 05:12:05-0700 [-] to upgrade the database, and try starting the buildmaster again. You may 2023-09-12 05:12:05-0700 [-] want to make a backup of your buildmaster before doing so. 2023-09-12 05:12:05-0700 [-] BuildMaster startup failed Perhaps a scheme for automatically updating the configured services could be created? Reproducible: Always
What about something like this? We compile a list of master enabled with the following: find /etc/systemd/system/multi-user.target.wants/ -type l -name 'buildbot-master*service' | cut -d '@' -f 2 | cut -d '.' -f 1 We can then loop over that to stop the master, upgrade, and start it again. We could do something similar with workers.
Can we use systemctl commands? systemctl list-units 'buildbot-master@*.service' --all --plain --no-legend buildbot-master loaded active running Buildbot master instance I don't think anything needs to be done for the workers, but I may be wrong there. Otherwise, seems like a good plan.
Good idea. The workers need a restart, but no DB upgrade.
FEDORA-2023-36f36e6ed3 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-36f36e6ed3
FEDORA-2023-5b38626e43 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5b38626e43
FEDORA-2023-830604bbe5 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-830604bbe5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-830604bbe5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-36f36e6ed3 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-36f36e6ed3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-36f36e6ed3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-5b38626e43 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-5b38626e43` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5b38626e43 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-5b38626e43 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-36f36e6ed3 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-830604bbe5 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.