You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
b1ron opened this issue
Feb 22, 2024
· 2 comments
· May be fixed by #4119
Assignees
Labels
area/authIssues about authentication and authorizationcode/bugSome user-visible feature works incorrectlynot readyIssues that are not ready to be worked on; PRs that should skip CI
MongoServerError: [msg_saslstart.go:184 handler.(*Handler).scramCredentialLookup] [collection.go:57 postgresql.(*collection).Query] [registry.go:279 metadata.(*Registry).DatabaseGetExisting] [registry.go:132 metadata.(*Registry).getPool] [pool.go:128 pool.(*Pool).Get] [opendb.go:95 pool.openDB] [opendb.go:110 pool.checkConnection] failed to connect to `host=127.0.0.1 user=byron database=ferretdb`: failed SASL auth (FATAL: password authentication failed for user "byron" (SQLSTATE 28P01))
The text was updated successfully, but these errors were encountered:
b1ron
added
code/bug
Some user-visible feature works incorrectly
not ready
Issues that are not ready to be worked on; PRs that should skip CI
labels
Feb 22, 2024
This is no longer an issue with the current version. However, what's quite confusing is that is passes locally but only once, and always fails on CI. It could be related to the fact that we authenticate using a new client instance in the shell.
I need to debug the test further in #4119 to fully understand the problem.
area/authIssues about authentication and authorizationcode/bugSome user-visible feature works incorrectlynot readyIssues that are not ready to be worked on; PRs that should skip CI
FerretDB version
v1.20.0-12-gb6fd73b4-dirty
Backend
PostgreSQL
Environment
dev
What did you do?
See repro #4119.
What did you expect to see?
A successful connection.
What did you see instead?
The text was updated successfully, but these errors were encountered: