Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVMfRemoteControllerConnect to return error or modify connection incase the connection already exists #66

Open
harshitap26 opened this issue Dec 7, 2022 · 2 comments

Comments

@harshitap26
Copy link

If we make a connection using an ID that is already used, but using a different target address, it gives a success response, but does not show it in NVMfRemoteControllerList

Example -
If the first connection is made using Id as 1 and target address as 10.0.0.1
Next time if I use the same Id as 1, but a different target address (10.0.0.2), it gives a success response but does not list the other connection.

The NVMfRemoteControllerConnect should return an error or should modify connection incase the connection already exists

@glimchb
Copy link
Member

glimchb commented Dec 7, 2022

@harshitap26 can you please attach docker-compose logs ?

@glimchb
Copy link
Member

glimchb commented Dec 7, 2022

the first part was done using #67 by adding ObjectKey to each request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants