Closed Bug 964564 Opened 12 years ago Closed 11 years ago

Slave loan request for a tst-linux64-ec2 machine

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: tedders1, Unassigned)

References

Details

(Whiteboard: [buildduty][capacity][buildslaves][loaner])

No description provided.
Blocks: 965577
Depends on: 965578
Sorry for the delay ted, it will be a bit longer. Rail, I needinfo'd you in another bug re: IP's being available which look like they shouldn't. After getting through that IP trap I'm now getting: EC2ResponseError: EC2ResponseError: 400 Bad Request <?xml version="1.0" encoding="UTF-8"?> <Response><Errors><Error><Code>Unsupported</Code><Message>VPC is not currently supported for your requested instance type (m3.med ium) in us-east-1b. Please retry your request by not specifying an Availability Zone or choosing us-east-1a, us-east-1c, us-east- 1d.</Message></Error></Errors><RequestID>abc47036-74e2-4de2-aa7e-27dd460ce6a8</RequestID></Response> Can I just ask you to please fix either our loan docs or the files now that we've changed some of our aws infra during this past week.
Flags: needinfo?(rail)
I symlinked the new virtualenv so it matches the docs. The error above is something that we don't ave control on. :/ You can try to use m1.medium or change the make sure that the IP is not in that "bad" subnet (you'll need to change the DNS entries as well). The infra changes are still in progress. As soon as they are stabilize I'll update the docs.
Flags: needinfo?(rail)
(In reply to Rail Aliiev [:rail] from comment #3) > I symlinked the new virtualenv so it matches the docs. > > The error above is something that we don't ave control on. :/ You can try to > use m1.medium or change the make sure that the IP is not in that "bad" > subnet (you'll need to change the DNS entries as well). > > The infra changes are still in progress. As soon as they are stabilize I'll > update the docs. Sure, but that doesn't tell me how to get the loaner complete. The IP is not in the reserved subnet of AWS, we get different errors when that is the case. What I need to know is "how do I correct the loaner process to give him a loaner like our production systems" -- I don't grok what is wrong and need assistance to do that --- the new venv didn't help
Flags: needinfo?(rail)
* run free_ip.py * check if the ip has a PTR entry already (host $ip or something) * repeat from start if there is a PTR entry
Flags: needinfo?(rail)
creds sent over e-mail, please close this bug when you're done with it
Assignee: nobody → tclancy
Hi Ted, I'm just sweeping through our running instances. I *think* there has been little activity on yours since Monday. By the way, we can always stop[shutdown] and start this instance in a flash if you feel there are going to be gaps in use. If you need this constantly, please ignore this poke and, as mentioned, close this bug when you are done with this instance forever[terminate].
^ comment 7
Flags: needinfo?(tclancy)
I've stopped the instance for now until I hear back. Please poke buildduty (on #releng with nickname ending "_buildduty) if you need the instance back. If we don't hear back from you by next week we will terminate the instance and ask you to request a new one if you happen to come back to this bug.
Hey, sorry for the delay. I've been distracted with a high-priority issue for the past couple weeks. I'm about to get back to working on this.
When would you like me to start it back?
As soon as is convenient for you.
Flags: needinfo?(tclancy)
It seems to be running. Please close the bug once you're done with it. Happy hacking!
Hi again Ted - you're certainly welcome to this machine as long as its useful, but I haven't seen a login since it was restarted. I've shut it down again to avoid paying for unused EC2 time. Please let me know when you're ready to use it again.
Hi Ben. Yeah, something important came up last Friday, and it kept me occupied over the past couple days. Can you restart the machine now?
(In reply to Ted Clancy [:tedders1] from comment #15) > Hi Ben. Yeah, something important came up last Friday, and it kept me > occupied over the past couple days. > > Can you restart the machine now? I just restarted the machine - sorry for the delay!
Ted, per your request on IRC I added an additional 40GB disk to this machine. It's mounted at /builds2 - sorry it took so long!
Are you still actively using this host, if yes no problem. If not but you still need it we can/should shut it down to save costs. If you don't need it at all we'll reclaim
Flags: needinfo?(tclancy)
no-one is logged into it now, `last` as root doesn't even show me any history, so I'm stopping it in ec2, please ping us in #releng or here when you need it again
No prob. To be honest, I don't think I'll be returning to this anytime soon.
(Clearing the needinfo.)
Okay, why can't I clear the needinfo flag? It's not working for me.
Flags: needinfo?(tclancy)
Oh, there it goes.
Assignee: tclancy → nobody
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
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.