$ ip netns does not display anything on Controller

Bug #1799591 reported by Juan Carlos Alonso on 2018-10-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Allain Legacy

Bug Description


$ ip netns command does not display anything on controller

Brief Description

`ip netns` command does not display anything on controller, so namespaces cannot be used and cannot ping an instance or make ssh to an instance from the controller.


<Major: System/Feature is usable but degraded>

Steps to Reproduce

$ ip netns

Expected Behavior

$ ip netns

Actual Behavior

$ ip netns



System Configuration

Multinode Local Storage Virtual Environment

description: updated
summary: - $ ip netns does not display anything
+ $ ip netns does not display anything on Controller
description: updated


Is it expected to make a ping or ssh to an instance from an active controller?
I ask because I could from a compute to an instance.

Ghada Khalil (gkhalil) wrote :

This is already explained in https://bugs.launchpad.net/starlingx/+bug/1797217
Network namespaces are created and managed by Neutron agents which are only scheduled on compute nodes or all-in-one controller nodes. In this report, the configuration is multi-node, so the controllers will not have any neutron agents scheduled on them.

Please refer to the above bug for more information about namespaces. Namespaces should not be directly used for end-to-end testing.

tags: added: stx.networking
Changed in starlingx:
assignee: nobody → Allain Legacy (alegacy)
importance: Undecided → Low
status: New → Invalid

On compute nodes $ ip netns can display content and can ping/ssh instances, so the corresponding test should be updated to indicate the restrictions.

Then I think this issue should be closed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers