m5 master (db1183) needs to be rebooted. Move db1176 to m5.
Description
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| mariadb: Move db1176 to m5 | operations/puppet | production | +6 -6 | |
| db1176: Disable notifications | operations/puppet | production | +1 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Restricted Task | |||||
| Restricted Task | |||||
| Resolved | Marostegui | T329478 Move db1176 to m5 |
Event Timeline
This host can be moved to m5, but it should not take over the master until the maintenance on row A eqiad is done (T329073 - 7th March)
Change 888987 had a related patch set uploaded (by Marostegui; author: Marostegui):
[operations/puppet@production] db1176: Disable notifications
Change 888987 merged by Marostegui:
[operations/puppet@production] db1176: Disable notifications
Mentioned in SAL (#wikimedia-operations) [2023-03-01T09:57:56Z] <marostegui> Stop db1117:3325 and db1176 T329478
Change 893408 had a related patch set uploaded (by Marostegui; author: Marostegui):
[operations/puppet@production] mariadb: Move db1176 to m5
Change 893408 merged by Marostegui:
[operations/puppet@production] mariadb: Move db1176 to m5
This is done - the switchover will be tracked at T330847: Switchover m5 master (db1183 -> db1176)