I would like to get a 32 bit and a 64 bit talos (hardware) slave to test out requirements for a new latency test. Once I am done on linux, I will be requesting windows and mac.
Sorry for the delay. This will be taken care of today.
Email sent to Joel for further instructions. Loaning slaves: - talos-linux64-ix-003.test.releng.scl3.mozilla.com - talos-linux32-ix-001.test.releng.scl3.mozilla.com Joel, I am going to assign this to you to keep track of these instances. When you are finished with them forever, please comment stating so and mark this bug as resolved. Following that, I can re-open this one or file a new one for the windows and mac loans.
> Joel, I am going to assign this to you to keep track of these instances. To remove ambiguity, these are hardware machines. I didn't mean to say instances.
I am done with these two slaves, I appreciate the loan! I have reset the assigned to field, let me know if I need to do anything else.
Assignee: jmaher → nobody
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Looks like this hid under the radar and never went back to production. However, joel needs another linux32 bit hardware slave so I will use this in: Bug 981095
To be clearer, both talos-linux32-ix-001 and talos-linux64-ix-003 are not in production. vpn dep bug 969168 did not seem to be re-opened with revoke request. Joel just needs one slave a linux32 hardware in Bug 981095 so I will be just returning 003 to production. I think talos-linux32-ix-001 may be in a semi returned state? Joel says he can ping it but password no longer works. Also, I can see paths that exist like: /var/lib/puppet/ssl which I believe should have been cleaned before loan. There is no buildbot.tac or twisted.log in /builds/* For talos-linux32-ix-001, /me and resets the passwords and cleans fully again. I'll move vpn access bug over to 981095. For talos-linux64-ix-003, /me files a re-image request bug and tacks it on this bug.
talos-linux64-ix-003 is waiting re-imaging. This bug can be closed when 981238 is resolved and it is put back in production. talos-linux32-ix-001 is now being tracked in 981095
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
turns out talos-linux64-ix-003 and talos-linux32-ix-001 were re-imaged and documented so in their own tracking bugs (not the loan bugs). My fault. They were just never put back in production. Still learning these ropes. Sorry for the noise.
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago → 5 years ago
Resolution: --- → FIXED
Component: Loan Requests → Buildduty
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.