Closed catherinemeadows closed 3 years ago
@bdevierno1 this might be a fix that can be included in your PR
Yea this ones on me - when I moved the NF ring allocation from the manager to the NF, I didn't account for the fact thats rings need to be allocated from a secondary process. In my latest PR (NF pool) i wrote a function that allocates a single ring from the manager using a NF -> manager communication mechanism. When we merge that we should fix this issue by having the NF use that function whenever allocating the ring.
Fixed from merge in #272
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:
and the NF hangs on
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:
Terminate with Ctrl + C and relaunch:
The same error occurs when re-launching an NF with the same instance ID but a different service ID:
Terminate with Ctrl + C and relaunch:
Environment
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: