Abraham, I guess I got confused as to why you are updating this bug report. Is there a reason you are trying to reproduce this issue? It's already noted in the notes that it is not 100% reproducible on all systems, so the fact that you cannot reproduce it doesn't mean there is no issue. The issue is also only specific to ovs-dpdk deployments (hence my first comment to you as it wasn't clear what vswitch backend you are using).
Anyway, to answer your question, yes you can change the cpu assignment for vswitch using a lock/unlock.
Abraham, I guess I got confused as to why you are updating this bug report. Is there a reason you are trying to reproduce this issue? It's already noted in the notes that it is not 100% reproducible on all systems, so the fact that you cannot reproduce it doesn't mean there is no issue. The issue is also only specific to ovs-dpdk deployments (hence my first comment to you as it wasn't clear what vswitch backend you are using).
Anyway, to answer your question, yes you can change the cpu assignment for vswitch using a lock/unlock.