private instance IPs can only reach public IPs in other regions, not the same region
Bug #1022612 reported by
Nick Moffitt
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Opinion
|
Undecided
|
Unassigned | ||
nova (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Take three instances in two regions (A and B) such that they are named A1, A2, and B1. A1 is the only instance with a public IP: A2 and B1 only have the standard private IPs they were given. In this situation:
A1 can reach both of its own interfaces.
B1 can reach A1's public IP, but not its private IP.
A2 can reach A1's private IP, but not its public IP.
This last line is counter-intuitive, as B1 can reach A1's public IP just fine. In fact, if we bring a public IP up on B1, A2 can reach B1's public IP without trouble.
Traceroutes halt right out of the gate, which may or may not indicate that this is enforced by nova-network itself.
Changed in nova: | |
status: | Incomplete → Opinion |
To post a comment you must log in.
FTR, actually A1 can't reach it's public IP either.