Bug 1022578
Summary: | quantum-ovs-cleanup delete the port that nova compute has plugged into an tap interface | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Scott Lewis <sclewis> |
Component: | openstack-quantum | Assignee: | Solly Ross <sross> |
Status: | CLOSED ERRATA | QA Contact: | Ofer Blaut <oblaut> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.0 | CC: | ajeain, apevec, breeler, chrisw, dallan, lpeer, ndipanov, oblaut, pbrady, sradvan, sross, twilson, wenjianhn, xqueralt, yeylon |
Target Milestone: | z4 | Keywords: | ZStream |
Target Release: | 3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | network | ||
Fixed In Version: | openstack-quantum-2013.1.4-3.el6ost | Doc Type: | Bug Fix |
Doc Text: |
Cause: The ovs cleanup script would exit before its operations finished.
Consequence: When restarting services, it was possible that OVS cleanup would remove devices needed by newly restarted services.
Fix: Ensure that the ovs cleanup script does not exit before completion.
Result: OVS cleanup does not delete devices that are created after it is run.
|
Story Points: | --- |
Clone Of: | 1010941 | Environment: | |
Last Closed: | 2014-01-30 19:49:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1010941 | ||
Bug Blocks: |
Comment 3
Ofer Blaut
2013-10-31 14:08:30 UTC
Can't validate the bug , it is not working Ofer: the steps to reproduce are how to produce the error artificially, in a way that would never happen normally. Testing shouldn't be by the above steps to reproduce, but instead should just verify that normal startup doesn't fail. The fix for this was to make sure that the scripts, when running with their normal priorities, don't occasionally fail due to the race condition that existed because daemon launched the OVS cleanup utility in a non-blocking way which could break nova if it ended up running afterward. As it was a race condition, the only way to really try it out would be to go through lots of reboots. This shouldn't have been removed from z-stream in my opinion. Hi Terry, the normal start up works, i just followed the reproduce steps as required . As i mentioned in my comments from "comment from Ofer Blaut on 2013-10-23" i was not sure about the steps. Since our nova.conf default is "resume_guests_state_on_host_boot=False" I will change it to True and reboot the hosts to check it out . I have tried few times with start_guests_on_host_boot=True Can't get the VMS UP after boot I have just checked it, The reproduction steps are 1. stop ovs-agent 2. stop nova-compute 3. run cleanup 4. start ovs-agent 5. start nova-compute Only after restarting nova compute the interfaces are back already tested ( see comment 12 ) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0110.html |