Closed
Bug 1023856
Opened 11 years ago
Closed 11 years ago
Slave loan request for a talos-r4-snow machine
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jgraham, Assigned: jgraham)
References
Details
(Whiteboard: [buildduty][capacity][buildslaves][loaner])
I want to borrow a slave to help green up web-platform-tests on OSX. Thanks!
Updated•11 years ago
|
Assignee: nobody → sbruno
Updated•11 years ago
|
Assignee: sbruno → james
Comment 1•11 years ago
|
||
Instructions provided via email. James: please close this bug when you are done with the loaner so that we can reclaim it. Thanks!
Updated•11 years ago
|
Blocks: t-snow-r4-0135
Assignee | ||
Comment 2•11 years ago
|
||
This was previously working, but I no longer seem to be be able to access the machine via SSH or VNC. I am connected to the VPN, but I get an error like "ssh: Could not resolve hostname. Name or service not known"
Comment 3•11 years ago
|
||
hmm, I can connect fine.
I think someone is still on the machine too:
cltbld console Mon Jun 16 16:48 still logged in
unless that's screen session or something
I'll check vpn access list to make sure both you and this host is on it.
Comment 4•11 years ago
|
||
Oh, I think this hostname of the slave has recently changed as it may have been involved with a recent move.
a valid fqdn should be: t-snow-r4-0135.test.releng.scl3.mozilla.com
Looking at the history of your loaner host (https://bugzilla.mozilla.org/show_bug.cgi?id=988830) I am also afraid this slave might have been re-imaged. Let me look into it this morning. Sorry for the interruption.
Assignee | ||
Comment 5•11 years ago
|
||
OK, it seems like I can resolve the new hostname, but I still can't connect.
Comment 6•11 years ago
|
||
re-added new hostname to vpn loaner access list and cleaned machine of secrets. Looks like there was some human error and this machine was re-imaged without informing you. Apologies if you lost state.
could you please try again? I'm in #releng if you have any other issues and want a quick response.
Comment 7•11 years ago
|
||
James, were you able to connect now? Do you still need this slave?
If you can't connect, we can check the vpn settings in ldap to make sure you personally are in there, and also the machine.
Flags: needinfo?(james)
Assignee | ||
Comment 8•11 years ago
|
||
I think I'm done with the slave for now, but I would just like to do a few more runs this weekend to see if the OSX situation for my testsuite is looking reasonable or not.
Flags: needinfo?(james)
Assignee | ||
Comment 9•11 years ago
|
||
OK, I am done with this slave. Thanks for all your help!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: Loan Requests → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•