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

[Bug]: 是不是内置ETCD和外部ETCD都无法启用auth呀,我试了外部的也一样连不上 #29718

Closed
1 task done
chjohnhuang123456 opened this issue Jan 5, 2024 · 5 comments
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@chjohnhuang123456
Copy link

chjohnhuang123456 commented Jan 5, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:2.3.2
- Deployment mode(standalone or cluster): cluster-helm-deploy(cpu)
- MQ type(rocksmq, pulsar or kafka):    pulsar
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): centos
- CPU/Memory: 512G
- GPU: 
- Others:

Current Behavior

我用外部etcd配置:

externalEtcd:
  enabled: true
  ## the endpoints of the external etcd
  ##
  endpoints:
    - 10.140.177.73:2379
  user: "root"
  password: "Jxlz2020."

和helm内置配置:

auth:
  ## Role-based access control parameters
  ## ref: https://etcd.io/docs/current/op-guide/authentication/
  ##
  rbac:
    ## @param auth.rbac.enabled Switch to enable RBAC authentication
    ##
    enabled: true
    ## @param auth.rbac.allowNoneAuthentication Allow to use etcd without configuring RBAC authentication
    ##
    allowNoneAuthentication: true
    ## @param auth.rbac.rootPassword Root user password. The root user is always `root`
    ##
    rootPassword: "Jxlz2020."
    userName: "root"
    ## @param auth.rbac.existingSecret Name of the existing secret containing credentials for the root user
    ##
    existingSecret: ""
  ## TLS authentication for client-to-server communications
  ## ref: https://etcd.io/docs/current/op-guide/security/

其他微服务都连不上etcd,报错:

[2024/01/05 07:43:23.845 +00:00] [ERROR] [sessionutil/session_util.go:255] ["retry func failed"] ["retry time"=44] [error="etcdserver: user name is empty"] [stack="github.com/milvus-io/milvus/internal/util/sessionutil.NewSession\n\t/go/src/github.com/milvus-io/milvus/internal/util/sessionutil/session_util.go:255\ngithub.com/milvus-io/milvus/internal/distributed/rootcoord/client.NewClient\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/rootcoord/client/client.go:57\ngithub.com/milvus-io/milvus/internal/distributed/datanode.NewServer.func1\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/datanode/service.go:86\ngithub.com/milvus-io/milvus/internal/distributed/datanode.(*Server).init\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/datanode/service.go:256\ngithub.com/milvus-io/milvus/internal/distributed/datanode.(*Server).Run\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/datanode/service.go:188\ngithub.com/milvus-io/milvus/cmd/components.(*DataNode).Run\n\t/go/src/github.com/milvus-io/milvus/cmd/components/data_node.go:53\ngithub.com/milvus-io/milvus/cmd/roles.runComponent[...].func1\n\t/go/src/github.com/milvus-io/milvus/cmd/roles/roles.go:113"]
[2024/01/05 07:43:26.846 +00:00] [DEBUG] [sessionutil/session_util.go:246] ["Session try to connect to etcd"]
{"level":"warn","ts":"2024-01-05T07:43:26.847Z","logger":"etcd-client","caller":"v3@v3.5.5/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc0002a56c0/10.140.177.73:2379","attempt":0,"error":"rpc error: code = InvalidArgument desc = etcdserver: user name is empty"}

Expected Behavior

在helm的milvus.yaml配置完用户名密码之后可以启用etcd auth

Steps To Reproduce

No response

Milvus Log

[2024/01/05 07:43:23.845 +00:00] [ERROR] [sessionutil/session_util.go:255] ["retry func failed"] ["retry time"=44] [error="etcdserver: user name is empty"] [stack="github.com/milvus-io/milvus/internal/util/sessionutil.NewSession\n\t/go/src/github.com/milvus-io/milvus/internal/util/sessionutil/session_util.go:255\ngithub.com/milvus-io/milvus/internal/distributed/rootcoord/client.NewClient\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/rootcoord/client/client.go:57\ngithub.com/milvus-io/milvus/internal/distributed/datanode.NewServer.func1\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/datanode/service.go:86\ngithub.com/milvus-io/milvus/internal/distributed/datanode.(*Server).init\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/datanode/service.go:256\ngithub.com/milvus-io/milvus/internal/distributed/datanode.(*Server).Run\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/datanode/service.go:188\ngithub.com/milvus-io/milvus/cmd/components.(*DataNode).Run\n\t/go/src/github.com/milvus-io/milvus/cmd/components/data_node.go:53\ngithub.com/milvus-io/milvus/cmd/roles.runComponent[...].func1\n\t/go/src/github.com/milvus-io/milvus/cmd/roles/roles.go:113"]
[2024/01/05 07:43:26.846 +00:00] [DEBUG] [sessionutil/session_util.go:246] ["Session try to connect to etcd"]
{"level":"warn","ts":"2024-01-05T07:43:26.847Z","logger":"etcd-client","caller":"v3@v3.5.5/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc0002a56c0/10.140.177.73:2379","attempt":0,"error":"rpc error: code = InvalidArgument desc = etcdserver: user name is empty"}

Anything else?

No response

@chjohnhuang123456 chjohnhuang123456 added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 5, 2024
Copy link
Contributor

github-actions bot commented Jan 5, 2024

The title and description of this issue contains Chinese. Please use English to describe your issue.

@xiaofan-luan
Copy link
Collaborator

/assign @smellthemoon
please help on this

@PowderLi
Copy link
Contributor

PowderLi commented Jan 6, 2024

related to #28895

@yanliang567
Copy link
Contributor

/unassign

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 8, 2024
Copy link

stale bot commented Feb 8, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Feb 8, 2024
@stale stale bot closed this as completed Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

5 participants