Description

Hello, I found in the function clusterLeave()

func (nDB *NetworkDB) clusterLeave() error {
	mlist := nDB.memberlist


	if err := nDB.sendNodeEvent(NodeEventTypeLeave); err != nil {
		log.G(context.TODO()).Errorf("failed to send node leave: %v", err)
	}


	if err := mlist.Leave(time.Second); err != nil {
		return err
	}


	// cancel the context
	nDB.cancelCtx()


	for _, t := range nDB.tickers {
		t.Stop()
	}


	return mlist.Shutdown()
}

If the mlist.Leave() return err, the nDB.cancelCtx() below will not get executed.

And it will lead the <-nDB.ctx.Done in triggerFunc() blocked persistently, so the goroutine leak.

blocking position:

Reproduce

I reproduce the bug by goleak.
Firstly, I modified the judge condition from err != nil to err == nil. Because I don't know how to let err != nil, the change only to make the return err can be executed easier. I'm not sure whether the change can lead other influences.
Normally:

	if err := mlist.Leave(time.Second); err != nil {
		return err
	}

After modified:

	if err := mlist.Leave(time.Second); err == nil {
		return err
	}

Then I used goleak to test in these test function related the funciton.

Expected behavior

No response

docker version

latest

docker info

latest

Additional Info

In short, I think the bug is caused by return but have not called the cancelFunc. I have tried to describe it in detail.