Closed Bug 1127433 Opened 9 years ago Closed 9 years ago

RabbitMQ Glibc patching 1/29 1p-2p Pst. downtime required

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: schan, Assigned: cliang)

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/375] )

We are able to coordinate a downtime with releng for the rabbit mq cluster.  This is happening from 10-12p. PST today.
Assignee: server-ops-webops → cliang
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/375]
Updated title to reflect new proposed time.
Summary: RabbitMQ Glibc patching 1/29 10a - 12p Pst. downtime required → RabbitMQ Glibc patching 1/29 1p-2p Pst. downtime required
this time works for releng
This will include the generic rabbitMQ cluster in PHX1 (me), the generic rabbitMQ cluster in SCL3 (me), and the Pulse rabbitMQ cluster (gozer).
All servers have been rebooted.  The main fallout of the reboot of the rabbit cluster in PHX1 was that several of the socorro processors shut down their processors; restarting the processor processes seemed to have cleared that up.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.