Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist

MongoDB - Defect ID: 377314

Make test spawned mongo processes bind to 0.0.0.0

Last updated on 10/27/2023

Overall
5.95.9
Severity
6.46.4
Community
5.55.5
Lifecycle
9.19.1
What is the BugZero Risk Score?

Vendor details

  • Priority: Major - P3
  • Status: Closed

Info

SERVER-28229 made MongoDB processes bind to localhost by default. In JSTests, we passed spawned daemons --bindIpAll as these processes spoke with each other via the host's external IP. Unfortunately, old processes spawned in the multiversion suite do not understand this flag. We must explicitly bind to 0.0.0.0.

Top User Comments

spencer.jackson@10gen.com commented on Wed, 26 Apr 2017 15:22:09 +0000: The original ticket which this would have ammended was reverted. The necessary work will be done there.

Steps to Reproduce


  • 5.9Defect ID: 2956672
    Some time-series tests implicitly rely on measurement insertion order for unordered inserts when checking bucket catalog stats
  • 6.14Defect ID: 2965528
    Remove push, publish_packages, and crypt_push tasks from Graviton 4 variants in v7.0 and v8.0
  • 6.14Defect ID: 2947969
    [SBE] Release storage engine resources when saveState() or restoreState() throws
  • 5.68Defect ID: 2919474
    StackLocator broken by v5 toolchain ASAN
  • 5.88Defect ID: 2968769
    Make new write path helper functions use acquireAndValidateBucketsCollection instead of acquireCollection

Ready to prevent the next vendor outage?

Get a demo
BugZero | MongoDB BugID 377314 - Make test spawned mongo processes bind to 0.0.0.0