Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

weave dns doesn't remove entries for containers that die super young #1281

Closed
tomwilkie opened this issue Aug 11, 2015 · 3 comments
Closed
Assignees
Milestone

Comments

@tomwilkie
Copy link
Contributor

Which is what you see in weave status and docker ps

vagrant@ubuntu-14:~/src/github.com/weaveworks/service$ weave status
weave router git-073836905a97
Our name is aa:4f:5c:2c:f8:7d(ubuntu-14)
Encryption off
Peer discovery on
Sniffing traffic on &{1102 65535 ethwe b2:37:e1:49:ac:c0 up|broadcast|multicast}
MACs:
6a:93:5b:00:1b:ad -> aa:4f:5c:2c:f8:7d(ubuntu-14) (2015-08-11 09:59:44.287784384 +0000 UTC)
d2:63:6d:68:ec:d6 -> aa:4f:5c:2c:f8:7d(ubuntu-14) (2015-08-11 10:06:30.182731544 +0000 UTC)
ee:5c:de:f3:5f:4d -> aa:4f:5c:2c:f8:7d(ubuntu-14) (2015-08-11 10:00:26.234948009 +0000 UTC)
b6:d0:88:77:89:a8 -> aa:4f:5c:2c:f8:7d(ubuntu-14) (2015-08-11 09:59:44.29417889 +0000 UTC)
f6:da:96:f2:e1:6d -> aa:4f:5c:2c:f8:7d(ubuntu-14) (2015-08-11 10:06:30.183672974 +0000 UTC)
Peers:
aa:4f:5c:2c:f8:7d(ubuntu-14) (v0) (UID 29660472120172713)
Routes:
unicast:
aa:4f:5c:2c:f8:7d -> 00:00:00:00:00:00
broadcast:
aa:4f:5c:2c:f8:7d -> []
Direct Peers:
Reconnects:

Allocator range [10.32.0.0-10.48.0.0)
Owned Ranges:
  10.32.0.0 -> aa:4f:5c:2c:f8:7d (ubuntu-14) (v314)
Allocator default subnet: 10.32.0.0/12

WeaveDNS (aa:4f:5c:2c:f8:7d)
  listening on 0.0.0.0:53, for domain weave.local.
  response ttl 1

c26978e5ee4d: scope-app-1.weave.local. [10.32.0.8]
vagrant@ubuntu-14:~/src/github.com/weaveworks/service$ weave dns-remove 10.32.0.8 c26978e5ee4d 
Error: No such container: c26978e5ee4d
@tomwilkie
Copy link
Contributor Author

Actual problem is I have a stale dns entry, and the weave script won't let me remove it.

@tomwilkie
Copy link
Contributor Author

hmmm

vagrant@ubuntu-14:~/src/github.com/weaveworks/service$ curl -H "Accept: application/json" http://172.17.1.33:6784/name | jq .
...
  {
    "Tombstone": 0,
    "Version": 0,
    "Hostname": "scope-app-1.weave.local.",
    "Addr": "10.32.0.8",
    "Origin": "aa:4f:5c:2c:f8:7d",
    "ContainerID": "c26978e5ee4d8278a2e17cce3563641ebd9f9b5dbcafbfec048ebaf700680148"
  },
...

@tomwilkie
Copy link
Contributor Author

DEBU: 2015/08/10 17:14:49.457630 [allocator aa:4f:5c:2c:f8:7d]: Allocated 10.32.0.8 for c26978e5ee4d8278a2e17cce3563641ebd9f9b5dbcafbfec048ebaf700680148 in [10.32.0.1-10.47.255.255)
INFO: 2015/08/10 17:14:49.735533 Discovered local MAC 96:ba:62:d0:53:f5
DEBU: 2015/08/10 17:14:49.984945 [allocator aa:4f:5c:2c:f8:7d]: Container c26978e5ee4d8278a2e17cce3563641ebd9f9b5dbcafbfec048ebaf700680148 died; released addresses
INFO: 2015/08/10 17:14:50.093747 [nameserver aa:4f:5c:2c:f8:7d] adding entry scope-app-1.weave.local. -> 10.32.0.8
INFO: 2015/08/10 17:14:50.178946 [gossipdns] 'c26978e5ee4d8278a2e17cce3563641ebd9f9b5dbcafbfec048ebaf700680148' is not running: removing
INFO: 2015/08/10 17:14:50.179791 [nameserver aa:4f:5c:2c:f8:7d] tombstoning hostname=scope-app-1.weave.local, containerid=c26978e5ee4d8278a2e17cce3563641ebd9f9b5dbcafbfec048ebaf700680148, ip=10.32.0.8

@tomwilkie tomwilkie changed the title weave dns-remove doesn't accept shortened container ids weave dns doesn't remove entries for containers that die super young Aug 11, 2015
@tomwilkie tomwilkie self-assigned this Aug 11, 2015
rade added a commit that referenced this issue Aug 11, 2015
Remove DNS entries for dead containers when adding correctly.

Fixes #1281.
@rade rade modified the milestone: 1.1.0 Aug 12, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants