Closed
Bug 538686
Opened 15 years ago
Closed 15 years ago
[AMO] Allow Hudson to connect to Selenium Grid server
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: clouserw, Assigned: dmoore)
References
Details
I'm attempting to hook Hudson up to QA's Selenium server. It's quasi-working off khan right now with a series of ssh tunnels around our VPNs (MPT vs. office) but to use it on hudson we'll need direct access to the box. Please allow connections from:
sm-hudson01.mozilla.org (10.2.76.137)
to:
host-7-208.mv.mozilla.com (10.250.6.185)
Destination ports will be 4444,5556,5557,5558.
Assignee | ||
Comment 1•15 years ago
|
||
Wil,
Could you elaborate more on the Selenium server at Castro? The IP address you've provided is dynamically allocated via DNS and could (would) eventually change at some point the future.
I think we'd prefer it if we could move that server to a static IP on the dedicated Build/QA network at Castro.
Assignee | ||
Comment 2•15 years ago
|
||
Er... that should read "dynamically allocated via DHCP"
Assignee | ||
Updated•15 years ago
|
Assignee: thardcastle → dmoore
Reporter | ||
Comment 3•15 years ago
|
||
Hey Derek, I don't know much about how QA's network is setup. I talked with retornam and he says he'll move this box to the qa lab and get a static ip for it today. After that we should be good.
Comment 4•15 years ago
|
||
Once I move the box the the Qa lab I will file a bug to obtain a static IP and link it to this bug as a blocker.
Assignee | ||
Comment 5•15 years ago
|
||
Thanks, Raymond. We'll open up network access after the static IP is assigned.
Assignee | ||
Comment 6•15 years ago
|
||
Network access granted from sm-hudson01 to qa-selenium.mv.mozilla.com
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 7•15 years ago
|
||
verified fixed on qa-selenium.mv.mozilla.com 10.250.48.239
Status: RESOLVED → VERIFIED
Comment 8•15 years ago
|
||
dhcp now assigns the qa-selenium.mv.mozilla.com 10.250.4.105 ( or any other 10.250.*.* after restart) instead of 10.250.48.239. This happened after changes were made to move the qa lab machines to the mv network
Severity: normal → blocker
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Updated•15 years ago
|
Assignee: dmoore → server-ops
Updated•15 years ago
|
Assignee: server-ops → dmoore
Assignee | ||
Comment 9•15 years ago
|
||
I've just moved qa-selenium back to the Build network, it should return to the assigned static IP address shortly.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Raymond/Wil: can you confirm this is fixed?
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•