Comment 1 for bug 1477475

The small research was done: OVS don't create veth pair for connection of br-int and bridge which was created for VM.

For example,

root@node-3:~# ovs-vsctl show
ec7e0e5e-27f1-495f-8132-f75c6143f8ec
    Bridge br-int
        fail_mode: secure
        Port "qvo39a97be3-88"
            tag: 1
            Interface "qvo39a97be3-88"
        Port int-br-prv
            Interface int-br-prv
                type: patch
                options: {peer=phy-br-prv}
        Port br-int
            Interface br-int
                type: internal
        Port "qvob3dbdaaa-24"
            tag: 1
            Interface "qvob3dbdaaa-24"
    Bridge br-prv
        Port phy-br-prv
            Interface phy-br-prv
                type: patch
                options: {peer=int-br-prv}
        Port "p_br-prv-0"
            Interface "p_br-prv-0"
                type: internal
        Port br-prv
            Interface br-prv
                type: internal
    ovs_version: "2.3.1"
root@node-3:~# brctl show
bridge name bridge id STP enabled interfaces
br-fw-admin 8000.640ac0d516d8 no eth0
br-mgmt 8000.64474cf31a9b no eth2
       p_br-prv-0
br-storage 8000.6456e9078afc no eth4
qbr1ceb0108-7e 8000.da23070d75fb no qvb1ceb0108-7e
       tap1ceb0108-7e
qbr39a97be3-88 8000.5aba96dbdc1d no qvb39a97be3-88
       tap39a97be3-88
qbrb3dbdaaa-24 8000.362497c67f72 no qvbb3dbdaaa-24
       tapb3dbdaaa-24

As you can see, veth pair is absent for bridges br-int and qvb1ceb0108-7e. Bridge "qvb1ceb0108-7e" matches inaccessible VM.