$ ip netns does not display anything on Controller

[Juan Carlos Alonso]

Title
-----

$ 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.

Severity
--------

<Major: System/Feature is usable but degraded>

Steps to Reproduce
------------------

$ ip netns

Expected Behavior
------------------

$ ip netns
qdhcp-<net-id>

Actual Behavior
----------------

$ ip netns
----

Reproducibility
---------------

100%

System Configuration
--------------------

Multinode Local Storage Virtual Environment

[Juan Carlos Alonso (juancarlosa)]

Question,

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)]

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.

[Juan Carlos Alonso (juancarlosa)]

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.