devstack leaves stale .pyc files around

Bug #1275967 reported by Steve Loranz
50
This bug affects 11 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Low
Steve Loranz
devstack
Invalid
Undecided
Unassigned

Bug Description

nova was recently ported to oslo.incubator. This results in devstack raising an exception about duplicate rpc_backend options being registered. The problem is that openstack/common/service.py was not updated as part of that work.

Changed in nova:
assignee: nobody → Steve Loranz (steveloranz)
Michael Still (mikal)
Changed in nova:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Christian Martinez (christian-martinez) wrote :

Hi,

Do you know of any workarounds on this (at least until the patch is released)?

Thanks,
Christian

Changed in nova:
status: Triaged → In Progress
Revision history for this message
Mark McLoughlin (markmc) wrote :

AFAICT the real issue here is that devstack doesn't clean up stale .pyc files

summary: - duplicate rpc_backend registration
+ devstack leaves stale .pyc files around
Mark McLoughlin (markmc)
Changed in nova:
status: In Progress → Invalid
Revision history for this message
Liusheng (liusheng) wrote :

Mark McLoughlin (markmc) is right.
Even though I haven't find the stale .pyc files should be remove, I used the following command in /opt/stack/nova/ removing all the .pyc files.
find . -name *.pyc -exec rm {} \;
Then, I run:
./unstack.sh
./stack.sh

This problem is solved.

Revision history for this message
Khanh-Toan TRAN (toan-tran) wrote :

Thanks Liusheng. That works!

Actually we don't need unstack, just restart the nova deamons is enough. I still do not know which pyc cause this problem.

Revision history for this message
Vui Lam (vui) wrote :

+1 on the .pyc removal. For the OP's problem, the culprit was nova/openstack/common/rpc/__init__.pyc.

Revision history for this message
Sean Dague (sdague) wrote :

This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.

Changed in devstack:
status: New → Invalid
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.