Closed
Bug 1477624
Opened 7 years ago
Closed 6 years ago
[MDC1] T-W1064-MS-065 disk space CRITCAL 0% free after re-image
Categories
(Infrastructure & Operations :: RelOps: Hardware, task)
Infrastructure & Operations
RelOps: Hardware
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: zfay, Assigned: markco)
References
Details
Attachments
(1 file)
|
62.30 KB,
image/png
|
Details |
The machine has been problematic for some time. Apparently its HDD is full and this prevents generic worker from starting.
| Reporter | ||
Updated•7 years ago
|
Summary: [MDC1] T-W1064-MS-065 disk space CRITCAL 0% free → [MDC1] T-W1064-MS-065 disk space CRITCAL 0% free after re-image
| Reporter | ||
Comment 1•7 years ago
|
||
The problem is still persisting. I'm guessing this needs to be physically checked. What do you think :markco?
Flags: needinfo?(mcornmesser)
| Assignee | ||
Comment 2•7 years ago
|
||
It appears this was missed in the reimaging process after the multiple hard drives configuration was rolled back. Kicked off a new image.
Flags: needinfo?(mcornmesser)
| Reporter | ||
Comment 3•7 years ago
|
||
It's last logs are still from Aug 22 about:
Aug 22 10:53:14 T-W1064-MS-072.mdc1.mozilla.com OpenCloudConfig: Current available disk space CRITCAL 0% free. Will not start Generic-Worker!#015
Attempted to re-image the worker and got the attached picture few minutes after kicking of the re-image. What should we do next?
Flags: needinfo?(mcornmesser)
| Assignee | ||
Comment 4•7 years ago
|
||
I have added a disk partition clean up step to the task sequence to address this issue. https://bugzilla.mozilla.org/show_bug.cgi?id=1485840
Flags: needinfo?(mcornmesser)
Updated•7 years ago
|
Assignee: relops → nobody
Component: RelOps: General → RelOps: Hardware
QA Contact: klibby
Updated•6 years ago
|
Assignee: nobody → mcornmesser
| Assignee | ||
Comment 5•6 years ago
|
||
It looks fine.
https://tools.taskcluster.net/provisioners/releng-hardware/worker-types/gecko-t-win10-64-hw/workers/mdc1/T-W1064-MS-065
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•