wolgod opened a new issue, #1165:
URL: https://github.com/apache/apisix-ingress-controller/issues/1165

   ### Issue description
   
   I wrote the service port wrong at the beginning, and the service port in 
apisixroute is also wrong, but when I change the service port and the port of 
apisixroute to the right, it does not take effect, and the correct Upstream 
cannot be synchronized to apisix, only when apisixroute is deleted. Resync the 
correct port to Upstream, but the ingress controller still prints an error 
message
   
   ### Environment
   
   - your apisix-ingress-controller version (output of 
apisix-ingress-controller version --long):1.4.1
   - 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):centos7
   
   
   ### Minimal test code / Steps to reproduce
   
   1.I wrote the service port wrong at the beginning, and the service port in 
apisixroute is also wrong
   2.≈t, it does not take effect
   3.when apisixroute is deleted. Resync the correct port to Upstream, but the 
ingress controller still prints an error message
   
   ### Actual result
   
   when apisixroute is deleted. ingress controller  can Resync the correct port 
to Upstream, and the ingress controller  don’t print error message 
   
   ### Error log
   
   error   translation/util.go:66  ApisixRoute refers to non-existent Service 
port {"namespace": "ns-2424", "port": "8123"}
   2022-07-18T10:13:12+08:00       error   ingress/apisix_route.go:217     
failed to translate old ApisixRoute     {"version": 
"apisix.apache.org/v2beta3", "event": "update", "error": "service.spec.ports: 
port not defined", "ApisixRoute": {}}
   2022-07-18T10:13:12+08:00       warn    ingress/apisix_route.go:305     sync 
ApisixRoute failed, will retry     {"object": 
{"Type":2,"Object":{"Key":"ns-2424/log-monitor-aggregate-test","OldObject":{},"GroupVersion":"apisix.apache.org/v2beta3"},"Tombstone":null},
 "error": "service.spec.ports: port not defined"}
   
   
   ### 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