juju 1.25.0: cannot initiate replica set: cannot dial mongo to initiate replicaset: no reachable servers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Autopilot Log Analyser |
Fix Committed
|
Undecided
|
Andreas Hasenack | ||
juju-core |
Expired
|
Undecided
|
Unassigned |
Bug Description
We're hitting these failures:
Reading package lists...
Building dependency tree...
Reading state information...
cloud-image-utils is already the newest version.
cloud-image-utils set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
tmux is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Attempt 1 to download tools from https:/
tools from https:/
0419fcde2d571a0
2016-01-19 14:36:45 INFO juju.cmd supercommand.go:37 running jujud [1.25.0-
2016-01-19 14:36:45 INFO juju.network network.go:242 setting prefer-ipv6 to false
2016-01-19 14:36:45 INFO juju.agent identity.go:22 writing system identity file
2016-01-19 14:36:45 INFO juju.mongo mongo.go:175 Ensuring mongo server is running; data directory /var/lib/juju; port 37017
2016-01-19 14:36:45 INFO juju.mongo mongo.go:339 installing juju-mongodb
2016-01-19 14:36:45 INFO juju.utils.
2016-01-19 14:44:33 INFO juju.worker.
2016-01-19 14:44:33 ERROR juju.cmd supercommand.go:429 cannot initiate replica set: cannot dial mongo to initiate replicaset: no reachable servers
ERROR failed to bootstrap environment: subprocess encountered error code 1
2016-01-19 14:44:34,309 [ERROR] oil_ci.juju.client: Calling "juju bootstrap" failed!
Failure is similar to bug 1423273 which was marked as invalid and bug 1355782.
These are automated builds and we don't currently collect /var/log/syslog
Changed in autopilot-log-analyser: | |
assignee: | nobody → Andreas Hasenack (ahasenack) |
status: | New → In Progress |
Changed in autopilot-log-analyser: | |
status: | In Progress → Fix Committed |
Larry, I'm not sure there's much we can tell from here without /var/log/syslog to look at what mongo's doing. Is there any way to collect that in the automated build?