bootstrap issue with replicasets on 1.20.1 with VM on MAAS provider
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
High
|
Unassigned |
Bug Description
I'm trying to bootstrap Juju 1.20.1 using a MAAS provider. The node I'm bootstrapping on is a VM on an OrangeBox.
I hit repeated
2014-07-11 10:25:08 WARNING juju.replicaset replicaset.go:86 Initiate: fetching replication status failed: cannot get replica set status: can't get local.system.
Followed by
2014-07-11 10:25:08 INFO juju.worker.
2014-07-11 10:25:08 ERROR juju.cmd supercommand.go:323 cannot initiate replica set: cannot get replica set status: can't get local.system.
ERROR bootstrap failed: subprocess encountered error code 1
Stopping instance...
Bootstrap failed, destroying environment
ERROR subprocess encountered error code 1
Full log from bootstrap on http://
I was asked to grab some mongo logs, but I'm struggling to do that since the bootstrap nodes is torn down. So far this is 100% reproducible.
description: | updated |
tags: | added: bootstrap mongodb |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.21-alpha1 |
Changed in juju-core: | |
milestone: | 1.21-alpha1 → none |
Using a loopback mount of the VM's image, I can see the bootstrap errors in cloud-init- output. log but there are no logs from mongo (/var/log/mongo doesn't exist)