-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Fully Compatible
-
ALL
Sporadic failures occur in in 4_upgrade_cluster.js. Example: https://mci.10gen.com/task/mongodb_mongo_master_linux_64_194522f2427a5bf9dcc813b224b943923790cc94_15_04_02_16_38_05_multiversion_linux_64
----
Cluster upgraded.
----
m29002| 2015-04-03T06:07:28.894+0000 I NETWORK [initandlisten] connection accepted from 127.0.0.1:44390 #1 (1 connection now open)
m30999| 2015-04-03T06:07:28.897+0000 I SHARDING [conn1] couldn't find database [config] in config db
m30999| 2015-04-03T06:07:28.934+0000 I NETWORK [conn1] Detected bad connection created at 1428041237141682 microSec, clearing pool for ip-10-153-130-203:29002 of 0 connections
m30999| 2015-04-03T06:07:28.934+0000 W SHARDING [conn1] error creating initial database config information :: caused by :: database metadata write failed: { ok: 0, code: 25, errmsg: "Could not verify that config servers were active and reachable before write" }
2015-04-03T06:07:28.940+0000 E QUERY Error: error: {
"$err" : "error creating initial database config information :: caused by :: database metadata write failed: { ok: 0, code: 25, errmsg: \"Could not verify that config servers were active and reachable before write\" }",
"code" : 25
}
at Error (<anonymous>)
at DBQuery.next (src/mongo/shell/query.js:265:15)
at DBCollection.findOne (src/mongo/shell/collection.js:190:22)
at printShardingStatus (src/mongo/shell/shardingtest.js:659:55)
at ShardingTest.printShardingStatus (src/mongo/shell/shardingtest.js:633:5)
at /data/mci/shell/src/jstests/multiVersion/4_upgrade_cluster.js:127:4 at src/mongo/shell/query.js:265
failed to load: /data/mci/shell/src/jstests/multiVersion/4_upgrade_cluster.js
The first build I see this on is: https://mci.10gen.com/task/mongodb_mongo_master_linux_64_14ce8911246fa6a9ae238d69fac05b169a66e6d4_15_03_31_15_34_06_multiversion_linux_64
which introduced a commit which may be related to config servers.