Bryan Boreham

Results 190 issues of Bryan Boreham

When running under Kubernetes, the probe will try to talk to kubelet on 10255, unsecured, if it doesn't know the node name. We should not assume unsecured access. There is...

k8s
chore
help-wanted
estimate/hours
good-first-issue

E.g. in this view, `kubernetes` should have the ship's wheel logo: ![image](https://user-images.githubusercontent.com/8125524/28382526-45be9336-6c73-11e7-8930-fb5aeb29802c.png) I can't see a way to do this obviously better than special-casing on the labels: ``` KUBERNETES LABELS...

feature
good-first-issue

E.g. this file: https://github.com/microservices-demo/microservices-demo/blob/master/deploy/kubernetes/manifests-policy/netpol-default-deny.yaml is using the old-style annotations.

[Did this because I was trying to use an IPVLan device and it barfs if you try to set its MAC address] If we don't do this it will adopt...

kind/bug
area/networking

Seen [here](https://weaveworks-foss.semaphoreci.com/jobs/77bb6c48-912a-484a-842a-ffa67f6697ab) for instance: ``` === RUN TestConcurrentVMCreation04:27 time="2021-01-13T18:32:10Z" level=info msg="Removed VM with name \"e2e-test-concurrent-vm-create-3\" and ID \"1dc7af60947f98b9\""04:27 time="2021-01-13T18:32:10Z" level=fatal msg="unable to lock \"/tmp/ignite-snapshot.lock\": open /tmp/ignite-snapshot.lock: no such file or...

As noted in the Travis docs: https://docs.travis-ci.com/user/pull-requests/#double-builds-on-pull-requests I suggest that one or other should be turned off because they are identical in most cases.

Stack trace: ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0xcc15be] goroutine 12 [running]: github.com/weaveworks/ignite/pkg/container.(*DHCPInterface).ServeDHCP(0xc0001868c0, 0xc0001bec00, 0x224, 0x5dc, 0x201, 0xc000639e90, 0xc0006...

Sometimes machines have multiple IP addresses, and the one you wish peers to connect to is not the same as the one you connect out on.

enhancement

Lock is not released until the `Send()` [returns](https://github.com/weaveworks/mesh/blob/58dbcc3e8e63eed7dd77f3a6286855ae8c8876c1/protocol_crypto.go#L131). Taken together with #125 this means it can hold a lock forever. Sender and receiver each maintain state including a sequence number,...

bug

We [set a deadline on reads](https://github.com/weaveworks/mesh/blob/58dbcc3e8e63eed7dd77f3a6286855ae8c8876c1/connection.go#L416) but not on writes. This means if something is blocking the other end of the connection we will wait forever. Since we expect connected...

bug