Bug 2238590
| Summary: | RFE: Upgrade databases on update | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Orion Poplawski <orion> |
| Component: | buildbot | Assignee: | Gwyn Ciesla <gwync> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | besser82, dradez, giallu, gwync, igor.raits, ngompa13, smilner, tflink |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | buildbot-3.9.2-3.fc37 buildbot-3.9.2-3.fc38 buildbot-3.9.2-3.fc39 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-10-08 02:09:12 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Orion Poplawski
2023-09-12 15:49:10 UTC
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. |