This repository has been archived by the owner on Mar 16, 2024. It is now read-only.
When a new DB is created in an existing cluster with same username (from existing DB) , consuming app is not able to connect to the DB. #9
Labels
bug
Something isn't working
Steps to reproduce the problem:
app1
acorn run -n app1 . --clusterName santest1 --dbName test1 --dbUser testusernew --provider AWS --region US_WEST_2
consumingapp1
forapp1
. Make sure consuming app is able to connect successfully to DB.app2
using the sameclusterName
anddbUser
but differentdbName
acorn run -n app2 . --clusterName santest1 --dbName test3 --dbUser testusernew --provider AWS --region US_WEST_2
consumingapp2
forapp2
. Make sure consuming app is able to connect successfully to DB.After this,
Try to make a DB connection from
consumingapp1
(from step2). DB connection starts failing:From MongoDB console:
Notice that tbith he
admin
anduser
both get overwritten for DB name -test3
The text was updated successfully, but these errors were encountered: