-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Reconciler error in Starrocks Operator (invalid: metadata.resourceVersion) | Latest Helm Chart #28626
Comments
can you provide following info?
|
Sure!
With theses steps I got the following:
and via ephemeral pod I got the backends:
By the other hand, there is a way to deploy Starrocks Cluster (FE & BE) without Starrocks Operator and CRD in Kubernetes? Thanks in advance! |
if you are using
This will give you a very basic cluster with no pvc for data persistency to play with.
You can try to do it your own with deployment or statefulset, but it is not recommended. Some one has a demo here if you are interested: StarRocks/demo#26 |
Thanks a lot for your quick answer. I will try with this way. Quick question, If I want to set a persistent volume I could set with the command install wright? |
either chart values or crd configuration, refer to https://github.com/StarRocks/starrocks-kubernetes-operator#optional-configuring-storage-volume, the "optional-configuring-storage-volume" section. |
Thanks! I will try with this way and comment by this loop if that's works |
I tried with the steps at https://artifacthub.io/packages/helm/kube-starrocks/kube-starrocks but unfortunately I got the same issue with
I don't understand where is the problem. Logs here:
|
probably, you need to uninstall all the resources including the crd, to get a clean env with no crd or operator installed, and then try again. @yandongxiao |
I have done just that, removed the first deployment with all its resources and including the CRD. What's more, this last deploy went directly to the Namespace Default.
|
In order to install starrocks in a specified namespace, like sr, you should execute |
The following log means the fileds of FE statefulset is updated, which is not allowed.
I think you forgot to execute |
Always execute this command The first time I created a namespace and then I unistalled the Helm realese of this namespace. The second time I tried with the steps at https://artifacthub.io/packages/helm/kube-starrocks/kube-starrocks in the default namespace. I will try again with you recomendation: [In order to install starrocks in a specified namespace, like sr, you should execute kubectl create ns sr; helm install -n sr starrocks starrocks-community/kube-starrocks.] |
I followed your recommendation: I've removed all deployments and launch again. I add my steps: ➜ ~
➜ ~
➜ ~
➜ ~
I got the same issue:
|
which k8s version are you using? |
Server Version: v1.21.6+vmware.1 |
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION Can you use the latest chart version v1.7.1 to try it? |
I deleted all then re-deployed and I got the same issue. I will try in minikube the next Monday. ~
|
I reproduce the error |
Many thanks! Could you please let me know about the change to pull it the new version? |
Ok |
is this a k8s version specific issue? |
I think so, in the v1.27.3, there is no such error in operator log |
StarRocks/starrocks-kubernetes-operator#214 This PR will included in starrocks-kubernetes-operator v1.8.0 which will be published in next week. |
Thanks a lot! |
Hey guys there is an update on this? I'm facing a similar issue |
Version 1.8.0 works well! |
General Question
I have an issue with the Starrocks Operator when apply the Starrocks Cluster with FE and BE. I add the Operator logs:
I0803 22:11:49.113850 1 starrockscluster_controller.go:83] StarRocksClusterReconciler reconcile the update crd name starrocks namespace kube-starrocks I0803 22:11:49.117336 1 statefulset.go:89] the statefulset name starrocks-fe new hash value 2344900785 old have value 3682884808 I0803 22:11:49.117483 1 k8sutils.go:94] Updating resource service namespace kube-starrocks name starrocks-fe kind &TypeMeta{Kind:,APIVersion:,} I0803 22:11:49.167775 1 k8sutils.go:94] Updating resource service namespace kube-starrocks name starrocks-fe-search kind &TypeMeta{Kind:,APIVersion:,} E0803 22:11:49.188632 1 fe_controller.go:111] FeController Sync create or patch internal service namespace kube-starrocks name starrocks-fe-search failed, message Service "starrocks-fe-search" is invalid: metadata.resourceVersion: Invalid value: "": must be specified for an update E0803 22:11:49.188697 1 starrockscluster_controller.go:111] StarRocksClusterReconciler reconcile sub resource reconcile failed, namespace=kube-starrocks, name=starrocks, controller=feController, error=Service "starrocks-fe-search" is invalid: metadata.resourceVersion: Invalid value: "": must be specified for an update 1.6911007091887467e+09 ERROR Reconciler error {"controller": "starrockscluster", "controllerGroup": "starrocks.com", "controllerKind": "StarRocksCluster", "StarRocksCluster": {"name":"starrocks","namespace":"kube-starrocks"}, "namespace": "kube-starrocks", "name": "starrocks", "reconcileID": "572f57e6-c84a-490b-a9fb-e11786f8711b", "error": "Service \"starrocks-fe-search\" is invalid: metadata.resourceVersion: Invalid value: \"\": must be specified for an update"} sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler /go/src/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:326 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem /go/src/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:273 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2 /go/src/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:234
The environment: Tanzu WmWare - Kubernetes
Could you please help me with this?
Thanks in advance.
The text was updated successfully, but these errors were encountered: