Canonical Juju

Juju fails trying to bootstrap with two NICs (bridged and physical)

Bug #1840661 reported by Simon Richardson
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

When trying to bootstrap to a MAAS machine with two NICS, one bridged and one physical in the same subnets causes juju to fail.

```
ERROR failed to start mongo: cannot initiate replica set: cannot get replica set status: no replset config has been received
2019-08-16 11:18:00 DEBUG cmd supercommand.go:502 error stack:
cannot get replica set status: no replset config has been received
/home/simon/go/src/github.com/juju/juju/worker/peergrouper/initiate.go:64: cannot initiate replica set
/home/simon/go/src/github.com/juju/juju/cmd/jujud/agent/bootstrap.go:297: failed to start mongo
2019-08-16 11:18:00 DEBUG juju.cmd.jujud main.go:200 jujud complete, code 0, err <nil>
12:18:01 ERROR juju.cmd.juju.commands bootstrap.go:697 failed to bootstrap model: subprocess encountered error code 1
12:18:01 DEBUG juju.cmd.juju.commands bootstrap.go:698 (error details: [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:772: failed to bootstrap model} {github.com/juju/juju/environs/bootstrap/bootstrap.go:562: } {github.com/juju/juju/environs/bootstrap/bootstrap.go:530: } {subprocess encountered error code 1}])
12:18:01 DEBUG juju.cmd.juju.commands bootstrap.go:1332 cleaning up after failed bootstrap
12:18:01 INFO juju.provider.common destroy.go:21 destroying model "controller"
12:18:01 INFO juju.provider.common destroy.go:32 destroying instances
12:18:02 INFO juju.provider.common destroy.go:56 destroying storage
12:18:02 INFO cmd supercommand.go:508 command finished
```

See the full stack trace https://paste.ubuntu.com/p/tVdPQz5KJg/

Richard Harding (rharding)
Changed in juju:
status: New → Confirmed
status: Confirmed → Triaged
importance: Undecided → High
Revision history for this message
Valentin Fischer (servergeek) wrote :
Download full text (9.5 KiB)

Hi guys,

Any progress on this ? I'm trying to deploy juju on microstack and I'm hit by this.

....
2019-11-05 10:43:24 INFO juju.replicaset replicaset.go:60 Unsuccessful attempt to initiate replicaset: No host described in new configuration 1 for replica set juju maps to this node
2019-11-05 10:43:24 INFO juju.replicaset replicaset.go:58 Initiating replicaset with config: {
  Name: juju,
  Version: 1,
  Protocol Version: 0,
  Members: {
    {1 "10.20.20.215:37017" juju-machine-id:0 voting},
  },
}
2019-11-05 10:43:29 INFO juju.replicaset replicaset.go:60 Unsuccessful attempt to initiate replicaset: No host described in new configuration 1 for replica set juju maps to this node
2019-11-05 10:43:29 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:30 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:30 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:31 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:31 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:32 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:32 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:33 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:33 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:34 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:34 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:35 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:35 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:36 WARNING juju.replicaset replicaset.go:136 Initiate: fetching replication status failed: cannot get replica set status: no replset config has been received
2019-11-05 10:43:36 WARNING juju.replicaset replicaset.go:136 ...

Read more...

Revision history for this message
Heather Lanigan (hmlanigan) wrote :

I've seen it trying to bootstrap a manual cloud with a machine created in openstack. The machine is newly constructed, did nothing to it. It does have a FIP. Nothing special in /etc/hosts.

For me:
{1 "10.20.20.215:37017" juju-machine-id:0 voting},
    ^^^^^^ is the FIP

Revision history for this message
Heather Lanigan (hmlanigan) wrote :

Must be something to do with the FIP. I was able to do a manual bootstrap of the same machine recreated from a machine in the same private network, no FIP on the machine this time.

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: High → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.