[SERVER-68946] jscore failure on 6.0 mongo container Created: 18/Aug/22  Updated: 27/Oct/23  Resolved: 19/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 6.0.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tausif Rahman (Inactive) Assignee: Backlog - Query Execution
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Assigned Teams:
Query Execution
Operating System: ALL
Participants:
Linked BF Score: 135

 Description   

Failing jscore tests: jstests/core/bypass_doc_validation.js, jstests/core/json_schema/logical_keywords.js
Bug Symptoms:

"A corrupt namespace has been detected. See http://dochub.mongodb.org/core/data-recovery for recovery steps."
"Could not complete validation of table:index-46-760292241510070916. This is a transient issue as the collection was actively in use by other operations."
"Detected one or more documents not compliant with the collection's schema. Check logs for log id 5363500."

Context:
On the Server Development Platform team, we are working on pushing MongoDB docker containers to DockerHub. We have set up test infrastructure to run some basic tests against a mongodb docker container & run jscore against the mongodb docker container. For 4.4 & 5.0 jscore works without any problems. When we added 6.0 jscore started failing with quite a few data validation failures. To verify that this is a 6.0 bug and not a test infrastructure bug, I ran the failing test with the 5.0 infrastructure against the 6.0 mongodb container (required some negligible changes to the 5.0 infrastructure) — which fails. When I ran the failing test with the 5.0 infrastructure against a local 6.0 mongod — things pass. We haven’t changed the way the mongodb docker container starts up. Since 6.0 has been released, this may be bug that is in our 6.0 binaries.

Mongo Container -
contains the 6.0 mongo binaries

Mongo Workload Container -
contains the 6.0 mongo binaries + 6.0 mongo repo to run resmoke against an existing Mongo Container

REPRO INSTRUCTIONS -

  1. Pull docker images
    1. docker pull deriamis/mongodb:6.0-ubuntu1804-enterprise-container-BF
    2. docker pull deriamis/mongodb:6.0-ubuntu1804-enterprise-workload-BF
  2. Create a test docker network
    1. docker network create mongo-net
  3. Start a mongo-container-BF (you can add -d flag if you want this to run in the background)
    1. docker run --network mongo-net -it --name test --rm deriamis/mongodb:mongo-container-BF
  4. Start a terminal session from a mongo-workload-container-BF container
    1. docker run --network mongo-net -it --name workload --rm  deriamis/mongodb:mongo-workload-container-BF /bin/bash
    2. cd mongo
    3. python3.8 buildscripts/resmoke.py run --suite core --shellConnString mongodb://test:27017 jstests/core/bypass_doc_validation.js
      1. You MUST include python3.8 to use resmoke deps


 Comments   
Comment by Tausif Rahman (Inactive) [ 19/Aug/22 ]

Hi david.storch@mongodb.com. max.hirschhorn@mongodb.com was able to help me out with this, we can close this out. Thanks for the help all!

Comment by David Storch [ 19/Aug/22 ]

tausif.rahman@mongodb.com did you mean to add this to our triage queue? I'm going to put it there and remove the 6.0.1 fixVersion.

Generated at Thu Feb 08 06:12:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.