[GitHub] [apisix-ingress-controller] GhangZh opened a new issue #886: bug: ingress-controller always shows this log not found service, but the service is actually there

Thu, 24 Feb 2022 00:24:17 -0800 


GhangZh opened a new issue #886:
URL: https://github.com/apache/apisix-ingress-controller/issues/886


   ### Issue description
   
   ingress-controller always shows this log, but the service is actually there
   
![image](https://user-images.githubusercontent.com/92301646/155486114-a44a6117-8610-4c8a-942d-c855788c1b52.png)
   
![image](https://user-images.githubusercontent.com/92301646/155486141-bd817922-c7b3-41a1-a4ff-fd22e2a1efb9.png)
   
![image](https://user-images.githubusercontent.com/92301646/155486153-ffb17a45-89e2-42aa-b62f-561b9093499c.png)
   
   
   ### Environment
   
   - your apisix-ingress-controller version (output of 
apisix-ingress-controller version --long):1.4.0
   - your Kubernetes cluster version (output of kubectl version):1.18
   - if you run apisix-ingress-controller in Bare-metal environment, also show 
your OS version (uname -a):
   
   
   ### Minimal test code / Steps to reproduce
   
   kubectl  -n ingress-apisix logs -f  apisix-ingress-controller-xxxxxx |grep 
retry
   kubectl  -n ingress-apisix describe ar apisixroute-dashboard
   
   ### Actual result
   
   no error log 
   
   ### Error log
   
   2022-02-24T15:39:39+08:00    warn    ingress/apisix_route.go:307     sync 
ApisixRoute failed, will retry     {"object": 
{"Type":1,"Object":{"Key":"ingress-apisix/apisixroute-dashboard","OldObject":null,"GroupVersion":"apisix.apache.org/v2beta1"},"Tombstone":null},
 "error": "service \"apisix-dashboard\" not found"}
   
   ### Expected result
   
   _No response_


-- 
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