Network verification fails "Public gateway or public ranges are not in one CIDR" for neutron with vlan segmentation

[Aleksandr Didenko]

Versions: {"release": "4.0", "nailgun_sha": "51ebc0ec305a35541b53256dfb5dce58f24751a4", "ostf_sha": "a8ee87612ae535808e5f49e96844ac995c02ee50", "astute_sha": "ef91b3a51030bc90a21b830a893826dac6f76eb7", "fuellib_sha": "ac52f3cf485bde0e445fb987eb31aba367dd3fb3"}

Network: neutron with vlan segmentation

Steps to reproduce:
1. Start a KVM guest with fuel-4.0-58 iso
2. Create new Environment with "neutron with vlan segmentation" network
3. In fuel web interface go to "Networks" tab under newly created environment
4. Try to change Public network, gateway and Floating IPs range to anything other than 172.16.0.0/24 (for example to 172.16.10.0/24)
5. Click "Save settings"

Result:
Verification failed.
Public gateway or public ranges are not in one CIDR.

[Andrew (box857+launchpad)]

We are using the fuel 4.0 preview built from git. We are getting the same issue.

I have one master node set up setting the ip, gw,dns1 and hostname in the kernel args in addition to having showmenu=yes.
When the install happened I set the settings in the menu as previous deployment.

If I go to the gui on port 8000 I get the same issue as AD, the original poster.

We have a current deployment and using the network arguments that work for that, but with those machines shut down the problem occurs.

Thanks.

[Andrew (box857+launchpad)]

Comparing between our working deployment and our failing 4.0 preview one.

On our working deployment we set the ranges and the vlan IDs.
On our 4.0 preview deployment if we set the VLAN IDS but except the default ranges for the IP's it seems to allow you to save the network config.

This info is second hand and I haven't seen myself it but my boss found that

/22 in public was recognized as /24

If I see that I will post that info to confirm.

Thanks.

[Julia Aranovich (jkirnosova)]

The problem can be caused by PUT request data for public network:
{"network_size":256,"name":"public","ip_ranges":[["172.16.0.2","172.16.0.126"]], "amount":1, "id":2, "netmask":"255.255.255.0", "cluster_id":1, "vlan_start":null, "cidr":"172.16.10.0/24", "gateway":"172.16.10.1"}

CIDR and gateway are changed from UI, but IP ranges not.
My proposal is not to sent on UI fields which will not used by UI (ip_ranges network attribute in this example). And manage ip_ranges/cidr calculation on backend part.

[Aleksey Kasatkin (alekseyk-ru)]

Root cause:
UI part of https://bugs.launchpad.net/fuel/+bug/1247283 (set IP ranges for Public istead of CIDR) is not merged to master.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/58938

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/58938
Committed: http://github.com/stackforge/fuel-web/commit/cd7bdfe85fbbb7f967e1a00666497cb178477f21
Submitter: Jenkins
Branch: master

commit cd7bdfe85fbbb7f967e1a00666497cb178477f21
Author: jkirnosova <email address hidden>
Date: Fri Nov 15 07:00:11 2013 -0500

    Public IP ranges for Neutron (4.0)

    Closes-Bug: #1253592

    Change-Id: Ib353bd9590c53b6369c3b84101e22317a2dbdd4b