unable to reach pdu1.r101-2[12].ops.releng.scl3.mozilla.com from build vpn or boris

VERIFIED FIXED

Status

Infrastructure & Operations
DCOps
VERIFIED FIXED
6 years ago
4 years ago

People

(Reporter: arr, Assigned: dmoore)

Tracking

Details

(Reporter)

Description

6 years ago
I went to test out the ability to reboot by PDU today and I am unable to reach either PDU from the build vpns or boris.  They should be reachable by all three.  I'm not sure if this is a problem with the PDU config or with the network flows.
(Reporter)

Updated

6 years ago
Summary: unable to reach pdu1.r101-2[12].ops.releng.scl3.mozilla.com form build vpn or boris → unable to reach pdu1.r101-2[12].ops.releng.scl3.mozilla.com from build vpn or boris
(Reporter)

Comment 1

6 years ago
I also just took a look in inventory, and I didn't see either of pdu1.r101-2[12].ops.releng.scl3.mozilla.com.  Are they in there under a different name?
(Assignee)

Comment 2

6 years ago
Each logical PDU is actually two different physical units (master/slave), and they are listed separately in inventory:

pdu1a.r101-21.ops.releng.scl3
pdu1b.r101-21.ops.releng.scl3
etc.
(Assignee)

Comment 3

6 years ago
These PDUs did not have their gateway updated when they were moved to the releng network. This has been fixed, and they are now accessible from boris. Any additional connectivity issues are likely due to network ACLs.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

6 years ago
Assignee: server-ops → dmoore
(Reporter)

Comment 4

6 years ago
I can now get to the PDUs from the VPN, thanks!
Status: RESOLVED → VERIFIED
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.