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]: Pods fail with permission denied error "failed: open /milvus/configs/milvus.yaml: permission denied" #33057

Open
1 task done
edwardquarm opened this issue May 14, 2024 · 1 comment
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@edwardquarm
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:v2.4.1
- Deployment mode(standalone or cluster): cluster
- MQ type(rocksmq, pulsar or kafka): pulsar    
- SDK version(e.g. pymilvus v2.0.0rc2): 2.4.1
- OS(Ubuntu or CentOS): Ubuntu
- CPU/Memory: 
- GPU:
- Others:

Current Behavior

When I try to install milvus helm chart on GKE standard cluster, the following pods go into CrashLoopBackOff

  • datacoord
  • datanode
  • indexcoord
  • indexnode
  • proxy
  • pulsar-bookie-init
  • querycoord
  • querynode
  • rootcoord

The pods fail with the message: write failed: open /milvus/configs/milvus.yaml: permission denied
It appears that this issue was reported by another user and fixed here: #22516
However, I'm encountering the same issue.

Expected Behavior

Milvus should get deployed to GKE standard cluster

Steps To Reproduce

helm repo add zilliztech https://zilliztech.github.io/milvus-helm
helm repo update
helm install milvus zilliztech/milvus -n platform

Milvus Log

No response

Anything else?

No response

@edwardquarm edwardquarm 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 May 14, 2024
@yanliang567
Copy link
Contributor

/assign @LoveEachDay
please help to take a look
/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 May 15, 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 triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants