Closed maxwell-gobel closed 10 months ago
any updates on this issue? 🙏
any updates on this issue? 🙏
This is actually fixed as I know in version 7.47.0. Our organization already has updated and doesn't see this error anymore.
I just ran into the same error. I updated from Agent 7.43.2 - Commit: 26255a9 - Serialization version: v5.0.67 - Go version: go1.19.6
to Agent 7.49.0 - Commit: 9cb8e9c - Serialization version: v5.0.97 - Go version: go1.20.10
and it's working for me.
Hello 👋 Closing this issue as it has been fixed in newer releases. Feel free to open it again if needed 🙂
Agent Environment Image Tag:
gcr.io/datadoghq/agent:7.41.1
Image Digest:gcr.io/datadoghq/agent@sha256:4992b38387ca6dbb732f3493ed66cdf5efe7e08154b7e9e4159b1735dbaabe3f
Image Architecture:Describe what happened: Migrated our k8s nodes from amd64 to arm64, and a previously functional postgres custom query check started failing with:
Describe what you expected:
Steps to reproduce the issue: Using the
linux/arm64
gcr.io/datadoghq/agent:7.41.1
image, configure a postgres custom query check using password auth Also reproduces with 7.42.0Additional environment details (Operating System, Cloud provider, etc): Running using the
datadog-2.37.4
helm chart. Custom query check is configured on the cluster-agent and farmed out to other agents (not running a dedicated cluster checks runner)Related: