commit c86fa4fb4ee6f4bf86252ca3e1fde25fa55c3677
Author: Alex Schultz <aschultz@redhat.com>
Date:   Tue Oct 13 09:42:28 2020 -0600

    Don't manage bridge mappings in scenario file
    
    The bridge mappings should be managed in the standalone parameters. This
    bridge mapping prevents us from being able to change the datacentre
    mapping in CI.
    
    Change-Id: I6b5b9db75a11c2347720258a39b03aa28702dbf1
    Related-Bug: #1895822

diff --git a/ci/environments/scenario012-standalone.yaml b/ci/environments/scenario012-standalone.yaml
index 0689e9c..56eb5de 100644
--- a/ci/environments/scenario012-standalone.yaml
+++ b/ci/environments/scenario012-standalone.yaml
@@ -28,4 +28,3 @@ parameter_defaults:
   NeutronFlatNetworks: datacentre
   NeutronNetworkVLANRanges: 'datacentre:500:599,tenant:300:399'
   ML2HostConfigs: { "net-ans-br": { "ansible_network_os": "openvswitch", "ansible_host": "127.0.0.1", "ansible_user": "root", "ansible_ssh_private_key_file": "/etc/puppet/ci-key"}}
-  NeutronBridgeMappings: 'datacentre:br-ex,tenant:br-tenant'