Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Halt advancement no values found for kuma metric request-success-rate probably podinfo.test is not receiving traffic: running query failed: no values found #1633

Open
yashp24 opened this issue Apr 22, 2024 · 1 comment

Comments

@yashp24
Copy link

yashp24 commented Apr 22, 2024

I am following this document https://docs.flagger.app/tutorials/kuma-progressive-delivery. When I checked the Automated canary promotion I got this error.

Events:
  Type     Reason  Age                   From     Message
  ----     ------  ----                  ----     -------
  Normal   Synced  18m (x8 over 2d15h)   flagger  New revision detected! Scaling up podinfo.test
  Warning  Synced  17m (x2 over 64m)     flagger  canary deployment podinfo.test not ready: waiting for rollout to finish: 0 of 1 (readyThreshold 100%) updated replicas are available
  Normal   Synced  17m (x9 over 2d15h)   flagger  Starting canary analysis for podinfo.test
  Normal   Synced  17m (x9 over 2d15h)   flagger  Pre-rollout check acceptance-test passed
  Normal   Synced  17m (x9 over 2d15h)   flagger  Advance podinfo.test canary weight 5
  Warning  Synced  15m (x42 over 2d15h)  flagger  Halt advancement no values found for kuma metric request-success-rate probably podinfo.test is not receiving traffic: running query failed: no values found

I am using kuma, flagger, and prometheus.

these are my pods in test namespace:

NAME                                   READY   STATUS    RESTARTS   AGE
pod/flagger-loadtester-65f76b8-49fp9   1/1     Running   0          2d20h
pod/podinfo-primary-56c8b6ff68-78rmx   2/2     Running   0          2d15h

Capture

Finally my canary deployment is getting failed. Can someone help me to resolve this issue?

@yashp24
Copy link
Author

yashp24 commented May 2, 2024

could someone please look into this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant