Public bug reported:
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.
** Affects: neutron
Importance: Undecided
Status: New
** Summary changed:
- 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
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1806032
Title:
neutron doesn't prevent the network update from external to internal
when floatingIPs present
Status in neutron:
New
Bug 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1806032/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
