Description
When testing running two test sessions at the same time, they were both using the EHN1 connectivity service. As such, when I used the same session name in both configs (testsession in both cases)
# In shell 1
drunc-unified-shell ssh-standalone config/daqsystemtest/example-configs.data.xml ehn1-local-1x1-config testsession
# In shell 2
drunc-unified-shell ssh-standalone config/daqsystemtest/example-configs.data.xml ehn1-local-1x1-config testsession
The second session connected to the applications running from the first session. A simple flask endpoint to verify that the session name is unused could be useful.
Note - for FD, this is intended to be handled by the session manager, but this safety catch would be helpful too.
Potential impact radius
Small/Isolated
Reason for change
Session safety.
Suggested implementations
No response
Testing suggestions
No response
Anything else?
No response
Description
When testing running two test sessions at the same time, they were both using the EHN1 connectivity service. As such, when I used the same session name in both configs (
testsessionin both cases)# In shell 1 drunc-unified-shell ssh-standalone config/daqsystemtest/example-configs.data.xml ehn1-local-1x1-config testsession# In shell 2 drunc-unified-shell ssh-standalone config/daqsystemtest/example-configs.data.xml ehn1-local-1x1-config testsessionThe second session connected to the applications running from the first session. A simple flask endpoint to verify that the session name is unused could be useful.
Note - for FD, this is intended to be handled by the session manager, but this safety catch would be helpful too.
Potential impact radius
Small/Isolated
Reason for change
Session safety.
Suggested implementations
No response
Testing suggestions
No response
Anything else?
No response