Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.7.7
-
Component/s: None
-
Labels:None
-
Operating System:ALL
Description
Seems to be an intermittent failure. The root cause may be: SERVER-13582
assert.soon failed: function () {
|
return A.runCommand({replSetGetStatus : 1}).syncingTo == bAddress;
|
}, msg:undefined
|
Error: assert.soon failed: function () {
|
return A.runCommand({replSetGetStatus : 1}).syncingTo == bAddress;
|
}, msg:undefined
|
at Error (<anonymous>)
|
at doassert (src/mongo/shell/assert.js:11:14)
|
at Function.assert.soon (src/mongo/shell/assert.js:180:60)
|
at /data/mci/shell/mongodb-mongo-master/jstests/noPassthrough/server6733.js:33:8
|
2014-04-22T22:11:11.771+0000 Error: assert.soon failed: function () {
|
return A.runCommand({replSetGetStatus : 1}).syncingTo == bAddress;
|
}, msg:undefined at src/mongo/shell/assert.js:13
|
failed to load: /data/mci/shell/mongodb-mongo-master/jstests/noPassthrough/server6733.js
|
Attachments
Issue Links
- related to
-
SERVER-13582 jstests/noPassthrough/server6733.js call to replSetSyncFrom does not handle an expected failure case properly
-
- Closed
-