The upgrader-06 instance is running Buster and needs upgrading to a newer Debian release.
Description
Description
Details
Details
Title | Reference | Author | Source Branch | Dest Branch | |
---|---|---|---|---|---|
Update dependency lock file for Bookworm | repos/ci-tools/libup!25 | taavi | taavi/bookworm | master |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | • taavi | T361488 Upgrade LibUp worker to Bookworm | |||
Resolved | • taavi | T356588 Document how LibUp instances are set up (or Puppetize it) | |||
Resolved | • taavi | T361513 Not Found for url: https://gitlab.wikimedia.org/repos/releng/release/-/raw/master/make-release/settings.yaml |
Event Timeline
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2024-04-01T16:57:08Z] <taavi> stop upgrader cron on upgrader-06 to prepare for move to libup-runner08 in T361488
Comment Actions
taavi opened https://gitlab.wikimedia.org/repos/ci-tools/libup/-/merge_requests/25
Update dependency lock file for Bookworm
Comment Actions
taavi merged https://gitlab.wikimedia.org/repos/ci-tools/libup/-/merge_requests/25
Update dependency lock file for Bookworm
Comment Actions
libup-runner08 is now up based the Puppet code in the production branch. Now I'm waiting for the queues to clear on upgrader-06 before starting the services on the new instance since I'm not going to bother to try to move the RabbitMQ cluster data over. /etc/libup.toml and the private SSH key will need to be moved manually to the new instance.