Adding physical port to ovs bridge fails

[Stanislav Makar]

When use ovs provider for everything, deployments fail during task netconfig.pp due to l2_port/ovs provider does not flush previous routes (reproduced for admin interface)

How to reproduce :
choose ovs provider for br-fw-admin and physical port as well and deploy

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/255203
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=2e6cfc9bb4327ecc2ffb76690db22e44930946a9
Submitter: Jenkins
Branch: master

commit 2e6cfc9bb4327ecc2ffb76690db22e44930946a9
Author: Stanislav Makar <email address hidden>
Date: Wed Dec 9 11:01:43 2015 +0000

    Fix adding physical port to ovs bridge

    When ovs provider is used for everything, deployments fail during task
    netconfig.pp due to l2_port/ovs provider does not flush previous routes.

    Change-Id: I1db11f55e309bf343ce98545eb6e6641b9872a49
    Closes-bug: #1524294

[Sergey Novikov (snovikov)]

Verified on VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "417"
  build_id: "417"
  fuel-nailgun_sha: "9ebbaa0473effafa5adee40270da96acf9c7d58a"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "df16d41cd7a9445cf82ad9fd8f0d53824711fcd8"
  fuel-nailgun-agent_sha: "92ebd5ade6fab60897761bfa084aefc320bff246"
  astute_sha: "c7ca63a49216744e0bfdfff5cb527556aad2e2a5"
  fuel-library_sha: "7ef751bdc0e4601310e85b8bf713a62ed4aee305"
  fuel-ostf_sha: "214e794835acc7aa0c1c5de936e93696a90bb57a"
  fuel-mirror_sha: "b62f3cce5321fd570c6589bc2684eab994c3f3f2"
  fuelmenu_sha: "2a0def56276f0fc30fd949605eeefc43e5d7cc6c"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "9f0ba4577915ce1e77f5dc9c639a5ef66ca45896"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "cfeadd34d8d048deeabf0884931708b1d040b8a6"

Steps to verify:

1. Prepare cluster with 3 controller and 2 compute nodes
2. Upload network template http://pastebin.com/LvmcL4GK
3. Deploy cluster
4. Run OSTF tests