Closed Bug 1052108 (talos-linux64-ix-027) Opened 11 years ago Closed 10 years ago

talos-linux64-ix-027 problem tracking

Categories

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

x86_64
Linux

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: coop, Unassigned)

References

Details

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

No description provided.
reimaging...
rebooted to production
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
After two reboots, it still hasn't even managed to find a master to connect to.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Re-imaged and returned to production.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Disabled because it looks to be stuck with an old version of talos, just like with bug 1037619, so it's failing every job. If nobody needs a loan of it to investigate, maybe this time we should just reimage it and put it back in service, unlike the ones from that instance that have been out of service for two months now.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Re-imaged and returned to production.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Lost the ability to run the chromez suite without timing out. Yesterday. Shrug. Disabled.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Re-imaged and returned to service.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Failed to update talos. Disabled.
Status: RESOLVED → REOPENED
Depends on: 1141416
Resolution: FIXED → ---
Re-imaged and enabled in slavealloc. Already completed several jobs with no issues.
Status: REOPENED → RESOLVED
Closed: 11 years ago10 years ago
Resolution: --- → FIXED
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.