Fuel for OpenStack

Network notation is always reset to 'cidr' while configuring multiple cluster networks

Bug #1519861 reported by Artem Panchenko on 2015-11-25

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Fuel for OpenStack	Fix Released	High	Aleksey Kasatkin	Fuel for OpenStack 8.0

Bug Description

Fuel version info (8.0 build #204): http://paste.openstack.org/show/479998/

Network notation is always reset to 'cidr' while configuring multiple cluster networks. This cause incorrect networks IP ranges configuration, so gateway IP becomes a part of range and deployment fails:

AssertionError: Task 'deploy' has incorrect status. error != ready, 'Gateway address belongs to the network's IP range [10.109.2.1-10.109.2.254].
Gateway address belongs to the network's IP range [10.109.4.1-10.109.4.254].
Gateway address belongs to the network's IP range [10.109.3.1-10.109.3.254].
Gateway address belongs to the network's IP range [10.109.17.1-10.109.17.254].
Gateway address belongs to the network's IP range [10.109.19.1-10.109.19.254].
Gateway address belongs to the network's IP range [10.109.18.1-10.109.18.254].'

Steps to reproduce:

1. Create cluster
2. Create new nodegroup
3. Configure cluster networks, so each network has a gateway, its IP ranges are valid, notation is 'ip_ranges'
4. Upload network configuration to Nailgun, download it and upload again (without changes)
5. Deploy cluster

Expected result: cluster is deployed and networks configuration is left the same as at step #3

Actual result: deployment failed (see error above), because networks notation was reset to 'cidr' and IP ranges were automatically changed for all networks except admin and public

Diagnostic snapshot is attached.

Tags: