Public bug reported:
When setting up a port that is not bound and assinging a Floating IP
(FIP) to it, the FIP gets associated but the Horizon UI does not show
the IP of the port, instead it shows a - .
The terraform/tofu snippet for the setup:
resource "openstack_networking_floatingip_associate_v2" "fip_1" {
floating_ip =
data.openstack_networking_floatingip_v2.fip_1.address
port_id = openstack_networking_port_v2.port_vip.id
}
resource "openstack_networking_port_v2" "port_vip" {
name = "port_vip"
network_id =
data.openstack_networking_network_v2.network_1.id
fixed_ip {
subnet_id = data.openstack_networking_subnet_v2.subnet_1.id
ip_address = "192.168.56.30"
}
}
Example from UI :
185.102.215.242 floatit
stack1-config-barssl-3-hostany-bootstrap-1896c992-3e17-4fab-b084-bb642c517cbe
192.168.56.20 europe-se-1-1a-net0 Active
193.93.250.171 - europe-se-1-1a-net0 Active
The top one is a port that is asigned to a host that looks as expected,
the second is not and corresponds to the terraform snippet. ( it is
being used as a floating IP internal for load balancing )
Expected is to see the IP 192.168.56.30 that is set at creation.
** Affects: horizon
Importance: Undecided
Status: New
--
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/2047132
Title:
floating ip on inactive port not shown in Horizon UI floating ip
details
Status in OpenStack Dashboard (Horizon):
New
Bug description:
When setting up a port that is not bound and assinging a Floating IP
(FIP) to it, the FIP gets associated but the Horizon UI does not show
the IP of the port, instead it shows a - .
The terraform/tofu snippet for the setup:
resource "openstack_networking_floatingip_associate_v2" "fip_1" {
floating_ip =
data.openstack_networking_floatingip_v2.fip_1.address
port_id = openstack_networking_port_v2.port_vip.id
}
resource "openstack_networking_port_v2" "port_vip" {
name = "port_vip"
network_id =
data.openstack_networking_network_v2.network_1.id
fixed_ip {
subnet_id =
data.openstack_networking_subnet_v2.subnet_1.id
ip_address = "192.168.56.30"
}
}
Example from UI :
185.102.215.242 floatit
stack1-config-barssl-3-hostany-bootstrap-1896c992-3e17-4fab-b084-bb642c517cbe
192.168.56.20 europe-se-1-1a-net0 Active
193.93.250.171 - europe-se-1-1a-net0 Active
The top one is a port that is asigned to a host that looks as
expected, the second is not and corresponds to the terraform snippet.
( it is being used as a floating IP internal for load balancing )
Expected is to see the IP 192.168.56.30 that is set at creation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/2047132/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
