-
Notifications
You must be signed in to change notification settings - Fork 39k
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
iscsi storage plugin only logs out of primary portal #45394
Comments
@humblec Want me to fix this or is there other work in the pipeline? |
I am also seeing this issue. Although in my case I am not using the multiple target addresses, but my iscsi equipment (equallogic) load balances you to another portal ip.
|
I also hit this problem. I have a plan to post a fix. |
@mtanino: Reiterating the mentions to trigger a notification: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@rootfs, PTAL |
When using iscsi storage with multiple target portal (TP) addresses and multipathing the volume manager logs on to the IQN for all portal addresses, but when a pod gets destroyed the volume manager only logs out for the primary TP and sessions for another TPs are always remained. This patch adds methods to store and load iscsi disk configrations, then uses the stored config at DetachDisk path. Fix kubernetes#45394
Automatic merge from submit-queue Log out from multiple target portals when using iscsi storage plugin **What this PR does / why we need it**: When using iscsi storage with multiple target portal (TP) addresses and multipathing the volume manager logs on to the IQN for all portal addresses, but when a pod gets destroyed the volume manager only logs out for the primary TP and sessions for another TPs are always remained. This patch adds mount points for all TPs, and then log out from all TPs when a pod is destroyed. If a TP is referred from another pods, the connection will be remained as usual. **Which issue this PR fixes** fixes #45394 **Special notes for your reviewer**: **Release note**: ``` NONE ```
When using iscsi storage with multiple target portal (TP) addresses and multipathing the volume manager logs on to the IQN for all portal addresses, but when a pod gets destroyed the volume manager only logs out for the primary TP and sessions for another TPs are always remained. This patch adds methods to store and load iscsi disk configrations, then uses the stored config at DetachDisk path. Fix kubernetes#45394
When using iscsi storage with multiple target portal (TP) addresses and multipathing the volume manager logs on to the IQN for all portal addresses, but when a pod gets destroyed the volume manager only logs out for the primary TP and sessions for another TPs are always remained. This patch adds methods to store and load iscsi disk configrations, then uses the stored config at DetachDisk path. Fix kubernetes#45394
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): iscsi
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG
Kubernetes version (use
kubectl version
): v1.6.0Environment:
uname -a
): Linux srv02 3.10.0-514.2.2.el7.x86_64 Unit test coverage in Kubelet is lousy. (~30%) #1 SMP Tue Dec 6 23:06:41 UTC 2016 x86_64 x86_64 x86_64 GNU/LinuxWhat happened:
When using iscsi storage with multiple target portal (TP) addresses + multipathing the volume manager
logs on to the IQN for all portal addresses, but when a pod gets destroyed the volume manager only logs out for the primary TP. This leaves a session dangling and the pod using the volume can't start as the SAN doesn't allow multiple hosts to connect to the same IQN
What you expected to happen:
The DetachDisk method in iscsi_utils.go should do the same as the AttachDisk which is to
iterate over all portals and log out from all of them.
Alternatively omit the -p command line to iscsiadm to log out all references to the IQN
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
The text was updated successfully, but these errors were encountered: