[SERVER-51733] config server in a docker container fails to start up with authentication Created: 19/Oct/20 Updated: 29/Oct/23 Resolved: 27/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.0, 4.4.1, 4.7.0 |
| Fix Version/s: | 4.9.0, 4.4.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Phillips Freeman | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Bug | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||||||||||||||
| Steps To Reproduce: | First start up a config server in a docker container:
Once it has started up create the repl set
After a few moments the database will crash producing the following error:
I could not add the complete log of the incident as that exceeds the allowed length in this text box. Therefore you can find it at the following link if needed:
|
||||||||||||||||||||||||||||
| Sprint: | Execution Team 2020-11-02 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
When mongo is running inside a docker container it is impossible to create a new replica set on a fresh config server. I have tried to find a work around by trying this on versions 4.4.1, 4.7.0, and 4.4.0, all produce the same error. I have also tried running it in a custom built container on Ubuntu 20.04 (focal) and also get the same error. |
| Comments |
| Comment by Githook User [ 19/Nov/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: (cherry-picked from commit e9ad50c2eb550e3d1db94ac94ac870ae4c68960e) |
| Comment by Githook User [ 19/Nov/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: (cherry-picked from commit 6419fd81bdefa91390303fdda48457c8a485399b) |
| Comment by Githook User [ 19/Nov/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: (cherry-picked from commit 3aafc656417787ad650701cc55f3a95dc8e75741) |
| Comment by Benety Goh [ 28/Oct/20 ] |
|
freemo@gmail.com, thank you for bringing this to our attention! Separately, we have filed issue #431 in the docker-library/mongo project on GitHub. |
| Comment by Jeffrey Phillips Freeman [ 28/Oct/20 ] |
|
Thanks so much on the speedy resolve on this one. Great work team! |
| Comment by Githook User [ 27/Oct/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 27/Oct/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 27/Oct/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Jeffrey Phillips Freeman [ 23/Oct/20 ] |
|
I can certainly do that. But given the nature of the error, and the fact that it is running standard mongo executables I would imagine in the end it would still come down to a bug in mongo itself. The key will be replicating it outside the container I suppose. |
| Comment by Jonathan Streets (Inactive) [ 23/Oct/20 ] |
|
hi freemo@gmail.com, thank you for reporting the issue. We've done some investigation and I can use your reproducer and get the error using the Community Supported docker.com container running on Ubuntu 18, however the commands succeed for both Ubuntu 18, and in the Mongo Supported Enterprise Operator. The container on docker.com is Community maintained and supported. Please can you report the issue there ? jon |
| Comment by Jeffrey Phillips Freeman [ 19/Oct/20 ] |
|
FYI It does appear 3.6.20 however is not affected by this bug, that version seems to work just fine, presumably earlier versions as well. |