Unable to re-launch NF with same instance ID #233
Description
Bug Report
Current Behavior
When re-launching an NF with the same instance ID (from either command line or from a JSON config file), the manager exits with the errors:
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
EAL: Error - exiting with code: 1
Cause: Cannot create rx ring queue for NF 1
and the NF hangs on
APP: Waiting for manager to assign an ID...
This bug occurs when re-launching an NF with the same instance ID (even if the service ID is changed).
Expected behavior/code
NFs should successfully re-launch if assigned the same instance ID as a prior launch.
Steps to reproduce
Launch NF with specified instance ID (either command line or from a JSON config file), terminal with Ctrl+C, and re-launch with the same instance ID.
Command line instructions for running speed_tester:
$ ./go.sh -- -n 1 -r 1 -- -d 2
Terminate with Ctrl + C and relaunch:
$ ./go.sh -- -n 1 -r 1 -- -d 2
The same error occurs when re-launching an NF with the same instance ID but a different service ID:
$ ./go.sh -- -n 1 -r 1 -- -d 2
Terminate with Ctrl + C and relaunch:
$ ./go.sh -- -n 1 -r 2 -- -d 2
Environment
- OS: Ubuntu 18.04
- onvm version: 20.05
Possible Solution
Make sure rings are being freed on NF shutdown
Additional context/Screenshots
The screenshot shows the result of trying to re-launch speed_tester from a JSON config file with the same instance ID as the first successful launch:
$ ./go.sh -F ../example_config.json -- -- -d 1
$ Ctrl + C
$ ./go.sh -F ../example_config.json -- -- -d 1
