Skip to content
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
@BRONSOLO

Description

What you expected to happen?

weaver detects/claims pre-existing IPs attached to the weave bridge on node via

func findExistingAddresses(dockerCli *weavedocker.Client, bridgeName string) (addrs []ipam.PreClaim, err error) {

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:

netDevs, err := weavenet.GetNetDevsByVethPeerIds(pid, peerIDs)
.

Specifically, given the change of #3876, the following command only detects processes within the PID namespace of the weave-net pod:

pids, err := common.AllPids("/proc")

How to reproduce it?

  • Move the boltdb file so that the persisted data gets cleared
  • Rotate the weave-net pod in the kube-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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions