Race condition for subnet-delete and subnet-create
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
When user has stopped rabbitmq-server and tries to create a subnet and delete that subnet , there is a race condition when rabbitmq-server is restarted, i.e. subnet-delete output is displaying first then later subnet-create output is displaying.
Steps to reproduce:-
1) In first terminal stop rabbitmq-server.
2) In second terminal create a subnet , there wont be any response to CLI , but there is a DB entry for subnet with <subnet_id> . This can be verified in other terminal by using "neutron subnet-list"
3) In Third terminal delete the subnet with that same <subnet_id> given in subnet-list. There wont be any response to CLI but the subnet gets deleted from DB. This can be verified in other terminal by using "neutron subnet-list"
4) Restart rabbitmq-server .
Here user can see that subnet-delete output is getting displayed first and then later subnet-create output is displayed. Here there is a race condition that delete output is displayed before create.
Tried reproducing the bug. I used the ocata stable version on ubuntu 16.04 to verify the same.
I could see the subnet create command is returning the output first and then the delete output(cursor returning not any text) is displayed which I think is the correct order.
Please verify and let me know if I am missing anything.