Closed chaoyoung closed 1 year ago
It seems that something is wrong with RBAC. Please check if role.xml, role_binding.yaml and service_account.yaml are the latest version and successfully applied.
E1109 10:10:55.758673 1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.1/tools/cache/reflector.go:167: Failed to watch *v1.Pod: failed to list *v1.Pod: pods is forbidden: User "system:serviceaccount:default:default" cannot list resource "pods" in API group "" at the cluster scope
It seems that something is wrong with RBAC. Please check if role.xml, role_binding.yaml and service_account.yaml are the latest version and successfully applied.
E1109 10:10:55.758673 1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.1/tools/cache/reflector.go:167: Failed to watch *v1.Pod: failed to list *v1.Pod: pods is forbidden: User "system:serviceaccount:default:default" cannot list resource "pods" in API group "" at the cluster scope
name-server and broker are running after redeploy, but console pod not found, rocketmq-operator contains error log:
2022-11-10T04:07:05.204Z ERROR controller_broker Failed to update Broker Size status. {"Request.Namespace": "default", "Request.Name": "broker", "error": "Broker.rocketmq.apache.org \"broker\" is invalid: status.nodes: Required value"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.0/pkg/internal/controller/controller.go:266
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.0/pkg/internal/controller/controller.go:227
name-server and broker are running after redeploy, but console pod not found, rocketmq-operator contains error log:
Are there any error messages about rocketmq-console?
name-server and broker are running after redeploy, but console pod not found, rocketmq-operator contains error log:
Are there any error messages about rocketmq-console?
It should be rocketmq-operator
unable to recognize affinity
field I added.
[root@dev-k8s-master1 rocketmq-operator]# k apply -f rocketmq_v1alpha1_rocketmq_cluster.yaml
configmap/broker-config created
broker.rocketmq.apache.org/broker created
nameservice.rocketmq.apache.org/name-service created
error: error validating "rocketmq_v1alpha1_rocketmq_cluster.yaml": error validating data: ValidationError(Console.spec): unknown field "affinity" in org.apache.rocketmq.v1alpha1.Console.spec; if you choose to ignore these errors, turn validation off with --validate=false
name-server and broker are running after redeploy, but console pod not found, rocketmq-operator contains error log:
Are there any error messages about rocketmq-console?
It should be
rocketmq-operator
unable to recognizeaffinity
field I added.[root@dev-k8s-master1 rocketmq-operator]# k apply -f rocketmq_v1alpha1_rocketmq_cluster.yaml configmap/broker-config created broker.rocketmq.apache.org/broker created nameservice.rocketmq.apache.org/name-service created error: error validating "rocketmq_v1alpha1_rocketmq_cluster.yaml": error validating data: ValidationError(Console.spec): unknown field "affinity" in org.apache.rocketmq.v1alpha1.Console.spec; if you choose to ignore these errors, turn validation off with --validate=false
BUG REPORT
Please describe the issue you observed:
What did you do (The steps to reproduce)?
What did you expect to see?
What did you see instead?
rocketmq-operator-5b59b6f6f8-gzkvw
print errorsbroker-0-master-0
print errorsname-service-0
print errorsPlease tell us about your environment:
k8s version: 1.24.6 rocketmq-operator version: 0.4.0 rocketmq version: 5.0.0
Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):
console pod not found and pod
rocketmq-operator-5b59b6f6f8-gzkvw
print the following errors:pod
broker-0-master-0
print the following errors:pod
name-service-0
print the following errors: