Closed Bug 1127411 Opened 9 years ago Closed 9 years ago

Slave loan request for a bld-linux64-ec2 vm

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: markco, Assigned: markco)

References

Details

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

I have a handful of Puppet patches I need to test before landing. The patches are for Windows support, but I want to make sure they do not causes any errors on a Posix builder.

It should be maybe an hour, and then the machine can be re-enabled.
cool. I'll create one for you now :)
Assignee: nobody → jlund
I have dev-linux64-ec2-mcornmesser.dev.releng.use1.mozilla.com created for you. Passwords and other bits have not been cleaned. You can still use puppet but if you reboot the machine, you will have to manually kill the runner daemon (`service runner stop`) as root. Otherwise runner will keep rebooting your machine after 5min.

Let me know if you need anything. I'll assign this bug to you. Please mark this bug as resolved when you are finished with it forever :)
Assignee: jlund → mcornmesser
Status: NEW → ASSIGNED
Flags: needinfo?(mcornmesser)
Blocks: 1128008
Again thank you.

Is this instance something I could spin up and spin down in the future? Just so I have something safe to test on when needed but not have instance idle for days at a time.
Flags: needinfo?(mcornmesser)
Odd this seems to be rebooting after I run puppet. Any thoughts?
(In reply to Mark Cornmesser [:markco] from comment #3)
> Is this instance something I could spin up and spin down in the future? Just
> so I have something safe to test on when needed but not have instance idle
> for days at a time.

We can get you access to aws-manager1 and/or the AWS console if you want direct control. Since you'll be working with AWS a lot, both probably make sense. 

Adding a needinfo to :rail to get that setup.
Flags: needinfo?(rail)
(In reply to Mark Cornmesser [:markco] from comment #4)
> Odd this seems to be rebooting after I run puppet. Any thoughts?

There are steps in puppet that trigger a reboot afterwards. Also make sure that /opt/runner has been deleted, otherwise runner may give you reboot headaches.
> You can still use
> puppet but if you reboot the machine, you will have to manually kill the
> runner daemon (`service runner stop`) as root. Otherwise runner will keep
> rebooting your machine after 5min.

was your machine still rebooting even if you ran the above cmd?
(In reply to Chris Cooper [:coop] from comment #5)
> (In reply to Mark Cornmesser [:markco] from comment #3)
> > Is this instance something I could spin up and spin down in the future? Just
> > so I have something safe to test on when needed but not have instance idle
> > for days at a time.
> 
> We can get you access to aws-manager1 and/or the AWS console if you want
> direct control. Since you'll be working with AWS a lot, both probably make
> sense. 
> 
> Adding a needinfo to :rail to get that setup.

I see /home/mcornmesser on aws-manager1, everything should be already in place.
Flags: needinfo?(rail)
Looks like this instance has been terminated
Status: ASSIGNED → RESOLVED
Closed: 9 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.