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

   ### Current Behavior
   
   Issue Summary
   The APISIX Ingress Controller logs a persistent, misleading error 
(ResourceSyncAborted) for an ApisixUpstream resource, stating the Upstream 
"doesn't exist" because it is waiting for a referencing ApisixRoute. This 
occurs even when the dependent ApisixRoute is present and valid.
   
   2025-12-12T03:15:44Z    error   apisix/apisix_upstream.go:865   update 
status   {"status": 
{"conditions":[{"type":"ResourcesAvailable","status":"False","observedGeneration":1,"lastTransitionTime":"2025-12-12T03:15:44Z","reason":"ResourceSyncAborted","message":"upstream
 doesn't exist. It will be created after ApisixRoute is created referencing 
it."}]}}
   W1212 03:15:44.697671       1 warnings.go:70] unknown field 
"status.conditions[0].lastTransitionTime"
   2025-12-12T03:15:44Z    warn    apisix/apisix_upstream.go:509   sync 
ApisixUpstream failed, will retry  {"object": 
{"Type":1,"Object":{"Key":"test/crl-url-migration-service-upstream","OldObject":null,"GroupVersion":"apisix.apache.org/v2"},"OldObject":null,"Tombstone":null},
 "error": "upstream doesn't exist. It will be created after ApisixRoute is 
created referencing it."}
   
   Upstream:
   
   apiVersion: apisix.apache.org/v2
   kind: ApisixUpstream
   metadata:
   name: crl-url-migration-service-upstream
   namespace: test # Example Namespace
   spec:
   externalNodes:
   - type: Domain
   name: foo.com
   
   Route Referring the Above upstream
   
   apiVersion: apisix.apache.org/v2
   kind: ApisixRoute
   metadata:
   name: xxx-routes
   namespace: test # Example Namespace
   spec:
   http:
   - name: xxx-yyy
   priority: 5
   match:
   hosts:
   # Insert a representative hostname here
   paths:
   - /*
   exprs:
   - subject:
   scope: Path
   name: dfg
   op: RegexMatch
   value: '/a/b/.*.csl$'
   upstreams:
   - name: crl-url-migration-service-upstream
   
   ### Expected Behavior
   
   Error should not be logged
   
   
   ### Error Logs
   
   
   2025-12-12T03:15:44Z    error   apisix/apisix_upstream.go:865   update 
status   {"status": 
{"conditions":[{"type":"ResourcesAvailable","status":"False","observedGeneration":1,"lastTransitionTime":"2025-12-12T03:15:44Z","reason":"ResourceSyncAborted","message":"upstream
 doesn't exist. It will be created after ApisixRoute is created referencing 
it."}]}}
   W1212 03:15:44.697671       1 warnings.go:70] unknown field 
"status.conditions[0].lastTransitionTime"
   2025-12-12T03:15:44Z    warn    apisix/apisix_upstream.go:509   sync 
ApisixUpstream failed, will retry  {"object": 
{"Type":1,"Object":{"Key":"test/crl-url-migration-service-upstream","OldObject":null,"GroupVersion":"apisix.apache.org/v2"},"OldObject":null,"Tombstone":null},
 "error": "upstream doesn't exist. It will be created after ApisixRoute is 
created referencing it."}
   
   
   
   ### Steps to Reproduce
   
   Deploy above routes and upstream in apisix and watch the ingress controller 
logs for error
   
   ### Environment
   
   - APISIX Ingress controller version  Version: 1.8.4
   Git SHA: d3f8ce9
   Go Version: go1.24.4
   Building OS/Arch: linux/aarch64
   Running OS/Arch: linux/arm64
   
   - Kubernetes cluster version (run `kubectl version`)
   Client Version: v1.32.2
   Kustomize Version: v5.5.0
   Server Version: v1.32.2
   
   - OS version if running APISIX Ingress controller in a bare-metal 
environment (run `uname -a`)
   


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