victorgkang opened a new issue, #219:
URL: https://github.com/apache/rocketmq-operator/issues/219

   This is my topictransfer.yaml
   apiVersion: rocketmq.apache.org/v1alpha1
   kind: TopicTransfer
   metadata:
     annotations:
       meta.helm.sh/release-name: rocketmq
       meta.helm.sh/release-namespace: rocketmq
     labels:
       app.kubernetes.io/managed-by: Helm
     name: topictransfer
     namespace: rocketmq
     selfLink: 
/apis/rocketmq.apache.org/v1alpha1/namespaces/rocketmq/topictransfers/topictransfer
     uid: d9ebc8e4-6a97-4cb3-9fbc-7dc5ee967541
   spec:
     sourceCluster: broker-0
     targetCluster: broker-1
     topic: TopicTest
     
   
   After create above topictransfer.yaml, operator encounter 
   2024-03-31T01:25:16.872Z        ERROR   controller_topictransfer        
Failed to list topic with output: The sub command topiclist -c -n 
192.168.25.11:9876 not exist.
   
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
           
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:114
   
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
           
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:311
   
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
           
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:266
   
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:227
   
   
   So, I guess under code has bug!!!
   cmd := exec.Command(cons.BasicCommand, cons.AdminToolDir, topicListCmd)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to