Closed Bug 1476179 (t-yosemite-r7-394) Opened 7 years ago Closed 6 years ago

[MDC1] t-yosemite-r7-394 problem tracking

Categories

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

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rmutter, Assigned: dragrom)

References

Details

I was trying to reimage the machines but seems like it requires root's password.
Rising the priority to P1 and marking it as a blocker, as we can't work on the machine. :dhouse can you please tickle the machine and see whats up?
Alias: t-yosemite-r7-394
Severity: normal → blocker
Depends on: 1473358
Flags: needinfo?(dhouse)
Priority: -- → P1
Summary: [MDC1]t-yosemite-r7-394 problem tracking → [MDC1] t-yosemite-r7-394 problem tracking
In build-puppet, there a note for bug 1388816 with t-yosemite-r7-394 marked as a loaner. However that bug is closed and some months old. So we can check with the owner and reclaim it if it is not being used anymore.
Depends on: 1388816
Flags: needinfo?(dhouse)
Dragos, can this machine be re-claimed or do you still need it as a loaner?
Assignee: nobody → dcrisan
Flags: needinfo?(dcrisan)
I want to use it on staging pool like 380, but if you need it to be into production you can re-claim. I don't use it at this moment
Flags: needinfo?(dcrisan)
Dragos, you can have this machine in the staging pool together with 380 if you so wish. We have plenty of machine working atm, especially as we are constantly fixing the lazy/broken ones. The OSX pool hasn't reported large pending numbers yet so we should be good.
t-yosemite-r7-394.test.releng.mdc1.mozilla.com is now part of the staging pool: https://tools.taskcluster.net/provisioners/releng-hardware/worker-types/gecko-t-osx-1010-beta
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Danut, can you update the ciduty script to know that this one is in the staging/beta pool? I have them pinned to my environment to test https://bugzilla.mozilla.org/show_bug.cgi?id=1480412
Flags: needinfo?(dlabici)
Updated. Thank you.
Flags: needinfo?(dlabici)

72: The worker is running on spot infrastructure in AWS EC2 and has been served a spot termination notice, and therefore has shut down. The following log were provided: https://papertrailapp.com/systems/t-yosemite-r7-394.test.releng.mdc1.mozilla.com/events?q=program%3Ageneric-worker

Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: 72

The worker is now in working state

Status: REOPENED → RESOLVED
Closed: 7 years ago6 years ago
Resolution: --- → FIXED
Whiteboard: 72

71: The worker was terminated via an interrupt signal (e.g. Ctrl-C pressed). The following log were provided: https://papertrailapp.com/systems/t-yosemite-r7-394.test.releng.mdc1.mozilla.com/events?q=program%3Ageneric-worker

Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: code - 71

The worker is now in working state

Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
Whiteboard: code - 71

69: Worker panic - either a worker bug, or the environment is not suitable for running a task, e.g. a file cannot be written to the file system, or something else did not work that was required in order to execute a task. See config setting shutdownMachineOnInternalError. The following log were provided: https://papertrailapp.com/systems/t-yosemite-r7-394.test.releng.mdc1.mozilla.com/events?q=program%3Ageneric-worker

Status: RESOLVED → REOPENED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Resolution: FIXED → ---
Whiteboard: code - 69
Whiteboard: code - 69

69: Worker panic - either a worker bug, or the environment is not suitable for running a task, e.g. a file cannot be written to the file system, or something else did not work that was required in order to execute a task. See config setting shutdownMachineOnInternalError. The following log were provided: https://papertrailapp.com/systems/t-yosemite-r7-394.test.releng.mdc1.mozilla.com/events?q=program%3Ageneric-worker

The worker is now in working state

Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
Whiteboard: code - 69

69: Worker panic - either a worker bug, or the environment is not suitable for running a task, e.g. a file cannot be written to the file system, or something else did not work that was required in order to execute a task. See config setting shutdownMachineOnInternalError. The following log were provided: https://papertrailapp.com/systems/t-yosemite-r7-394.test.releng.mdc1.mozilla.com/events?q=program%3Ageneric-worker

Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: code - 69

The worker is now in working state

Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
Whiteboard: code - 69
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.