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