1196602 - Requesting a loaner machine b2g_ubuntu64_vm to diagnose Bug 1194979

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task)

Description

[Greg Weng [:snowmantw][:gweng][:λ]]

Hello, I need a loaner machine of type b2g_ubuntu64_vm since I want to diagnose why some Gaia Unit tests only failed on CI environment. The failure is recorded at Bug 1194979.

Comment 1

[Alin Selagea [:aselagea]]

Email sent to :gweng for further instructions. 

Loaning machines: 
- tst-linux64-ec2-gweng

Hi Greg, 

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 faster turnaround, ping #releng (look for nick with 'buildduty')

Comment 2

[Greg Weng [:snowmantw][:gweng][:λ]]

Hi Alin: when I tried to connect to the machine with the FQDN under VPN protection, it reported

    port 22: Connection refused

Does this mean I need to do some other configs to connect to the instance?

Comment 3

[Alin Selagea [:aselagea]]

Hello Greg,

Sorry for the inconvenience. I only added the IP and hostname of the machine in VPN ACL, but not your account. It should be fixed now, so please try again.

Comment 4

[Greg Weng [:snowmantw][:gweng][:λ]]

It shows the same error. I write my steps to make sure I didn't do anything wrong:

1. Use Tunnelblick with the config file extracted from the package downloaded from the logins server
2. Connect to datacenter VPN with my own account and password. I confirmed that since only when it shows 'connected' the DNS can solve the instance to IP, otherwise it is unable to find the server
3. Try to ssh the instance with the account and password in your mail. The server seems connected but it still refuse the connection as I post at Comment 2.

Comment 5

[Alin Selagea [:aselagea]]

Before going further, please disconnect from the VPN, reconnect to it and then try to ssh once more.
Thanks.

Comment 6

[Greg Weng [:snowmantw][:gweng][:λ]]

Just an update: I now use it to debug another serious intermittent error, which relates to Bug 1194979,

Comment 7

[Nick Thomas [:nthomas] (UTC+12)]

gweng, do you still need this loaner ?

Comment 8

[Greg Weng [:snowmantw][:gweng][:λ]]

Oh no, I don't need it anymore. Because I have been unable to connect to it after there is no need to debug that, I thought the VM has been released and forgot this bug. Thanks.

Comment 9

[Nick Thomas [:nthomas] (UTC+12)]

Actually, there's no dependent bug to handle the cleanup, so lets reopen this for SoftVision to handle.

Comment 10

[Nick Thomas [:nthomas] (UTC+12)]

Assigning to Alin to silence the nagios alert about loaner bugs.

Comment 11

[Alin Selagea [:aselagea]]

Terminated the instance, removed inventory entries and revoked VPN access.