[SERVER-28072] Running a script using 'mongo' on replication set fails Created: 22/Feb/17 Updated: 16/Nov/21 Resolved: 04/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 3.4.2 |
| Fix Version/s: | 3.4.11, 3.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tom Leibu | Assignee: | Sara Golemon |
| Resolution: | Done | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||||||||||||||
| Steps To Reproduce: | OS: CentOS Linux release 7.1.1503 (Core) Just run this line. |
||||||||||||||||||||||||
| Sprint: | Platforms 2017-07-31, Platforms 2017-09-11, Platforms 2017-10-02, Platforms 2017-10-23 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
rIt seems like there's a regression bug Prior to 3.4.2 this command succeeded: The current output I'm getting is: MongoDB shell version v3.4.2 |
| Comments |
| Comment by Githook User [ 27/Nov/17 ] | ||
|
Author: {'name': 'Sara Golemon', 'username': 'sgolemon', 'email': 'sara.golemon@mongodb.com'}Message: (cherry picked from commit 592208bb012bee0355d2024dcbc062185e6d22e7) | ||
| Comment by Githook User [ 04/Oct/17 ] | ||
|
Author: {'email': 'sara.golemon@mongodb.com', 'name': 'Sara Golemon', 'username': 'sgolemon'}Message: | ||
| Comment by Andrew Morrow (Inactive) [ 21/Aug/17 ] | ||
|
mskalick - The ticket is currently marked 3.5 required, and scheduled for our next development sprint. The fix will go to master first, and then (presumably) get backported, but it seems reasonable to expect to see a fix for this land in the 3.4 branch within the next month or so, barring surprises or re-prioritization. | ||
| Comment by Marek Skalický [ 21/Aug/17 ] | ||
|
What is a status of this please? This broke our scripts. And it would be great to have this fixed. | ||
| Comment by Tyler Kaye [ 10/Aug/17 ] | ||
|
This is a different problem from the one solved in | ||
| Comment by Mark Agarunov [ 27/Feb/17 ] | ||
|
Hello tomzan, Upon further investigation, this does appear to be a regression. You can watch this ticket for updates on this issue. In the meantime, the newer connection string format can be used as a workaround. Thanks, | ||
| Comment by Mark Agarunov [ 23/Feb/17 ] | ||
|
Hello tomzan, Thank you for the report. Looking over the output you've provided, this behavior seems to be due to the bug detailed in
Would now be
If this behavior is still present with the updated connection string, please let me know so that we can continue investigating. Thanks, |