namespace is not reassigned on swact
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Invalid
|
Low
|
Allain Legacy |
Bug Description
Title
-----
Namespace created on controller is not reassigned when doing a swact
Brief Description
-----------------
When a network is created also a namespace should be created in order to ping the VMs by namespace, currently the namespace is created but when doing a swact the namspace remains assigned to the previous controller and on the active controller no namespace is available.
Severity
--------
Provide the severity of the defect.
Major
Steps to Reproduce
------------------
1. On active controller create a net and a subnet
$ openstack network create test-net --shared
$ penstack subnet create --network test-net --subnet-range 192.168.0.0/24 --ip-version 4 --dhcp test-subnet
2. Verify that a namespace is created with the id of the network
$ sudo ip netns
qdhcp-
3. Perform a swact on active controller
$ system host-swact <controller_X>
4. Wain until swact is completed
5. On Controller active (controler-Y) execute command
$ sudo ip netns
Expected Behavior
------------------
namespace should be re created after the swact on the new active controller
Actual Behavior
----------------
namespace is not being re-created after the swact on teh new active controller
Reproducibility
---------------
Reproducible
System Configuration
-------
Duplex Bare-Metal Two node system
Branch/Pull Time/Commit
-------
r-2018-.10
Network
Timestamp/Logs
--------------
tags: | added: stx.2018.10 |
Changed in starlingx: | |
assignee: | nobody → Allain Legacy (alegacy) |
tags: | added: stx.networking |
summary: |
- namespace is not reasgined on swact + namespace is not reassigned on swact |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: |
added: stx.1.0 removed: stx.2018.10 |
The expected behavior is incorrect. Network namespaces are created and managed by Neutron agents. They are not directly affected by a controller swact. A namespace will only move from one node to a different node if the resource that created it moves to a different node.
Network namespaces are a part of the internal infrastructure needed to allow agents to have connectivity to VM instances attached to a particular tenant network. They are not intended as a means for end users to access tenant networks for the purposes of pinging or SSHing to VM instances. Networking developers, for debugging purposes, may make direct use of namespaces to test connectivity to/from various resources, but end users (and formal tests) should not make use of namespaces.