Migration error: Unsupported OP_QUERY command

[ralf-berger]

What version were you using?

Branch issue/4-create-admin-user-on-startup

What steps can we follow to reproduce the behaviour?

The Branch belonging to #4 introduces migrations for MongoDB to be run before using accessing the database. Running those during startup (Compose service migrations) causes the following error.

What is the actual behaviour?

$ node cli/dist/server migrateMongo --up

(node:28) UnhandledPromiseRejectionWarning: MongoError: Unsupported OP_QUERY command: insert. ⏎
  The client driver may require an upgrade. For more details see [https://dochub.mongodb.org/core/legacy-opcode-removal⁠](https://dochub.mongodb.org/core/legacy-opcode-removal)
    at Function.MongoError.create (/opt/learninglocker/node_modules/mongodb-core/lib/error.js:31:11)
    at /opt/learninglocker/node_modules/mongodb-core/lib/connection/pool.js:497:72
    at authenticateStragglers (/opt/learninglocker/node_modules/mongodb-core/lib/connection/pool.js:443:16)
    at Connection.messageHandler (/opt/learninglocker/node_modules/mongodb-core/lib/connection/pool.js:477:5)
    at Socket.<anonymous> (/opt/learninglocker/node_modules/mongodb-core/lib/connection/connection.js:333:22)
    at Socket.emit (events.js:198:13)
    at Socket.EventEmitter.emit (domain.js:448:20)
    at addChunk (_stream_readable.js:288:12)
    at readableAddChunk (_stream_readable.js:269:11)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

What is the expected behavior?

It's supposed to apply required schema/data updates to MongoDB.

Is there any additional information that will help us replicate/understand the problem?

The application uses Node 10, MongoDB 6.0, Yarn (mongoose 5.5, mongodb 3.3)

[shoebjoarder]

I guess the issue lies with Learning Locker’s Node.js 10-era MongoDB driver against MongoDB 6. The driver is still using the legacy OP_QUERY wire protocol commands like insert, which MongoDB 5.0+ has removed according to the docs.

Since LL has issues with Node version higher than 10, one way to fix it is to download the MongoDB version in the compose file:

mongo:
   #  image: mongo:6.0
   image: mongo:4.4
   command: mongod --wiredTigerCacheSizeGB 0.25 --quiet --logpath /dev/null
   ports: ["27017:27017"]
   volumes:
      - mongo:/data/db
   healthcheck:
      test: "mongo --eval 'db.runCommand({ ping: 1 }).ok'"
      start_period: 2s
      interval: 10s

Managed to run the docker compose build command successfully

[+] Running 13/13
 ✔ ghcr.io/ude-soco/learninglocker:latest   Built                                                        0.0s 
 ✔ Network learninglocker_default           Created                                                      0.0s 
 ✔ Volume "learninglocker_redis"            Created                                                      0.0s 
 ✔ Volume "learninglocker_xapi-service"     Created                                                      0.0s 
 ✔ Volume "learninglocker_mongo"            Created                                                      0.0s 
 ✔ Container learninglocker-redis-1         Created                                                      1.3s 
 ✔ Container learninglocker-mongo-1         Created                                                      1.3s 
 ✔ Container learninglocker-xapi-service-1  Created                                                      0.4s 
 ✔ Container learninglocker-worker-1        Created                                                      0.4s 
 ✔ Container learninglocker-migrations-1    Created                                                      0.3s 
 ✔ Container learninglocker-fixtures-1      Created                                                      0.2s 
 ✔ Container learninglocker-api-1           Created                                                      0.2s 
 ✔ Container learninglocker-ui-1            Created                                                      0.2s 
Attaching to api-1, fixtures-1, migrations-1, mongo-1, redis-1, ui-1, worker-1, xapi-service-1
worker-1  | Starting worker ...
xapi-service-1  | yarn run v1.22.19
xapi-service-1  | $ node dist/server.js
migrations-1    | yarn run v1.22.5
migrations-1    | $ node cli/dist/server migrateMongo --up
migrations-1    | (node:28) DeprecationWarning: collection.update is deprecated. Use updateOne, updateMany, or bulkWrite instead.
migrations-1    | Done in 1.67s.
migrations-1 exited with code 0
fixtures-1      | Setting up admin account ...
fixtures-1 exited with code 0
api-1           | Starting API ...
ui-1            | Starting UI ...

The admin user was also generated.

[shoebjoarder]

MongoDB 4.4 works with the classic mongo shell, not mongosh, which is why Docker shows that the container learninglocker-mongo-1 is unhealthy.

mongo:
  image: mongo:4.4
  command: mongod --wiredTigerCacheSizeGB 0.25 --quiet --logpath /dev/null
  ports: [ "27017:27017" ]
  volumes:
  - mongo:/data/db
  healthcheck:
    # test: "mongosh --nodb --eval 'disableTelemetry()'; echo 'db.runCommand({ping: 1}).ok' | mongosh localhost:27017/test --quiet"
    test: "mongo --nodb --eval 'disableTelemetry()'; echo 'db.runCommand({ping: 1}).ok' | mongo localhost:27017/test --quiet"
    start_period: 2s
    interval: 10s