-
Notifications
You must be signed in to change notification settings - Fork 11
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
integration tests failing because one of hardware-observer's metrics are down #161
Labels
Comments
ca-scribner
added a commit
that referenced
this issue
Aug 7, 2024
Previously, hardware-observer is showing a metric down, resulting in CI failures. This change pins to a known working version of hardware observer. See #161 for more details.
ca-scribner
added a commit
that referenced
this issue
Aug 7, 2024
Previously, hardware-observer is showing a metric down, resulting in CI failures. This change pins to a known working version of hardware observer. See #161 for more details.
ca-scribner
added a commit
that referenced
this issue
Aug 7, 2024
Previously, hardware-observer is showing a metric down, resulting in CI failures. This change pins to a known working version of hardware observer. See #161 for more details.
ca-scribner
added a commit
that referenced
this issue
Aug 7, 2024
Previously, hardware-observer is showing a metric down, resulting in CI failures. This change pins to a known working version of hardware observer. See #161 for more details.
mmkay
pushed a commit
that referenced
this issue
Aug 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
During CI runs (locally and in gh), we're seeing the following:
which is caused because one of hardware-observer's monitored metrics is down:
Previous successful CI runs have used hardware-observer successfully with rev70 of the charm - this appears to be new behaviour. An issue is filed in hardware-observer to see if this is a bug.
To Reproduce
tox -e integration
on the current charmEnvironment
Relevant log output
Additional context
Full logs: https://github.com/canonical/grafana-agent-operator/actions/runs/10287798773/job/28471764690
The text was updated successfully, but these errors were encountered: