Bug 814440 (talos-r3-xp-100)

talos-r3-xp-100 problem tracking

RESOLVED FIXED

Status

P3
normal
RESOLVED FIXED
6 years ago
6 months ago

People

(Reporter: kmoir, Unassigned)

Tracking

Details

(Whiteboard: [buildduty][buildslaves][capacity])

(Reporter)

Description

6 years ago
needs to be rebooted, not accessible via the network
(Reporter)

Updated

6 years ago
Depends on: 814216
(Reporter)

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Reboot needed.
Status: RESOLVED → REOPENED
Depends on: 816278
Resolution: FIXED → ---
Back action.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
Back in action, even.
Status: RESOLVED → REOPENED
Depends on: 821746
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED

Updated

6 years ago
Status: RESOLVED → REOPENED
Depends on: 823960
Resolution: FIXED → ---
Back in production.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
01:04 < nagios-releng> Tue 01:04:48 PST [493] talos-r3-xp-100.build.scl1.mozilla.com is DOWN :PING CRITICAL - Packet loss = 100%

and down again
Status: RESOLVED → REOPENED
Depends on: 834922
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED

Updated

6 years ago
Depends on: 839427
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
Time since last job: 2 days, 13:57:23
Not responding to pings
Status: RESOLVED → REOPENED
Depends on: 844993
Resolution: FIXED → ---
Back online and running jobs.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED

Updated

6 years ago
Status: RESOLVED → REOPENED
Depends on: 847472
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 851394
Resolution: FIXED → ---

Updated

6 years ago
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED

Updated

6 years ago
Status: RESOLVED → REOPENED
Depends on: 854240
Resolution: FIXED → ---

Updated

6 years ago
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 858075
Resolution: FIXED → ---
back in production
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
(Reporter)

Updated

6 years ago
Status: RESOLVED → REOPENED
Depends on: 859793
Resolution: FIXED → ---
(Reporter)

Comment 9

6 years ago
back in production
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
(Reporter)

Updated

6 years ago
Status: RESOLVED → REOPENED
Depends on: 860229
Resolution: FIXED → ---
(Reporter)

Comment 10

6 years ago
And it's done again.
Depends on: 861175
(Reporter)

Updated

6 years ago
Depends on: 861400
back in prod.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 866251
Resolution: FIXED → ---

Updated

6 years ago
Depends on: 870809
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
(Reporter)

Comment 12

5 years ago
It's been down for three days
Status: RESOLVED → REOPENED
Depends on: 884505
Resolution: FIXED → ---
In production.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago5 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering

Updated

6 months ago
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.