There is no need for a zuul-merger on contint1001, we already have one on scandium.eqiad.wmnet. To ease migration from gallium to contint1001, lets remove the zuul-merger on gallium.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
contint: remove zuul-merger from gallium | operations/puppet | production | +7 -8 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Declined | None | T133150 Move gallium to an internal host? | |||
Declined | None | T137358 Migrate CI services from gallium to contint1001 | |||
Resolved | hashar | T137418 Remove zuul-merger from gallium |
Event Timeline
Change 293501 had a related patch set uploaded (by Hashar):
contint: remove zuul-merger from gallium
Mentioned in SAL [2016-06-09T14:33:00Z] <hashar> stopped / disabled zuul-merger on gallium T137418
Puppet ran just fine, and the iptables rules looks ok. I have manually cleaned up the host:
update-rc.d zuul-merger disable
And deleted zuul-merger related files from /etc using the puppet compiler to track them.
Dropped:
- /srv/ssd/zuul/git
- /var/log/zuul/merger*
All that with assistance of @Muehlenhoff :)
Mentioned in SAL [2016-06-09T15:22:15Z] <hashar> Cleaning git-daemon on gallium (was used by zuul-merger) T137418
Mentioned in SAL [2016-06-14T09:04:27Z] <hashar> gallium: manually removing cron entry zuul_repack from user zuul. Causes cron spam due to zuul merger no more being on gallium T137418
zuul@gallium.wikimedia still had a cron entry:
# Puppet Name: zuul_repack PATH=/usr/bin:/bin:/usr/sbin:/sbin 7 4 * * * MAILTO='jenkins-bot@wikimedia.org' find /srv/ssd/zuul/git -maxdepth 3 -type d -name '.git' -exec git --git-dir='{}' pack-refs --all \;
Which caused cron spam:
find: `/srv/ssd/zuul/git': No such file or directory