[Bug]: MountVolume.SetUp failed for volume "cert" : secret "milvus-operator-webhook-cert" not found about milvus HOT 7 CLOSED

@haorenfsa can you help to take a look?

from milvus.

Hi @gaoyuan5251, are you using Alicloud's ACK? please refer to this issue #21961.

follow the instructions from this comment #21961 (comment)

你好 @gaoyuan5251，你是在使用Alicloud的ACK吗？ 请参考#21961 这个issue . 跟着这条评论的说明来 #21961 (comment)

from milvus.

TODO： add FAQ doc for this kind of issue.
/assign

from milvus.

TODO： add FAQ doc for this kind of issue. /assign

Hi @gaoyuan5251, are you using Alicloud's ACK? please refer to this issue #21961.

follow the instructions from this comment #21961 (comment)

你好 @gaoyuan5251，你是在使用Alicloud的ACK吗？ 请参考#21961 这个issue . 跟着这条评论的说明来 #21961 (comment)

@haorenfsa operator 按照指示可以运行，但是milvus-standalone v2.3.1 仍然不能安装/。
kubectl get po -A
NAMESPACE NAME READY STATUS RESTARTS AGE
cert-manager cert-manager-6888d6b69b-vp7ss 1/1 Running 0 20h
cert-manager cert-manager-cainjector-76f7798c9-gd78m 1/1 Running 0 20h
cert-manager cert-manager-webhook-7d4b5d8484-4dkks 1/1 Running 0 20h
default nfs-client-provisioner-6b8547fdf4-cv97z 1/1 Running 0 41h
hll-etcd etcd-0 1/1 Running 0 24h
hll-etcd etcd-1 1/1 Running 0 24h
hll-etcd etcd-2 1/1 Running 1 (24h ago) 24h
hll-minio hll-milvus-pool-0-0 2/2 Running 0 23h
hll-minio hll-milvus-pool-0-1 2/2 Running 0 23h
hll-minio hll-milvus-pool-0-2 2/2 Running 0 23h
hll-minio hll-milvus-pool-0-3 2/2 Running 0 23h
ingress-nginx ingress-nginx-admission-create-m4p76 0/1 Completed 0 41h
ingress-nginx ingress-nginx-admission-patch-h46tc 0/1 Completed 3 41h
ingress-nginx ingress-nginx-controller-8c9449dbf-6txjh 1/1 Running 0 41h
kube-system calico-kube-controllers-595b58b579-vx24b 1/1 Running 0 2d16h
kube-system calico-node-887jl 1/1 Running 0 2d16h
kube-system calico-node-dmnf6 0/1 Running 0 2d16h
kube-system calico-node-fch7c 1/1 Running 0 2d16h
kube-system calico-node-gtzkj 1/1 Running 0 2d16h
kube-system coredns-6d8c4cb4d-fbgm4 1/1 Running 0 2d16h
kube-system coredns-6d8c4cb4d-z76bc 1/1 Running 0 2d16h
kube-system etcd-aly-hn1-inner-risk-graph-service-svc-stg-001 1/1 Running 59 2d16h
kube-system kube-apiserver-aly-hn1-inner-risk-graph-service-svc-stg-001 1/1 Running 0 41h
kube-system kube-controller-manager-aly-hn1-inner-risk-graph-service-svc-stg-001 1/1 Running 5097 2d16h
kube-system kube-proxy-7klhg 1/1 Running 0 2d16h
kube-system kube-proxy-98clm 1/1 Running 0 2d16h
kube-system kube-proxy-crqs6 1/1 Running 0 2d16h
kube-system kube-proxy-l4dsx 1/1 Running 0 2d16h
kube-system kube-scheduler-aly-hn1-inner-risk-graph-service-svc-stg-001 1/1 Running 4986 2d16h
milvus-operator milvus-operator-6f578f564f-77sdm 1/1 Running 0 16m
minio-operator console-576dbcc6b7-5bbz4 1/1 Running 0 42h
minio-operator minio-operator-76f469d84b-bzz9b 1/1 Running 0 42h
minio-operator minio-operator-76f469d84b-q599p 1/1 Running 1 (41h ago) 42h

日志：
kubectl logs milvus-operator-6f578f564f-77sdm -n milvus-operator -f

2024-06-14T02:30:44.851Z ERROR controller-runtime.manager.controller.milvus Reconciler error {"reconciler group": "milvus.io", "reconciler kind": "Milvus", "name": "hll-release", "namespace": "hll-milvus-stg", "error": "Operation cannot be fulfilled on milvuses.milvus.io "hll-release": the object has been modified; please apply your changes to the latest version and try again"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:253
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:214

from milvus.

milvus-operator milvus-operator-6f578f564f-77sdm 1/1 Running 0 16m

@haorenfsa 我的milvus.yaml

apiVersion: v1
kind: Secret
metadata:
name: hll-release-minio-secret
namespace: hll-milvus
type: Opaque
stringData:
accesskey: ***
secretkey: ***

apiVersion: milvus.io/v1beta1
kind: Milvus
metadata:
name: hll-release
labels:
app: milvus
namespace: hll-milvus-stg

spec:
mode: standalone
config:
common:
security:
tlsEnabled: false
etcd:
rootPath: hll-release
msgChannel:
chanNamePrefix:
cluster: hll-release
minio:
bucketName: hll-milvus
rootPath: milvus/hll-release
useSSL: false
components:
image: milvusdb/milvus:v2.4.1
nodeSelector:
disktype: ssd
standalone:
replicas: 1
serviceType: LoadBalancer
dependencies:
etcd:
external: true
endpoints: ["etcd.hll-etcd.svc.cluster.local:2379"]
storage:
external: true
endpoint: *****:80
secretRef: hll-release-minio-secret
type: MinIO

from milvus.

so what is the new error msg? if Milvus fails to start, please help to attach the full milvus logs. please refer this doc to export the whole Milvus logs for investigation

/assign @gaoyuan5251
/unassign

from milvus.

so what is the new error msg? if Milvus fails to start, please help to attach the full milvus logs. please refer this doc to export the whole Milvus logs for investigation

@yanliang DONE

from milvus.