kubernetes-retired/external-storage

is there has a necessary that return InitiatorName, if DiscoveryCHAPAuth was enabled

DeepLJH0001 opened this issue · 7 comments

https://github.com/kubernetes-incubator/external-storage/blob/a6c939cac809c94d341f107e499091efebf8fda3/iscsi/targetd/provisioner/iscsi-provisioner.go#L149-L160

I just have a little confused,
when the DiscoveryCHAPAuth was enabled, how kubelet know the correct InitiatorName?
is there has a bug?

https://github.com/kubernetes-csi/drivers/blob/907b108b4f7cfb6323413cdb8b740d4fcea2b68a/pkg/iscsi/iscsi_util.go#L183-L193

ref this, if the discovery was enable, miss this may cause kubelet can't discover iscsi session

/label bug

@DeepLJH0001: The label(s) /label bug cannot be applied. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other

In response to this:

/label bug

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.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.