[nailgun] 'Verify networks' failed after success HA deploy

[Stanislaw Bogatkin]

{"build_id": "2014-07-17_16-59-40",
 "ostf_sha": "9863db951a6e159f4fa6e6861c8331e1af069cf8",
"build_number": "433",
"auth_required": false,
"api": "1.0",
"nailgun_sha": "e4b2810fe69cc6f0b4bde72692bfd340e11956f5",
"production": "docker",
"fuelmain_sha": "37b50682c58444d33bf5fbe17814591af2109e7e",
"astute_sha": "d90cad0130da014eded5c21fa5f31054ce999dac",
"feature_groups": ["mirantis"],
 "release": "5.1",
"fuellib_sha": "0c9da0cea8d32c11df725b9fa48858fcaa1d9f30"
}

Steps to reproduce:
1. Create new env
2. Select CentOS, HA mode, “Neutron with VLANs”
3. Add 3 controllers, 1 compute
4. Run 'Deploy changes'

All will success, but if we check 'verify networks' in Networks tab on master node, it will fail with:

Verification failed.
Node Name Node MAC address Node Interface Expected VLAN (not received)
Untitled (6c:46) 64:f1:a6:25:6c:46 eth0 1027,1028,1029,102,1000,1001,1002,1030,101

But from controller (6c:46) we can see:

# ovs-vsctl show

[root@node-10 ~]# ovs-vsctl show
2eae23e3-7636-43d5-a4b2-941435beed40
    Bridge br-prv
        Port br-prv
            Interface br-prv
                type: internal
        Port "br-prv--br-eth0"
            Interface "br-prv--br-eth0"
                type: patch
                options: {peer="br-eth0--br-prv"}
        Port phy-br-prv
            Interface phy-br-prv
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "br-ex--br-eth1"
            trunks: [0]
            Interface "br-ex--br-eth1"
                type: patch
                options: {peer="br-eth1--br-ex"}
        Port phy-br-ex
            Interface phy-br-ex
        Port "qg-4078cc94-d3"
            Interface "qg-4078cc94-d3"
                type: internal
    Bridge br-int
        Port int-br-ex
            Interface int-br-ex
        Port br-int
            Interface br-int
                type: internal
        Port "qr-12f4c2e3-46"
            tag: 1
            Interface "qr-12f4c2e3-46"
                type: internal
        Port int-br-prv
            Interface int-br-prv
    Bridge br-fw-admin
        Port br-fw-admin
            Interface br-fw-admin
                type: internal
        Port "br-fw-admin--br-eth0"
            trunks: [0]
            Interface "br-fw-admin--br-eth0"
                type: patch
                options: {peer="br-eth0--br-fw-admin"}
    Bridge "br-eth2"
        Port "eth2"
            Interface "eth2"
        Port "br-eth2"
            Interface "br-eth2"
                type: internal
    Bridge br-mgmt
        Port br-mgmt
            Interface br-mgmt
                type: internal
        Port "br-mgmt--br-eth0"
            Interface "br-mgmt--br-eth0"
                type: patch
                options: {peer="br-eth0--br-mgmt"}
    Bridge "br-eth1"
        Port "br-eth1--br-ex"
            trunks: [0]
            Interface "br-eth1--br-ex"
                type: patch
                options: {peer="br-ex--br-eth1"}
        Port "br-eth1"
            Interface "br-eth1"
                type: internal
        Port "eth1"
            Interface "eth1"
    Bridge "br-eth3"
        Port "eth3"
            Interface "eth3"
        Port "br-eth3"
            Interface "br-eth3"
                type: internal
    Bridge "br-eth4"
        Port "eth4"
            Interface "eth4"
        Port "br-eth4"
            Interface "br-eth4"
                type: internal
    Bridge br-storage
        Port "br-storage--br-eth0"
            Interface "br-storage--br-eth0"
                type: patch
                options: {peer="br-eth0--br-storage"}
        Port br-storage
            Interface br-storage
                type: internal
    Bridge "br-eth0"
        Port "br-eth0--br-prv"
            Interface "br-eth0--br-prv"
                type: patch
                options: {peer="br-prv--br-eth0"}
        Port "eth0"
            Interface "eth0"
        Port "br-eth0--br-mgmt"
            tag: 101
            Interface "br-eth0--br-mgmt"
                type: patch
                options: {peer="br-mgmt--br-eth0"}
        Port "br-eth0"
            Interface "br-eth0"
                type: internal
        Port "br-eth0--br-storage"
            tag: 102
            Interface "br-eth0--br-storage"
                type: patch
                options: {peer="br-storage--br-eth0"}
        Port "br-eth0--br-fw-admin"
            trunks: [0]
            Interface "br-eth0--br-fw-admin"
                type: patch
                options: {peer="br-fw-admin--br-eth0"}
    ovs_version: "1.10.2"
[root@node-10 ~]#

[Dima Shulyak (dshulyak)]

I observed this issue previously on environments with high load, one of the controller did not recieve part of sended vlans.
I am pretty sure this issue will dissapear after second run of network verification

I will mark this as duplicate to https://bugs.launchpad.net/fuel/+bug/1306705 , reopen that but and will try to find cause of such behaviour one more time