Floating range is validated against network which has meta.floating_range_var field. In the case described above this network is still the default one, so IMO either this field should removed or changed in the backend, or no validation of floating ip range correspondence to cidr can be performence on the UI side.
the first option seems better for me, so re-assigning this bug fuel-python team.
Floating range is validated against network which has meta.floating_ range_var field. In the case described above this network is still the default one, so IMO either this field should removed or changed in the backend, or no validation of floating ip range correspondence to cidr can be performence on the UI side.
the first option seems better for me, so re-assigning this bug fuel-python team.