Closed Bug 876013 Opened 12 years ago Closed 10 years ago

Loan t-w732-ix-003, t-w732-ix-004 to Q

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

x86
Windows 7
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: q)

References

Details

(Whiteboard: [buildduty][buildslaves])

The win7 machines for working on the graphic cards solution. I don't remember what the xp machines were booked for though.
Q: I'm assigning this bug to you until you're done with those 2 win7 machines to work on the graphics solution. Mark: what was the reason to book those 2 XP machines for? I forgot.
Assignee: nobody → q
OS: Mac OS X → Windows 7
The XP machines where set a side for for further development with GPOs, monitoring, and eventually Puppet. However, currently I have shifted focus to 2008, so it maybe some time, maybe weeks, before i need to use them.
Maybe we can re-image them and put them in the pool until you need them? Wfy?
I have just kicked off a new install on t-xp32-ix-100, so it shall be available shortly. I am currently having issues finding and connecting to t-xp32-ix-099. I will take a deeper look into that today or tomorrow and get it ready to be handed over.
099 is on RMA
(In reply to Mark Cornmesser from comment #4) > I have just kicked off a new install on t-xp32-ix-100, so it shall be > available shortly. > > I am currently having issues finding and connecting to t-xp32-ix-099. I will > take a deeper look into that today or tomorrow and get it ready to be handed > over. As far as I know, we had swapped in an email thread those two machines for t-xp32-ix-001, t-xp32-ix-002. Currently, t-xp32-ix-100 is a production machine. It seems that we might have only burn a job or two: https://secure.pub.build.mozilla.org/buildapi/recent/t-xp32-ix-100 Would you mind re-imaging 001 and 002 when you can? They're currently idle.
001 and 002 and will be available shortly.
(In reply to Mark Cornmesser from comment #7) > 001 and 002 and will be available shortly. Is there a reason that VNC should not work? I get rejected.
VNC appears to be working for me on both machines with the standard password. Checking into machine t-xp32-ix-001 for anything out of order.
(In reply to Armen Zambrano G. [:armenzg] (Release Enginerring) from comment #8) > (In reply to Mark Cornmesser from comment #7) > > 001 and 002 and will be available shortly. > > Is there a reason that VNC should not work? I get rejected. The log is showing UltraVnc reporting an "Invalid Attempt". Which could possible be a bad password
(In reply to Mark Cornmesser from comment #10) > (In reply to Armen Zambrano G. [:armenzg] (Release Enginerring) from comment > #8) > > (In reply to Mark Cornmesser from comment #7) > > > 001 and 002 and will be available shortly. > > > > Is there a reason that VNC should not work? I get rejected. > > The log is showing UltraVnc reporting an "Invalid Attempt". Which could > possible be a bad password I kept on typing the cltbld password. We should have a bot slap me every time I talk about VNC not working.
Whiteboard: [buildduty][buildslaves]
Component: Release Engineering: Machine Management → Release Engineering: Loan Requests
Product: mozilla.org → Release Engineering
Hi Q, are you using t-w732-ix-003 and t-w732-ix-004 actively? All good if so. If not, I would like to put them back in the pool.
Flags: needinfo?(q)
We are, unfortunately, still actively using those two machines to get a grip on several outstanding graphics issues.
Flags: needinfo?(q)
Sorry to hear that. Best of luck.
No longer blocks: t-xp32-ix-002, t-xp32-ix-001
Summary: Loan t-w732-ix-003, t-w732-ix-004 to Q and t-xp32-ix-001, t-xp32-ix-002 to Mark → Loan t-w732-ix-003, t-w732-ix-004 to Q
(note drop) releng and amy met on monday, and that discussion identified these were still in use, (dropping a comment since its been a while since a status update here).
Do you still need these loaners?
Flags: needinfo?(q)
Yes unfortunately we are still battling this one between other fires.
Flags: needinfo?(q)
Update from Q: nothing concrete unfortunately have been focusing on other things for the last couple of weeks.
QA Contact: armenzg → coop
Hey Q, Still needed? Thanks, Pete
Flags: needinfo?(q)
Yes unfortunately, but this should be the last quarter they are needed. Q
Flags: needinfo?(q)
Status: NEW → ASSIGNED
It's 2015, so I'd like to check-in to see if you still need your loaned slave. If yes, great, just let buildduty know when you are done. If you no longer need the slave, comment here and then un-assign yourself from the bug. buildduty will take care of it from there.
Just take them back.
We are still using these machines unfortunately
These can go back into the pool.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Component: Loan Requests → Buildduty
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.