neutron-sriov-nic-agent raises UnsupportedVersion security_groups_provider_updated

Bug #1510411 reported by yjiang
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Undecided
Unassigned

Bug Description

neutron-sriov-nic-agent raises following exception:
2015-10-26 04:46:18.297 116015 ERROR oslo_messaging.rpc.dispatcher [-] Exception during message handling: Endpoint does not support RPC version 1.3. Attempted method: security_groups_provider_updated
2015-10-26 04:46:18.297 116015 ERROR oslo_messaging.rpc.dispatcher Traceback (most recent call last):
2015-10-26 04:46:18.297 116015 ERROR oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply
2015-10-26 04:46:18.297 116015 ERROR oslo_messaging.rpc.dispatcher executor_callback))
2015-10-26 04:46:18.297 116015 ERROR oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 195, in _dispatch
2015-10-26 04:46:18.297 116015 ERROR oslo_messaging.rpc.dispatcher raise UnsupportedVersion(version, method=method)
2015-10-26 04:46:18.297 116015 ERROR oslo_messaging.rpc.dispatcher UnsupportedVersion: Endpoint does not support RPC version 1.3. Attempted method: security_groups_provider_updated
2015-10-26 04:46:18.297 116015 ERROR oslo_messaging.rpc.dispatcher

This VM is build with SRIOV port(macvtap).
 jenkins@cnt-14:~$ sudo virsh list --all
 Id Name State
----------------------------------------------------
 10 instance-00000003 paused

Revision history for this message
yjiang (jiangyu27) wrote :
Rui Zang (rui-zang)
affects: networking-nec → neutron
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Can you confirm versions and steps to reproduce? See [1], for details on how to report isses.

[1] http://docs.openstack.org/developer/neutron/policies/bugs.html#bug-report-template

Changed in neutron:
status: New → Incomplete
Revision history for this message
yjiang (jiangyu27) wrote :

Linux version: 14.04.1 LTS, Trusty Tahr
Openstack version: Upstream version
SRIOV NIC: Intel Corporation I350 Ethernet Controller
It's single node.use all-in-one mode.

This is all steps:
1. localrc file http://paste.openstack.org/show/477586/
2. /etc/neutron/plugins/ml2/ml2_conf_sriov.ini http://paste.openstack.org/show/477588/
3. /etc/neutron/plugins/ml2/sriov_agent.ini http://paste.openstack.org/show/477587/
4. After devstack deployment,Restart q-svc service. Add parameter "--config-file /etc/neutron/plugins/ml2/sriov_agent.ini"
5. Start neutron-sriov-nic-agent service.
"neutron-sriov-nic-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/plugins/ml2/ml2_conf_sriov.ini --config-file /etc/neutron/plugins/ml2/sriov_agent.ini"
6. Create two network .One network use vlan mode.
7. Create two subnet on those two net.
8. Create two port belong to different subnet. One port type is macvtap,this sriov port should be assigned to vlan network The parameters like:
neutron port-create --vnic-type macvtap
the other port is normal type.
9. Launch VM with both two port.

Then you will see the exception occur in neutron-sriov-nic-agent outputs.Instance status become "paused".

Rui Zang (rui-zang)
Changed in neutron:
status: Incomplete → New
Revision history for this message
yjiang (jiangyu27) wrote :

I've changed my local.conf file http://paste.openstack.org/show/477612/
It seems like the reason why VM status keep "paused" status is em3 port on my server don't have cable connecting with my physical network.After i changed it to "em4" which have cable connecting and I can create VM with macvtap port normally.

I don't know whether it is right to keep VM "paused" state in such occasion.Maybe someone could help to answer:)
But that error information still exist in outputs of neutron-sriov-nic-agent.

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 240 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.