nova-network doesn't create SNAT rules if CONF.force_snat_range is not set

[Roman Podoliaka]

In Juno network-network no longer creates SNAT rules for new networks if CONF.force_snat_range is not set to '0.0.0.0/0'.

This was changed in 59ac254bf15bb059cca12a82c9d819c371ea5c6f (https://review.openstack.org/#/c/94112/), which treats external gateway in a special way (though, in this case, it's not an external gateway).

Curiously, those rules will be created when nova-network process is restarted (must be something 59ac254bf15bb059cca12a82c9d819c371ea5c6f didn't intend to do).

[Vladimir Kuklin (vkuklin)]

Workaround is to set force_snat_range to 0.0.0.0/0 for deployment to succeed.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/128379
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=7580b284f7ab38fb1f9bed23994afd1ef67a170f
Submitter: Jenkins
Branch: master

commit 7580b284f7ab38fb1f9bed23994afd1ef67a170f
Author: Vladimir Kuklin <email address hidden>
Date: Tue Oct 14 21:52:47 2014 +0400

    Set force_snat_range to ANY network

    Due to change 59ac254bf15bb059cca12a82c9d819c371ea5c6f
    Nova-network checks whether network has external gateway
    and does (which it has by default) and does not create SNAT
    rules for the instances if list of force snat ranges is empty
    now.

    This change sets force_snat_range to ANY network and thus
    new code adds corresponding rules.

    Change-Id: I8d22a2564dfcd8e81543d7a25089a0e7af3ca2b3
    Closes-bug: #1381164

[Dennis Dmitriev (ddmitriev)]

{"build_id": "2014-10-15_12-56-31", "ostf_sha": "de177931b53fbe9655502b73d03910b8118e25f1", "build_number": "22", "auth_required": true, "api": "1.0", "nailgun_sha": "bddd4a2571af02de3a7d8f0640928a5c2f16d48c", "production": "docker", "fuelmain_sha": "aa19ee635a48df8398b08a8934f3264d46ca55ce", "astute_sha": "c440db0449f3fe6ce6007b514e9133d8f6d0c750", "feature_groups": ["mirantis"], "release": "6.0", "release_versions": {"2014.2-6.0": {"VERSION": {"build_id": "2014-10-15_12-56-31", "ostf_sha": "de177931b53fbe9655502b73d03910b8118e25f1", "build_number": "22", "api": "1.0", "nailgun_sha": "bddd4a2571af02de3a7d8f0640928a5c2f16d48c", "production": "docker", "fuelmain_sha": "aa19ee635a48df8398b08a8934f3264d46ca55ce", "astute_sha": "c440db0449f3fe6ce6007b514e9133d8f6d0c750", "feature_groups": ["mirantis"], "release": "6.0", "fuellib_sha": "c03e89d3e59685ccd1c230a53f4eb8da95047aac"}}}, "fuellib_sha": "c03e89d3e59685ccd1c230a53f4eb8da95047aac"}

[Alexander Ignatov (aignatov)]

Oleg confirmed that bug doesn't affect mos part since it has been fixed in Fuel side.