weave status showing targets, though no hosts were provided during weave launch

[AnilNeeluru]

What you expected to happen?

During weave launch, no hosts are specified as targeted hosts to connect. So i would expect, "weave status targets" output should show empty.

Example of how weave process running on Master host,,
root 2831 2814 4 Feb28 ? 05:08:41 /home/weave/weaver --port 6783 --name 5e:3c:a5:df:57:df --nickname an-dbmaster --datapath datapath --ipalloc-range 10.32.0.0/12 --dns-effective-listen-address 172.17.0.1 --dns-listen-address 172.17.0.1:53 --http-addr 127.0.0.1:6784 --status-addr 127.0.0.1:6782 --resolv-conf /var/run/weave/etc/resolv.conf --connlimit=100 --ipalloc-init consensus=3

What happened?

weave gets launched successfully, and initially it shows targets empty. some of the peers also gets discovered as for few peer hosts we are mentioning the initially launched weave IP as master to connect during weave launch.

But over a period of time, i see "weave status targets" getting filled up with all its peers discovered/connected. I expect, the targets should stay empty, as no hosts are given during weave launch.

Would like to understand on how "weave status targets" getting filled on Master Host ?

Not able to find any info on weave troubleshooting/faq. So posting here. Thanks for your help in advance !

How to reproduce it?

On Host1:
launch weave without any hosts to connect
on Host2/Host3/Host4:
launch weave with Host1 to connect

Expected Host 1 should have "weave status targets" empty always.
Expected Host1 in "weave status targets" in Host2/Host3/Host4: which is looking as expected.

Anything else we need to know?

Versions:

$ weave version
weave script 1.9.4
weave router 1.9.4
weave proxy  1.9.4
weave plugin 1.9.4

$ docker version
Docker version 19.03.0, build aeac949

$ uname -a
Linux an-dbmaster 4.4.0-173-generic #203-Ubuntu SMP Wed Jan 15 02:55:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

$ kubectl version
NA,

Logs:

$ docker logs weave

or, if using Kubernetes:

$ kubectl logs -n kube-system <weave-net-pod> weave

Network:

$ ip route
$ ip -4 -o addr
$ sudo iptables-save

[murali-reddy]

@AnilNeeluru You are using very old version of weave. Please try recent release. Its working as expected.