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
./plano demo gets stuck when using skupper 1.4.4 with the latest HEAD on skewer. Not positive, but looked like it may have affected @pwright as well.
I suspect it is a version compatibility thing - mixing skupper and skewer versions. Maybe it could be useful to tag skewer along with a particular upstream release or something? 🤷♂️
I see that it stalls here:
plano: notice: Running command 'kubectl get configmap/skupper-network-status'
Error from server (NotFound): configmaps "skupper-network-status" not found
plano: notice: Sleeping for 5 seconds
My workaround was this:
diff --git a/subrepos/skewer/python/skewer/standardsteps.yaml b/subrepos/skewer/python/skewer/standardsteps.yaml
index cbce9ce..c3c05ab 100644
--- a/subrepos/skewer/python/skewer/standardsteps.yaml
+++ b/subrepos/skewer/python/skewer/standardsteps.yaml
@@ -114,7 +114,7 @@ check_the_status_of_your_namespaces:
installed.
commands:
"*":
- - await: [deployment/skupper-service-controller, deployment/skupper-router, configmap/skupper-network-status]
+ - await: [deployment/skupper-service-controller, deployment/skupper-router]
- run: sleep 15 # A temp hack for a 1.5.0 problem
apply: test
- run: skupper status
The text was updated successfully, but these errors were encountered:
./plano demo gets stuck when using skupper 1.4.4 with the latest HEAD on skewer. Not positive, but looked like it may have affected @pwright as well.
I suspect it is a version compatibility thing - mixing skupper and skewer versions. Maybe it could be useful to tag skewer along with a particular upstream release or something? 🤷♂️
I see that it stalls here:
My workaround was this:
The text was updated successfully, but these errors were encountered: