Activity log for bug #1806032

Date Who What changed Old value New value Message
2018-11-30 12:43:00 lina He bug added bug
2018-11-30 12:43:47 lina He summary neutron doesn't prevent the network update from external to internal when floatingIP present neutron doesn't prevent the network update from external to internal when floatingIPs present
2018-11-30 12:59:21 lina He description The floatingIP can be created in an external network, but after updating the external network to internal, the floatingIP is still in that internal network. The updating from internal network to external should be prevented if there are FloatingIP existing or it is allowed with the floatingIPs deleted when updating. Reproduction: ~$ neutron net-create net1 --router:external true ~$ neutron floatingip-create net1neu ~$ neutron net-update net1 --router:external fasle This is based on master and stable/queens. The floatingIP can be created in an external network, but after updating the external network to internal, the floatingIP is still in that internal network. The updating from internal network to external should be prevented if there are FloatingIP existing or it is allowed with the floatingIPs deleted when updating. Reproduction: ~$ neutron net-create net1 --router:external true ~$ neutron floatingip-create net1 ~$ neutron net-update net1 --router:external fasle This is based on master and stable/queens.
2018-11-30 13:00:07 lina He description The floatingIP can be created in an external network, but after updating the external network to internal, the floatingIP is still in that internal network. The updating from internal network to external should be prevented if there are FloatingIP existing or it is allowed with the floatingIPs deleted when updating. Reproduction: ~$ neutron net-create net1 --router:external true ~$ neutron floatingip-create net1 ~$ neutron net-update net1 --router:external fasle This is based on master and stable/queens. The floatingIP can be created in an external network, but after updating the external network to internal, the floatingIP is still in that internal network. The updating from internal network to external should be prevented if there are FloatingIP existing. Reproduction: ~$ neutron net-create net1 --router:external true ~$ neutron floatingip-create net1 ~$ neutron net-update net1 --router:external fasle This is based on master and stable/queens.
2018-11-30 13:00:43 lina He description The floatingIP can be created in an external network, but after updating the external network to internal, the floatingIP is still in that internal network. The updating from internal network to external should be prevented if there are FloatingIP existing. Reproduction: ~$ neutron net-create net1 --router:external true ~$ neutron floatingip-create net1 ~$ neutron net-update net1 --router:external fasle This is based on master and stable/queens. The floatingIP can be created in an external network, but after updating the external network to internal, the floatingIP is still in that internal network. The updating from internal network to external should be prevented if there are FloatingIPs existing. Reproduction: ~$ neutron net-create net1 --router:external true ~$ neutron floatingip-create net1 ~$ neutron net-update net1 --router:external fasle This is based on master and stable/queens.
2018-12-03 13:38:52 Bence Romsics neutron: status New Confirmed
2018-12-03 13:57:28 Bence Romsics neutron: status Confirmed Incomplete
2018-12-04 10:00:33 OpenStack Infra neutron: status Incomplete In Progress
2018-12-04 10:00:33 OpenStack Infra neutron: assignee Bence Romsics (bence-romsics)
2018-12-05 22:00:20 Brian Haley bug added subscriber Brian Haley
2018-12-06 15:15:45 Bence Romsics neutron: importance Undecided Low
2019-01-21 09:04:22 Slawek Kaplonski tags l3-ipam-dhcp
2019-01-30 10:10:16 Magnus Bergman bug added subscriber Magnus Bergman
2019-04-16 08:46:09 Slawek Kaplonski neutron: status In Progress New
2019-04-16 08:46:09 Slawek Kaplonski neutron: assignee Bence Romsics (bence-romsics)
2019-04-16 08:46:15 Slawek Kaplonski tags l3-ipam-dhcp l3-ipam-dhcp timeout-abandon