-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(bors): merge pull request #912
912: fix(ha-node): use transport info from nvme connect response r=dsharma-dc a=dsharma-dc With tcpFallback option enabled, the csi-node can make a decision to connect an rdma capable target over tcp if the initiator is not rdma capable. However, after the NvmeConnectResponse is received at ha-node, the ha-node doesn't know that fallback could've happened. The ha-node blindly goes ahead validating the new path presence by matching using rdma transport parsed from target uri, which it doesn't find because new path got connected over tcp. This cascades a SubsystemNotFound error up to ha-cluster agent that reinitiates republish and keeps looping in same problem. This fix passes the actual transport used for connect info from csi-node to ha-node in NvmeConnectResponse, letting ha-node validate using accurate transport. Co-authored-by: Diwakar Sharma <[email protected]>
- Loading branch information
Showing
7 changed files
with
83 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters