Closed Bug 731303 (talos-r3-fed64-023) Opened 13 years ago Closed 12 years ago

talos-r3-fed64-023 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86_64
Linux
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

References

Details

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

No description provided.
Alias: talos-r3-fed64-023
Summary: talos-r3-fed64-023 needs rebooting → talos-r3-fed64-023
Priority: -- → P3
Whiteboard: [buildduty][capacity][buildslaves]
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
It seems it is down again.
Status: RESOLVED → REOPENED
Depends on: 731996
Resolution: FIXED → ---
Summary: talos-r3-fed64-023 → talos-r3-fed64-023 problem tracking
back up
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 740493
OS: Mac OS X → Linux
Hardware: x86 → x86_64
Resolution: FIXED → ---
Depends on: 740798
No longer depends on: 740798
Depends on: 744575
No longer depends on: 731291, 731996, 740493
Depends on: 745308
No longer depends on: 744575
no vga sig | rebooted
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
The screensaver is enabled (https://tbpl.mozilla.org/php/getParsedLog.php?id=11279131&tree=Mozilla-Inbound#error0 - "XScreenSaver state: Off"), which breaks several hundred tests when it becomes On, and "XScreenSaver will activate after another 0 seconds idle time" there it goes.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
disabled in slavealloc
This slave hasn't being doing puppet since at least April 17: Apr 17 09:28:16 talos-r3-fed64-023 puppetd[1992]: Lock file /var/lib/puppet/state/puppetdlock exists; skipping catalog run And the clock jumped back to 2001, probably sometime after Apr 22 01:25:23. /var/log/messages* aren't clear with the time discontinuity. But with puppet fixed up there's nothing much to do, some tweaks to ntp and networking and installing node. Our options now are reimaging, or crossing our fingers and putting it back in prod.
Depends on: 750257
Let's reimage and be hopefully "safer".
Back in production.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 789584
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 13 years ago → 12 years ago
Resolution: --- → FIXED
No longer depends on: 789584
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: armenzg
Needs a reboot.
Status: RESOLVED → REOPENED
Depends on: 806246
Resolution: FIXED → ---
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Needs a reboot.
Status: RESOLVED → REOPENED
Depends on: 822903
Resolution: FIXED → ---
Producing green jobs.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.