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]: milvus cluster cannot use tsl connec etcd custer #20868

Closed
1 task done
eliassama opened this issue Nov 28, 2022 · 5 comments
Closed
1 task done

[Bug]: milvus cluster cannot use tsl connec etcd custer #20868

eliassama opened this issue Nov 28, 2022 · 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.
Milestone

Comments

@eliassama
Copy link

eliassama commented Nov 28, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: v2.2.0
- Deployment mode(standalone or cluster): cluster
- SDK version(e.g. pymilvus v2.0.0rc2): @zilliz/milvus2-sdk-node@2.2.0
- OS(Ubuntu or CentOS): docker 
- CPU/Memory: 1C/1G
- GPU: 0
- Others:

Current Behavior

when i changed both etcd and pulsar to cluster mode, and etcd was connected using ssl, all the milvus services only showed what was on the image
image
image
image

my milvus config is:
image
image

my etcd config is:
image
image

if i use node.js example to connect, i get an error:
image

I think etcd is a problem, but as of now, none of these services have any ERROR logs.

when i set up earlier, i use etcd for single, nor did I use ssl encryption.

Expected Behavior

with etcd cluster and tsl enabled, the connection should work

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@eliassama eliassama 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 Nov 28, 2022
@eliassama eliassama changed the title [Bug]: [Bug]: milvus cluster cannot use tsl connec etcd custer Nov 28, 2022
@jiaoew1991
Copy link
Contributor

/assign
/unassign @yanliang567

@jiaoew1991 jiaoew1991 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 Nov 28, 2022
@yanliang567 yanliang567 added this to the 2.2.1 milestone Nov 30, 2022
@xiaofan-luan
Copy link
Contributor

/assign @eliassama feel free to test on day build

@sre-ci-robot
Copy link
Contributor

@xiaofan-luan: GitHub didn't allow me to assign the following users: test, on, day, build, feel, free, to.

Note that only milvus-io members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @eliassama feel free to test on day build

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.

@yanliang567
Copy link
Contributor

/assign @eliassama

@yanliang567 yanliang567 modified the milestones: 2.2.1, 2.2.2, 2.2.3 Dec 19, 2022
@stale
Copy link

stale bot commented Jan 23, 2023

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 Jan 23, 2023
@stale stale bot closed this as completed Jan 30, 2023
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