This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
Duplicate IP resulting from incorrect PID namespace #4005
Open
Description
What you expected to happen?
weaver
detects/claims pre-existing IPs attached to the weave
bridge on node via
Line 26 in 8c84763
What happened?
weaver
stopped using the host process namespace (via hotsPID) as of #3876, which was needed for detecting devices via the peer ids / process ids here:
Line 84 in 8c84763
Specifically, given the change of #3876, the following command only detects processes within the PID namespace of the weave-net
pod:
Line 79 in 8c84763
How to reproduce it?
- Move the boltdb file so that the persisted data gets cleared
- Rotate the
weave-net
pod in thekube-system
namespace - Rotate any pod once the
weave-net
pod comes back up - Notice how the IP assigned to the pod has already been assigned to another pod on the cluster
Anything else we need to know?
This is specifically for weave
running on k8s
.
Versions:
weave version 2.8.1
Metadata
Assignees
Labels
No labels
Activity