Closed krtk6160 closed 1 year ago
same issue when I use 8.2.3 to connection localhost:27017 (e.g. run migrate-mongo status
)
but use 8.2.2 is working correctly
issue still exists in 9.0.0
EDIT: works for me when adding directConnection=true
to the connection string
Thanks @Jay-Funk, directConnection
worked as a workaround.
See last comment for a workaround. Issue is not directly caused by migrate-mongo, so I'm closing this.
Describe the bug When I run
migrate-mongo status
on v8.2.3 while port-forwarding a kubectl mongodb pod I get this error ->However, doing the same on v8.2.2, I get the correct list of migrations I've already performed.
To Reproduce Steps to reproduce the behavior:
kubectl port-forward mongodb-0 27017
migrate-mongo status
in an already initialized directoryExpected behavior I expect it to display my migrations correctly, just like v8.2.2 does.