action #50951
closed
Enable transactional updates on all o3 workers again once OBS published the most recent os-autoinst version
Added by nicksinger almost 5 years ago.
Updated over 4 years ago.
Description
Due to the deployment of https://progress.opensuse.org/issues/35395 we need to make sure https://github.com/os-autoinst/os-autoinst/pull/1075 (API breaking) is deployed on both o3 and OSD. Since OBS did still not publish the build RPMs after >3h we had to disable the automatic updates on all o3 workers (imagetester, aarch64, openqaworker1, openqaworker4).
This ticket exists to make sure we don't forget to enable the transactional timers again once everything is deployed/merged.
Please ping @Martchus or @nsinger in #opensuse-factory before you touch anything in that regard on these systems or in case of further questions.
- Copied to action #51410: Enable automatic test deployment on o3 again once it is deployed with the newest os-autoinst package added
- Copied to deleted (action #51410: Enable automatic test deployment on o3 again once it is deployed with the newest os-autoinst package )
- Related to action #51410: Enable automatic test deployment on o3 again once it is deployed with the newest os-autoinst package added
- Status changed from Blocked to Resolved
- Assignee set to nicksinger
the openQA-worker packages where updated on the 4 worker hosts. Therefore we could enable the transactional-update.timer again. systemctl list-timers currently shows:
Tue 2019-05-21 01:19:16 CEST 7h left n/a n/a transactional-update.timer transactional-update.service
- Subject changed from Enable tranactional updates on all o3 workers again once OBS published the most recent os-autoinst version to Enable transactional updates on all o3 workers again once OBS published the most recent os-autoinst version
Also available in: Atom
PDF