Closed
Bug 668104
Opened 13 years ago
Closed 13 years ago
I need to reach staging-master from w64-ix-slave21
Categories
(Infrastructure & Operations Graveyard :: NetOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: ahill)
References
Details
I cannot ping staging-master so I can connect w64-ix-slave21 to the buildbot master. The port that I am trying to talk to is 9014. I could set up a testing master on that subnet if that makes things easier. Otherwise a hole on the firewall or moving w64-ix-slave21 back to the same net as staging-master is. Whatever you think is best.
Comment 1•13 years ago
|
||
For the time being, let's switch this machine to vlan48. I'll file a separate bug to create a new vlan for windows slaves with the same flows as vlan48, but let's not block Armen on that. Over to netops for: Move sw-4a.scl1:22 to vlan48 (should be 76 now).
Assignee: server-ops-releng → network-operations
Component: Server Operations: RelEng → Server Operations: Netops
QA Contact: zandr → mrz
Comment 2•13 years ago
|
||
My mistake: sw-4a.scl1:27 (vlan76 -> vlan48)
Comment 3•13 years ago
|
||
Amended and moved, per zandr in IRC
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•13 years ago
|
||
I can reach staging-master now. Thanks a lot!
Status: RESOLVED → VERIFIED
Comment 5•13 years ago
|
||
Please move sw-4a.scl1:22 back to the sandbox vlan76. Digipengi is blocked on getting a windows 64 image off of the this machine and back onto the windows server.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Updated•13 years ago
|
Assignee: network-operations → ahill
Port 27. moved to vlan 76 and currently untagged (to match its configuration in vlan48.) Let me know if that works.
Comment 7•13 years ago
|
||
Sorry, I cut-n-pasted the first (incorrect) port in this ticket. Port 27 is right. I rebooted the box and it appears to have gotten 10.12.76.101 as an IP and it can ping 10.12.76.10. Matt, can you confirm that the host is capable of doing what you need it to do at this point and close this ticket if so?
Comment 8•13 years ago
|
||
I am able to get to it on vlan76 now thanks Amy. I can now continue with cloning.
Status: REOPENED → UNCONFIRMED
Ever confirmed: false
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Infrastructure & Operations
Updated•2 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•