Bug 973754 – Unable to access namespace after a deletion has failed

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 973754 - Unable to access namespace after a deletion has failed [NEEDINFO]

Summary:	Unable to access namespace after a deletion has failed

Status:	CLOSED INSUFFICIENT_DATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	kernel (Show other bugs)
Sub Component:
Version:	3.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	4.0
Assigned To:	Don Howard
QA Contact:	Ami Jeain
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-06-12 11:45 EDT by Gary Kotton
Modified:	2016-04-26 09:28 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2013-10-23 07:23:19 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	tgraf: needinfo? (gkotton)

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Gary Kotton 2013-06-12 11:45:30 EDT

Description of problem:
If the deleteion of a namespace fails (for example run  quantum-netns-cleanup --force), then one is unable to access the namsepace from that moment on:

[root@dhcp-4-126 ~]# ip netns exec qdhcp-412dc916-6975-4956-9be0-0dac739657e0 ip link
seting the network namespace failed: Invalid argument


Version-Release number of selected component (if applicable):
Linux dhcp-4-126.tlv.redhat.com 2.6.32-358.6.2.openstack.el6.x86_64 #1 SMP Wed May 29 19:20:22 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:
Every time

Steps to Reproduce:
1. Ensure that dhcp agent has created namespace
2. Run  quantum-netns-cleanup --force (this fails with deletion of namespace)
3. Try and access namespace

Actual results:


Expected results:


Additional info:

Comment 2 Thomas Graf 2013-06-17 10:43:57 EDT

Can you somehow reproduce that without the use of quantum? I can't get the namespace deletion to fail.

Note You need to log in before you can comment on or make changes to this bug.