Closed inzagod closed 2 months ago
hi all, i tried to add the adminusername : mongodb in the secret and the pod begin to start well but it crash after few moment because, while mongodb has been updated, notice that after a few moment the secret is overwritten because it managed by microcksinstall but in the microcksinstall yaml i cannot set the adminusername secret value
because the operator has automatic updates (like every operators) the operator is already up to date and i cannot rollback to an older version ! how can i do now to migrate my datas (in pvc) in 1.9 version to 1.10.1 version ? i am stuck !
i join you the log file when the pod try to start and we saw that the mongodb version is too high for the datas :
{"t":{"$date":"2024-09-05T13:24:51.482+00:00"},"s":"F", "c":"STORAGE", "id":4671205, "ctx":"initandlisten","msg":"This version of MongoDB is too recent to start up on the existing data files. Try MongoDB 4.2 or earlier."}
very thanks a lot
ludo my-microcksinstall-mongodb-865995b5b4-9sdj2-mongodb.log
hi all, i close this issue because restart from scratch (not enough data) solve the issue i create another one because i have another issue in another cluster (restart from scratch but scc issue with mongodb) thanks a lot ludo
Describe the bug
hi all, with microcks 1.10 operator mongodb pod don't want to start because adminUsername data is missing in the secret
please see below the secret yaml
notice that the operator has automatic updates and i cannot revert to an older version
can you help me please ?
ludo
Expected behavior
No response
Actual behavior
mongodb pod don't want to start it is in CreateContainerConfigError state
Error: couldn't find key adminUsername in Secret microcksinstall/my-microcksinstall-mongodb-connection
How to Reproduce?
No response
Microcks version or git rev
1.10
Install method (
docker-compose
,helm chart
,operator
,docker-desktop extension
,...)operator
Additional information
No response