You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Running the hello-world example, using the same namespace names and resource
names in a loop, seems to be causing problems to the controller.
The logs show that it is trying to update the listener, but failing.
time=2025-02-05T21:33:36.783Z level=INFO msg="updating listener token-west-testing/backend..."
time=2025-02-05T21:33:39.994Z level=INFO msg="[ControllerError] Error while handling Pod token-east-testing/backend-8465dfcd48-zfjfp: Error looking up connector for token-east-testing/backend"
time=2025-02-05T21:33:40.008Z level=INFO msg="[ControllerError] Error while handling Pod token-east-testing/backend-8465dfcd48-zfjfp: Error looking up connector for token-east-testing/backend"
time=2025-02-05T21:33:40.021Z level=INFO msg="[ControllerError] Error while handling Pod token-east-testing/backend-8465dfcd48-zfjfp: Error looking up connector for token-east-testing/backend"
time=2025-02-05T21:33:40.034Z level=INFO msg="[ControllerError] Error while handling Pod token-east-testing/backend-8465dfcd48-zfjfp: Error looking up connector for token-east-testing/backend"
time=2025-02-05T21:33:40.041Z level=INFO msg="[ControllerError] Error while handling Pod token-east-testing/backend-8465dfcd48-zfjfp: Error looking up connector for token-east-testing/backend"
time=2025-02-05T21:33:40.404Z level=INFO msg="[ControllerError] Error while handling Pod token-east-testing/backend-8465dfcd48-zfjfp: Error looking up connector for token-east-testing/backend"
How To Reproduce
Run the hello-world example (automated) in a loop.
Expected behavior
Site state should reflect current resources, but I see:
NAMESPACE NAME STATUS SITES IN NETWORK MESSAGE
token-east-testing token-east Ready 2 OK
token-west-testing token-west Ready 2 OK
NAMESPACE NAME STATUS REMOTE SITE MESSAGE
token-east-testing link-1738790792 Ready token-west OK
NAMESPACE NAME ROUTING KEY PORT HOST STATUS HAS MATCHING CONNECTOR MESSAGE
token-west-testing listener.skupper.io/backend backend-8080 8080 backend Pending No matching connectors
NAMESPACE NAME ROUTING KEY PORT HOST SELECTOR STATUS HAS MATCHING LISTENER MESSAGE
token-east-testing connector.skupper.io/backend backend-8080 8080 app=backend Ready true OK
Environment details
quay.io/skupper/controller:v2-dev
quay.io/skupper/skupper-router:main
quay.io/skupper/kube-adaptor:v2-dev
Kubernetes (minikube)
The text was updated successfully, but these errors were encountered:
Describe the bug
Running the hello-world example, using the same namespace names and resource
names in a loop, seems to be causing problems to the controller.
The logs show that it is trying to update the listener, but failing.
More details can be found through:
https://gist.github.com/fgiorgetti/bb44cf8d91f76177256cc800899e49c2
Snippet:
How To Reproduce
Run the hello-world example (automated) in a loop.
Expected behavior
Site state should reflect current resources, but I see:
Environment details
The text was updated successfully, but these errors were encountered: