local provider use the wrong interface

[Patrick Hetu]

I've got this bug bootstrapping the local provider:

[initandlisten] connection accepted from 10.36.0.35:42103 #2 (1 connection now open)
[conn2] assertion 16550 not authorized for query on local.system.replset ns:local.system.replset query:{}
[conn2] ntoskip:0 ntoreturn:-1
[conn2] end connection 10.36.0.35:42103 (0 connections now open)
2014-11-13 20:08:03 DEBUG juju.worker.peergrouper initiate.go:67 replica set initiation failed, will retry: cannot get replica set configuration: cannot get replset config: not authorized for query on local.system.replset

If got an external (eth0) network in 10.36.0.0/24 and an internal (lxcbr0) in 10.3.0.0/24.
It looks like a juju is picking the 10.36.0.0/24 network instead of 10.3.0.0.
I was wondering if there is anything I can do to fix that?

Maybe Juju could sort is network interface list by class so I could change the lxc bridge and use a class C address
and then Juju would choose the right interface.

The error in /var/log/syslog:

mongod.37017[26007]: Thu Nov 13 15:08:53.593 [rsStart] replSet can't get local.system.replset config from self or any seed (EMPTYCONFIG)
mongod.37017[26007]: Thu Nov 13 15:08:58.150 [initandlisten] connection accepted from 10.36.0.35:41847 #12 (1 connection now open)
mongod.37017[26007]: Thu Nov 13 15:08:58.154 [conn12] assertion 16550 not authorized for query on local.system.replset ns:local.system.replset query:{}
mongod.37017[26007]: Thu Nov 13 15:08:58.154 [conn12] ntoskip:0 ntoreturn:-1
mongod.37017[26007]: Thu Nov 13 15:08:58.154 [conn12] end connection 10.36.0.35:41847 (0 connections now open)
 mongod.37017[26007]: Thu Nov 13 15:08:58.989 [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
mongod.37017[26007]: Thu Nov 13 15:08:58.989 [signalProcessingThread] now exiting
 mongod.37017[26007]: Thu Nov 13 15:08:58.989
mongod.37017[26007]: dbexit:

juju bootstrap complet error:

2014-11-13 20:08:01 INFO juju.cmd supercommand.go:37 running jujud [1.20.11.1-trusty-amd64 gc]
2014-11-13 20:08:01 DEBUG juju.agent agent.go:377 read agent config, format "1.18"
2014-11-13 20:08:01 INFO juju.provider.local environprovider.go:42 opening environment "local"
2014-11-13 20:08:02 DEBUG juju.cmd.jujud bootstrap.go:210 starting mongo
2014-11-13 20:08:02 DEBUG juju.cmd.jujud bootstrap.go:235 calling ensureMongoServer
2014-11-13 20:08:02 INFO juju.mongo mongo.go:171 Ensuring mongo server is running; data directory /var/lib/lxc/local; port 37017
2014-11-13 20:08:02 INFO juju.mongo mongo.go:326 installing juju-mongodb
2014-11-13 20:08:02 INFO juju.utils.apt apt.go:132 Running: [apt-get --option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install juju-mongodb]
2014-11-13 20:08:03 DEBUG juju.mongo mongo.go:275 using mongod: /usr/lib/juju/bin/mongod --version: "db version v2.4.10\nThu Nov 13 15:08:03.085 git version: nogitversion\n"
2014-11-13 20:08:03 DEBUG juju.worker.peergrouper initiate.go:41 Initiating mongo replicaset; dialInfo &mgo.DialInfo{Addrs:[]string{"127.0.0.1:37017"}, Direct:false, Timeout:300000000000, FailFast:false, Database:"", Source:"", Service:"", Mechanism:"", Username:"", Password:"", PoolLimit:0, DialServer:(func(*mgo.ServerAddr) (net.Conn, error))(nil), Dial:(func(net.Addr) (net.Conn, error))(0x5bef10)}; memberHostport "10.0.3.1:37017"; user ""; password ""
2014-11-13 20:08:03 DEBUG juju.mongo open.go:96 connection failed, will retry: dial tcp 127.0.0.1:37017: connection refused
2014-11-13 20:08:03 DEBUG juju.mongo open.go:96 connection failed, will retry: dial tcp 127.0.0.1:37017: connection refused
2014-11-13 20:08:03 INFO juju.mongo open.go:104 dialled mongo successfully
2014-11-13 20:08:03 DEBUG juju.worker.peergrouper initiate.go:67 replica set initiation failed, will retry: cannot get replica set configuration: cannot get replset config: not authorized for query on local.system.replset

[Dimiter Naydenov (dimitern)]

This is the inverse issue of bug 1416928, but both cases - local and non local environments using lxcbr0 correctly or not - are resolved by the fix for that bug, so I'm marking this as duplicate.