Comment 1 for bug 1576185

Can't reproduce on 9.0 iso #250. Also I've found the following errors in logs from your diagnostic snapshot:

node-3: neutron-sriov-agent.log

2016-04-28 11:15:20.704 33100 ERROR neutron.agent.linux.utils [req-9f230b78-31b1-483c-bdd4-8a29aedf9679 - - - - -] Exit code: 2; Stdin: ; Stdout: ; Stderr: RTNETLINK answers: Operation not supported
2016-04-28 11:15:20.705 33100 WARNING neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [req-9f230b78-31b1-483c-bdd4-8a29aedf9679 - - - - -] Device fa:16:3e:ae:13:e5 does not support state change
2016-04-28 11:15:20.840 33100 DEBUG oslo_concurrency.lockutils [req-9f230b78-31b1-483c-bdd4-8a29aedf9679 - - - - -] Lock "qos-port" acquired by "neutron.agent.l2.extensions.qos.handle_port" :: waited 0.000s inner /usr/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:270
2016-04-28 11:15:20.841 33100 INFO neutron.agent.l2.extensions.qos [req-9f230b78-31b1-483c-bdd4-8a29aedf9679 - - - - -] QoS extension did have no information about the port ec35f707-7e9e-4d93-850c-de765411f5f1 that we were trying to reset

Did you enable Neutron QoS on your environment?