Comment 3 for bug 1263895

After changing public IP/networks via CLI and deployment, Nailgun returns old IPs/networks which is wrong and it breaks OSTF.

{"build_id": "2014-02-21_13-53-24", "mirantis": "yes", "build_number": "176", "nailgun_sha": "d528441c490fc53f26a9115fb866d41208727d1a", "ostf_sha": "e74dcb33134d4334786a4fa27107febf9a497f2b", "fuelmain_sha": "fe157dcc0c68a237b527cb9b6adf9101c815e374", "astute_sha": "3d43abeefb60677ce6cae83d31ebbba1ff3cdbe2", "release": "4.1", "fuellib_sha": "a964b37f7f96f62a2f92b117c06077b53386a3ae"}

Steps to reproduce:

1. Create CentOS simple env with Novanetwork+FlatDHCP
2. Add 3 nodes: 1 controller, 1 cinder, 1 compute.
3. On Fuel node run (may need to adjust env ID):
fuel deployment default --env-id=1
4. Change public network address and IPs to anything different from what you have.
5. On Fuel node run the following command to upload changes:
fuel deployment --upload --dir /root/deployment_1 --env 1
6. Deploy changes:
fuel deploy-changes --env 1
7. After deployment ends check public IPs via API:
curl -s http://127.0.0.1:8000/api/clusters/1/network_configuration/nova_network
You will get old public IPs/networks that were configured before changes made via CLI.
8. Run OSTF via Fuel web interface. It will fail all tests with "Keystone client is not available. Please, refer to OpenStack logs to fix this problem".

In "nailgun" DB I can see old IPs in "ip_addrs" and "ip_addr_ranges" tables.

Archive with diagnostic snapshot, DBs dumps and deployment yamls attached.