Please may I have this to try figure out why we ended up with bug 1082773
Email sent to :dburns for further instructions. Loaning slaves: - tst-linux64-ec2-dburns Hi David, I am going to assign this to you to keep track of the loan. When you are finished with the loan forever, please comment stating so here in the bug, and mark the bug as RESOLVED. By the way, now that this aws instance has been created, starting and stopping it can happen in a flash! If you are not going to be using this machine for multiple hours, let us know in this bug and we can stop it. Comment again when you want it started back up. * For really fast turnaround, ping #releng (look for nick with 'buildduty')
Assignee: nobody → dburns
I wont be using this machine for the next 12 hours at least so can you please stop it and I will ping buildduty tomorrow to start it up
(In reply to David Burns :automatedtester from comment #2) > I wont be using this machine for the next 12 hours at least so can you > please stop it and I will ping buildduty tomorrow to start it up OK, instance is stopped.
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.
:automatedtester: do you still need this machine?
nope, sorry, totally forgot about this. the project I needed it for was removed from buildbot. Sorry I was a bad citizen
vpn access revoked and aws instance terminated and removed from dns
Status: NEW → RESOLVED
Last Resolved: 3 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.