[nailgun] Nailgun receives incorrect value of node interface state

[Egor Kotko]

{"build_id": "2014-03-14_13-49-12", "mirantis": "yes", "build_number": "29", "nailgun_sha": "06d22c86f0875943b91395cc1dc5fe92df0cefa9", "ostf_sha": "0ad6f6de46e615022c2672c345a11fb44ffaa4e1", "fuelmain_sha": "d67783166401529d1c0fe82b8a4885b6573ad7b4", "astute_sha": "e260b36adb73bb32aca1660767a988e1fce736d8", "release": "5.0", "fuellib_sha": "45320c9167979d73c6768e251f61ba2c8f928626"}

Steps to reproduce:
1. Create env:
Ubuntu, 1Controller, 2 Computes, Neutron GRE (bonding: Balance SLB on eth2,eth3), NO: Murano, Savanna, Ceilometer.
See the state of interfaces of any node(Configure Interfaces)

Expected result:
All interfaces on UI should be in active state.

Actual result:
On UI all interfaces except eth0 are in inactive state.
But if check its on node all interfaces are in UP

Nailgun receive incorrect state:

current_speed: null
id: 4
mac: "52:54:00:ec:59:bc"
max_speed: null
name: "eth0"
state: "up"
type: "ether"
1: {name:eth1, state:down, mac:52:54:00:88:63:c3, max_speed:null, current_speed:null,…}
assigned_networks: [{id:2, name:public}]
current_speed: null
id: 3
mac: "52:54:00:88:63:c3"
max_speed: null
name: "eth1"
state: "down"
type: "ether"
2: {name:eth2, state:down, mac:52:54:00:0e:bb:44, max_speed:null, current_speed:null,…}
assigned_networks: []
current_speed: null
id: 2
mac: "52:54:00:0e:bb:44"
max_speed: null
name: "eth2"
state: "down"
type: "ether"
3: {name:eth3, state:down, mac:52:54:00:fa:cf:cd, max_speed:null, current_speed:null,…}
assigned_networks: []
current_speed: null
id: 1
mac: "52:54:00:fa:cf:cd"
max_speed: null
name: "eth3"
state: "down"
type: "ether"
4: {name:ovs-bond0, state:null, mac:null, mode:balance-slb, slaves:[{name:eth3}, {name:eth2}],…}
assigned_networks: [{id:3, name:management}, {id:4, name:storage}]
mac: null
mode: "balance-slb"
name: "ovs-bond0"
slaves: [{name:eth3}, {name:eth2}]
state: null
type: "bond"

[Evgeniy L (rustyrobot)]

The problem is it doesn't work correctly on virtualbox and we didn't find a way to make it work. On KVM and baremetal it works fine.
Its known issue, I'll set low priority.

[Egor Kotko (ykotko)]

FYI: I have this bug on KVM on two different servers.

[Vladimir Sharshov (vsharshov)]

Egor, can you provide output from command

    ethtool <ethX>

Example: ethtool eth2

for such problem interfaces?

[Egor Kotko (ykotko)]

eth0 - in UI appears correctly, other are problem interfaces (see the attached screen).

root@node-1:~# ethtool eth0
Settings for eth0:
 Link detected: yes
root@node-1:~# ethtool eth1
Settings for eth1:
 Link detected: yes
root@node-1:~# ethtool eth2
Settings for eth2:
 Link detected: yes
root@node-1:~# ethtool eth3
Settings for eth3:
 Link detected: yes

[Vladimir Sharshov (vsharshov)]

At now moment as i can see this problem affect only UI part and do not block any part of functionality. Move to 5.1.

Egor Kotko, thanks for info.

[Vladimir Kuklin (vkuklin)]

need a reproducer

[Bogdan Dobrelya (bogdando)]

please try to reproduce and update the status

[Andrey Sledzinskiy (asledzinskiy)]

It's not reproduced on {

    "build_id": "2014-08-05_00-31-14",
    "mirantis": "yes",
    "build_number": "164",
    "ostf_sha": "09b6bccf7d476771ac859bb3c76c9ebec9da9e1f",
    "nailgun_sha": "04ada3cd7ef14f6741a05fd5d6690260f9198095",
    "production": "docker",
    "api": "1.0",
    "fuelmain_sha": "77423fe5a01196fb11776c4db9ee6ae93bfcd4d9",
    "astute_sha": "6db5f5031b74e67b92fcac1f7998eaa296d68025",
    "release": "5.0.1",
    "fuellib_sha": "dec8421a18e3ccfa35978b36b5de3292b53e6b69"

}