Reproduced on fuel-7.0-upgrade-144-2015-08-06_21-24-26.tar.lrz
Steps to reproduce
1) Create environment via Fuel 6.1
2) Upgrade master node
3) Send API call to clone environment
Actual result:
======================================================================
FAIL: clone_env.CloneEnvTests.test_env_clone_to_deployable_release_id
----------------------------------------------------------------------
_StringException: Traceback (most recent call last):
File "/home/ubuntu/clone_env.py", line 144, in test_env_clone_to_deployable_release_id
network["ip_ranges"])
File "/home/ubuntu/env/local/lib/python2.7/site-packages/testtools/testcase.py", line 350, in assertEqual
self.assertThat(observed, matcher, message)
File "/home/ubuntu/env/local/lib/python2.7/site-packages/testtools/testcase.py", line 435, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: [[u'10.20.2.2', u'10.20.2.254']] != [[u'10.20.2.1', u'10.20.2.254']]
Due to the fact that the ip_ranges parameter can not be changed for network groups with the CIDR notation and also the notation parameter can not be changed too (before the patch [1]) the upgrade procedure cannot set specific IP ranges. The network manager responsible for setting proper IP ranges and it has some known problems in it [2]. We have that clusters which were created in environments earlier then 7.0 (and were upgraded to 7.0) have different IP ranges of network groups for the clusters which were created in 7.0 with the same parameters.
Frankly speaking you can not break an upgrade by setting wider ranges during upgrade of clusters than it were before.
[1] https:/
[2] https:/
[3] https:/