yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #39158
[Bug 1499670] [NEW] Option "Associate Floating IP" available for instances that can't have interfaces with floating ip
Public bug reported:
If we have one network topology like the one attached, the instance
"ne2" has the IP 20.0.0.3 but the 20.0.0.0/24 isn't an external network,
but when we go to http://host/dashboard/project/routers/<instance-id>/
we see the option "Associate Floating IP" and when the pop-up "Manage
Floating IP Associations" opens there aren't any port of instance "ne2"
listed, and this is correct, the network that the instance is attached
isn't an external network but the option of "Associate Floating IP" is
incorrect.
HORIZON_BRANCH=master
** Affects: horizon
Importance: Undecided
Status: New
** Attachment added: "Captura de ecrã 2015-09-25, às 11.14.43.png"
https://bugs.launchpad.net/bugs/1499670/+attachment/4474208/+files/Captura%20de%20ecr%C3%A3%202015-09-25%2C%20%C3%A0s%2011.14.43.png
** Description changed:
If we have one network topology like this one:
- +-+
- | | +--+ +--+
- | | | | 10.0.0.4 router_interface | |
- | | | | 20.0.0.1 router_interface | | + When we go to:
+ <pre>
+ +-+
+ | | +--+ +--+
+ | | | | 10.0.0.4 router_interface | |
+ | | | | 20.0.0.1 router_interface | | + When we go to:
| | | | | | | /dashboard/project/instances/<instance-id>/
- | | | | +-----+ | | | We have the option Associate Floating IP
- | | | +------+ R2 +-------------------+ | | but when the pop up "Manage Floating IP
- | | +----+ | | +-----+ | | | Associations" the instance ports are not
- | +----------+ R1 +----------------+ | | | | listed because this instance can't have
- | | +----+ | | | | v floating IPs.
- | | | | | |
- | | 172.24.4.2 router_gateway| | +--------------------+ | | +---------------+
- | | 10.0.0.1 router_interface| +--+ Instance 1 | | +-----+ Instance 2 |
- | | | | +--------------------+ | | +---------------+
- | | | | 10.0.0.3 | | 20.0.0.3
- | | | | 172.24.4.4 (floating ip) | |
- | | | | | |
- | | | | | |
- | | | | | |
- | | | | | |
- | | | |Private | |Private
- | | | |10.0.0.0/24 | |20.0.0.0/24
- | | +--+ +--+
- | | External network:
- | | 172.24.4.0/24
- | |
+ | | | | +-----+ | | | We have the option Associate Floating IP
+ | | | +------+ R2 +-------------------+ | | but when the pop up "Manage Floating IP
+ | | +----+ | | +-----+ | | | Associations" the instance ports are not
+ | +----------+ R1 +----------------+ | | | | listed because this instance can't have
+ | | +----+ | | | | v floating IPs.
+ | | | | | |
+ | | 172.24.4.2 router_gateway| | +--------------------+ | | +---------------+
+ | | 10.0.0.1 router_interface| +--+ Instance 1 | | +-----+ Instance 2 |
+ | | | | +--------------------+ | | +---------------+
+ | | | | 10.0.0.3 | | 20.0.0.3
+ | | | | 172.24.4.4 (floating ip) | |
+ | | | | | |
+ | | | | | |
+ | | | | | |
+ | | | | | |
+ | | | |Private | |Private
+ | | | |10.0.0.0/24 | |20.0.0.0/24
+ | | +--+ +--+
+ | | External network:
+ | | 172.24.4.0/24
+ | |
+-+
+ </pre>
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1499670
Title:
Option "Associate Floating IP" available for instances that can't have
interfaces with floating ip
Status in OpenStack Dashboard (Horizon):
New
Bug description:
If we have one network topology like the one attached, the instance
"ne2" has the IP 20.0.0.3 but the 20.0.0.0/24 isn't an external
network, but when we go to http://host/dashboard/project/routers
/<instance-id>/ we see the option "Associate Floating IP" and when the
pop-up "Manage Floating IP Associations" opens there aren't any port
of instance "ne2" listed, and this is correct, the network that the
instance is attached isn't an external network but the option of
"Associate Floating IP" is incorrect.
HORIZON_BRANCH=master
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1499670/+subscriptions
