Closed Bug 853634 Opened 11 years ago Closed 11 years ago

Win8 machines can get stuck on a prompt "Dirty Environment" saying that an install has not gone as expected

Categories

(Infrastructure & Operations :: RelOps: General, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: q)

References

Details

Attachments

(1 file)

I have seen a machine with this message when I VNCed into it. It had not taken jobs for a while.
I have not yet determined how this can be easily noticed without VNCing.
If I understand correctly, the machine stops taking jobs until the prompt is dealt with. I don't know why this happens.

I will file the bug to keep track for it and keep an eye on it.

I'm very sorry I did not take note of the machine. I was trying to fix the tree with dozens of machines to deal with.
Assignee: server-ops-releng → q
t-w864-ix-slave22 was found on this state.

I believe last time I just hit "OK" and let the machine take jobs.

Which seems to machine to the machine only taking one job and not anymore jobs after that:
https://secure.pub.build.mozilla.org/buildapi/recent/t-w864-ix-022
Summary: Win8 machines can get stuck on a prompt saying that an install has not gone as expected → Win8 machines can get stuck on a prompt "Dirty Environment" saying that an install has not gone as expected
This looks to have had a bad install. Based on the registry and directory structure  it looks like it didn't download all of the WDS files during its first run. I re-imaged the machine and it came back up just fine
I have rebooted it several times and things seem okay. My initial hunch is that this machine was being imaged during one of the "WDS1 cpu events" but I will need to do more research to verify.
Would you like us to put the machine back into the production pool? or do you need it for debugging purposes?
(In reply to Armen Zambrano G. [:armenzg] from comment #3)
> Would you like us to put the machine back into the production pool? or do
> you need it for debugging purposes?

I just saw the other comment on the other bug.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: