no primary found in replicaset

[joshuacox]

I've seen this error before on a few edge cases, but now that I have separated out the mongo chart, I get it consistently in the gymongonasium branch. You'll notice RC fail with logs like this:

$ docker logs d01
=> Starting app on port 3000...

/opt/reaction/dist/bundle/programs/server/node_modules/fibers/future.js:313
                                                throw(ex);
                                                ^
MongoError: no primary found in replicaset

log into a mongo container and verify "no replset config has been received":

> cfg = rs.config()
2017-12-10T15:09:27.831+0000 E QUERY    [thread1] Error: Could not retrieve replica set config: {
        "info" : "run rs.initiate(...) if not yet done for the set",
        "ok" : 0,
        "errmsg" : "no replset config has been received",
        "code" : 94,
        "codeName" : "NotYetInitialized"
} :
rs.conf@src/mongo/shell/utils.js:1288:11
@(shell):1:7

[joshuacox]

this was due to me following the documentation for the chart and not looking at the yaml itself this has been fixed in #b58f7