Closed Bug 849006 Opened 11 years ago Closed 11 years ago

Need access to a B2G Arm (VM) opt test slave

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P2)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: fabrice, Unassigned)

References

Details

(Whiteboard: [buildduty][loaner]) 

I can't reproduce locally the M1 test failure from https://tbpl.mozilla.org/?tree=Try&rev=33619ab65ecd so I'd like to see what's happening on a test slave configuration.

My ldap ID is fdesre@mozilla.com
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: armenzg
Something of class tst-linux64-ec2-nnn.
Summary: Need access to a B2G Arm (VM) opt build slave → Need access to a B2G Arm (VM) opt test slave
Depends on: 850008
Assignee: nobody → dustin
Assignee: dustin → nobody
I'll spin up a VM for this.
Assignee: nobody → nthomas
Priority: -- → P2
Whiteboard: [buildduty]
VM created, but need to get hold of some credentials to finish it up.
rail commented on IRC that this slave was failing to puppet. I had created the VM but lost my network connection before that completed, so I terminated it and created a second. It may be the puppet master now has the certs from the first instance and they need to be blown away. Not being able to puppet would line up with no known credentials working for root.

rail, could you fix this up ?
Assignee: nthomas → nobody
Assignee: nobody → rail
I sent credentials for tst-fdesre-ubuntu64-001 (i-ed34c59f) 10.134.57.112.

Please assign the bug back to nobody when you don't need the slave.
Assignee: rail → fabrice
:fabrice, Just checking in; are you still using this slave?

It is fine if you are.
Flags: needinfo?(fabrice)
Whiteboard: [buildduty] → [buildduty][loaner]
(In reply to Justin Wood (:Callek) from comment #6)
> :fabrice, Just checking in; are you still using this slave?

No I'm not, sorry for not telling you!
Flags: needinfo?(fabrice)
Assignee: fabrice → nobody
I don't see this one in AWS instance console right now
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
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.