"context deadline exceeded" error message is too generic

[trombik]

many part of the backend code use context with WithTimeout. they do not always throw exception with details. they just throw "context deadline exceeded" error. this makes debugging extremely difficult.

Expected Behavior

when timeout occurs, throws an error with more contexts, such as, who threw the error? what was the code doing? so that users can identify what the real cause is.

Current Behavior

the backend (possibly others) throw "context deadline exceeded".

Possible Solution

ensure to return error with the context.

Steps to Reproduce (for bugs)

there are many ways to reproduce. the easiest way is:

1. try to enable TLS in the backend
2. make mistakes
3. start the backend

Context

while I was trying to enable TLS, the backend always throws the error. I know it IS my fault, but it does not tell what the real issue is. to enable TLS, you need to change at least 20 configuration flags in backend.yml, which is not documented in the official documentation. if the backend gave me more context in errors, it would have been (slightly) easier.

Your Environment

• Sensu version used (sensuctl, sensu-backend, and/or sensu-agent): 5.20.0
• Installation method (packages, binaries, docker etc.): my own package
• Operating System and version (e.g. Ubuntu 14.04): FreeBSD 12.1

[echlebek]

This can be traced to a bug in etcd 3.3: etcd-io/etcd#9400

We need to upgrade to at least etcd 3.4 to fix this, but etcd 3.4 was published as a broken Go module, so we can't upgrade to it. We have to wait for etcd 3.5, which should be published some time this year.

See also #3729, #3649, and #3663, which are related to this issue.

[calebhailey]

Looks like etcd 3.5 is still in progress: https://github.com/etcd-io/etcd/milestone/37

[portertech]

Will be closed by #3729

[portertech]

We will confirm the issue has been fixed after merging #4229

[amdprophet]

I wasn't able to reproduce this on the main branch which now has Etcd 3.4. If this continues to happen after the next release (6.4.0), please reopen this.