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

Missing metric keda_scaled_object_paused after keda-operator restart #6321

Closed
aguerra opened this issue Nov 7, 2024 · 1 comment · Fixed by #6322
Closed

Missing metric keda_scaled_object_paused after keda-operator restart #6321

aguerra opened this issue Nov 7, 2024 · 1 comment · Fixed by #6322
Labels
bug Something isn't working

Comments

@aguerra
Copy link

aguerra commented Nov 7, 2024

Report

Keda-operator reports the metric keda_scaled_object_paused as 1 for a paused scaled object. After restarting or replacing the keda-operator pod the metric is missing.

Expected Behavior

The reconciliation should be able to detect the paused scaled object and set the corresponding metric keda_scaled_object_paused to 1.

Actual Behavior

The metric keda_scaled_object_paused is missing.

Steps to Reproduce the Problem

  1. Pause a scaled object and confirm that the metric keda_scaled_object_paused{scaledObject="my-scaled-object"} is present and equals 1.
  2. Restart or replace the keda-operator pod.
  3. The metric keda_scaled_object_paused{scaledObject="my-scaled-object"} is missing.

Logs from KEDA operator

example

KEDA Version

2.15.1

Kubernetes Version

1.30

Platform

Amazon Web Services

Scaler Details

CPU

Anything else?

No response

@JorTurFer
Copy link
Member

Thanks for reporting! I've reproduced the issue and the PR with the fix is already opened 😄

@github-project-automation github-project-automation bot moved this from To Triage to Ready To Ship in Roadmap - KEDA Core Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Ready To Ship
Development

Successfully merging a pull request may close this issue.

2 participants