ryu controller can not start when ovs_ryuapp.py compiled to pyc

Bug #1736400 reported by Rong.Wang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Confirmed
Undecided
Rong.Wang

Bug Description

hi,
I found a problem in my openstack,
when I use the of_interface 'native' mode, if I compiled the ovs_rpyapp.py to pyc(and remove the ovs_rpyapp.py file), and restart the openstack-openvswitch-agent.service, found that the ryu-controller could not be connected by ovs.
And, if I reuse the ovs_rpyapp.py to restart the openstack-openvswitch-agent.service, then the controller is ok can be connected by ovs.

So, whether this is a bug? or something I missed ?
Thanks a lot.

Tags: ovs ryu
Rong.Wang (stormflying)
tags: added: ryu
Revision history for this message
Tristan Cacqueray (tristan-cacqueray) wrote :

Removing the private setting since this doesn't describe a security bug.

information type: Private Security → Public
Rong.Wang (stormflying)
description: updated
description: updated
Revision history for this message
Rong.Wang (stormflying) wrote :

I confirmed how does this problem occurs.
Ryu (app/ofctl/api.py) uses the call stack to load the dependent-app('ryu.app.ofctl.service').
When ovs_ryuapp.py be compiled to pyc, the call stack changed and missed the stack of ovs_ryuapp.
So, the dependent-app will not be assigned to ovs_ryuapp, then the ofctl would not be loaded.
This may be the bug of Ryu, and NOT compile the ovs_ryuapp.py to pyc may avoid this problem.

Changed in neutron:
assignee: nobody → Rong.Wang (stormflying)
status: New → Confirmed
tags: added: ovs
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.