[bitnami/mongodb] Custom databases not getting created

[desgith]

Name and Version

mongodb-13.6.7

What architecture are you using?

None

What steps will reproduce the bug?

helm.exe install mongodb . -n mongo

Are you using any custom parameters or values?

  usernames: [mycontext]
  passwords: [context]
  databases: [mynewdb]

What is the expected behavior?

mongosh admin --host "mongodb-0.mongodb-headless.m.svc.cluster.local:27017,mongodb-1.mongodb-headless.m.svc.cluster.local:27017" --authenticationDatabase admin -u root -p $MONGODB_ROOT_PASSWORD

The above command should login and

show dbs

should show me mynewdb

What do you see instead?

rs0 [primary] admin> show dbs
admin   140.00 KiB
config  184.00 KiB
local   620.00 KiB

mynewdb is missing

Additional information

Am i doing anything wrong in this command or my understanding is wrong? .Values.auth.databases create new DBs or should i do something else to make it work

[javsalgar]

Hi!

Could you share the logs of the containers to see if there's an any error?

[desgith]

Hi,
I dont see any errors, i am seeing no restarts in the containers as well

NAME                            READY   STATUS             RESTARTS          AGE
mongodb-0                       1/1     Running            0                 45h
mongodb-1                       1/1     Running            0                 45h
mongodb-arbiter-0               1/1     Running            0                 45h

The log is very big, with errors related to missing username as well, which i tried creating using custom usernames let me know if you need it

[desgith]

Any update on this request?

[aoterolorenzo]

Hi @desgith,

Anything showing up in the container logs?

kubectl logs mongodb-0

Also, seems you are installing a cluster, could you provide the exact values for replicating your same example?

[ghost]

@aoterolorenzo I've got a a similar issue:

rs0 [primary] admin> show dbs
admin   172.00 KiB
config  216.00 KiB
local   444.00 KiB

$ helm upgrade --install rc-mongo mongodb/mongodb -f mongodb-dev-values.yaml -n rc

mongodb-dev-values.yaml

auth:
  usernames:
    - rocketchat
  databases:
    - rocketchat
  passwords:
    - rocketchat
  rootPassword: rocketchat
architecture: replicaset
useStatefuleSet: false
replicaCount: 3
affinity:
  nodeAffinity:
    requiredDuringSchedulingIgnoredDuringExecution:
      nodeSelectorTerms:
      - matchExpressions:
        - key: "node-role.kubernetes.io/control-plane"
          operator: DoesNotExist
        - key: "node-role.kubernetes.io/etcd"
          operator: DoesNotExist
        - key: "node-role.kubernetes.io/master"
          operator: DoesNotExist
arbiter:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: "node-role.kubernetes.io/control-plane"
            operator: DoesNotExist
          - key: "node-role.kubernetes.io/etcd"
            operator: DoesNotExist
          - key: "node-role.kubernetes.io/master"
            operator: DoesNotExist

[ghost]

mongo-db-0.txt

[aoterolorenzo]

Hi @benhosmereop,

The configuration values seems OK so probably there is a bug behind the issue. I will raise an internal task for our team to investigate this. We will be in touch over this conversation when it gets to an outcome. Meanwhile, I will mark it as on hold to prevent the bitnami-bot from closing it.

[fhbmax]

I hit the same issue using the helm chart with the extra values for auth.databases, auth.usernames and auth.passwords.
The created users weren't able to connect to the databases (which didn't show up when checking as root).
We had to manually add the roles dbAdmin additionally to the readWrite role to the extra users using the mongosh:

db.createUser({
    user: 'testuser',   
    pwd: '<password>',  
    roles: [  
        {role: 'readWrite', db: 'testdb'},   
        {role: 'dbAdmin', db: 'testdb'}`
    ]  
});  

Then it would work as expected.

[sagimann]

Did you try to check if the db exists even though it's not showing up on show dbs? See this article. I had the same symptom, but the dbs and their users were actually there. I was able to login, assuming the auth db is where the user was created:

kubectl run --namespace default mongo-mongodb-client --rm --tty -i --restart='Never' --image docker.io/bitnami/mongodb:5.0.18-debian-11-r10 --command -- mongosh admin --host "mongo-mongodb" --authenticationDatabase testdb -u myuser -p 12345
use testdb
testdb> db.collection1.insertOne({name:"hello"})
testdb> show collections
collection1

[rafariossaa]

Hi,
@fhbmax , @desgith , @benhosmereop Did you have the chance to check what @sagimann indicated ?

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

[virtyaluk]

Although this issue has been closed for more than a year now, I just happened to run into the same problem it turned out that the database has been created and I can actually use it, but it still doesn't show up in the list of available databases. Thanks.