Bug 1758547
| Summary: | Stale namespace entries & neutron-netns-cleanup is failing | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ravi Singh <ravsingh> | |
| Component: | python-paunch | Assignee: | Rodolfo Alonso <ralonsoh> | |
| Status: | CLOSED ERRATA | QA Contact: | Eran Kuris <ekuris> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 13.0 (Queens) | CC: | agladkov, akaris, amuller, apevec, aschultz, atomlin, bcafarel, bdobreli, ccamposr, chrisw, cmuresan, dalvarez, david.costakos, dhill, ebiederm, fiezzi, gkadam, jbainbri, kiyyappa, knoha, ljozsa, ltamagno, mporrato, nchandek, njohnston, peli, pratik.bandarkar, ralonsoh, rcarrier, rcernin, rmalafai, sandyada, scohen, skaplons, slinaber, smeisner, tkajinam, tquinlan | |
| Target Milestone: | z10 | Keywords: | Reopened, Triaged, ZStream | |
| Target Release: | 13.0 (Queens) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | python-paunch-2.5.0-8.el7ost | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1771563 (view as bug list) | Environment: | ||
| Last Closed: | 2019-12-20 16:13:16 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: | 1760041, 1771556, 1772400 | |||
| Bug Blocks: | 1771563 | |||
|
Description
Ravi Singh
2019-10-04 13:32:47 UTC
kernel-3.10.0-1062.1.1.el7.x86_64 Sat Sep 14 05:48:05 2019 (In reply to Ravi Singh from comment #0) > How reproducible: > reproduced in lab > > Steps to Reproduce: > 1. > 2. > 3. Please provide instructions on how to reproduce. Devel can't fix something if we don't describe how to actually get the system into an error state. Hi Jamie, I am not sure how to reproduce this..since once customer reported issue..I saw the same in my environment & opened up this BZ. Please let me know if you want to have a look on my env. I suggest you continue to work on it, so that you can provide a set of steps which reproduce the issue from boot. Possible workaround for this issue: docker restart neutron_l3_agent; sleep 2; for i in $(ip netns 2>/dev/null | grep -v "id:" | sort); do docker exec -it -u 0 neutron_l3_agent ip netns delete $i; sleep 1; done; ip netns; docker restart neutron_l3_agent ; ip netns CU update ~~~ Hi Tim, David, We've been able to reproduce the issue without CrowdStrike installed. So we can disregard that as being a factor for now. Simply running the tempest neutron test scenarios is enough to see the namespaces go stale [1]. We also updated to z9 last night, it's the same issue on that release. [1] tempest run -r neutron ~~~ In tripleo, we've worked around this by creating a service that is started on boot which creates a placeholder namespace to ensure the folders are created with the created shared nature. This patch was landed in the Stein timeframe (https://review.rdoproject.org/r/#/c/17078/) in the paunch packaging. This patch assumes an updated version of iproute2 and pyroute2 which have the fixes for the shared nature. I've proposed a backport of this patch for upstream Queens/Rocky which already have the updated iproute packaging. I've taking this bug over for the paunch patch get it landed. We need to have https://bugzilla.redhat.com/show_bug.cgi?id=1771556 before the paunch patch will work correctly. changing to modify because we blocked to verify it. *** Bug 1571321 has been marked as a duplicate of this bug. *** *** Bug 1571321 has been marked as a duplicate of this bug. *** 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. https://access.redhat.com/errata/RHBA-2019:4335 |