BABEL does not update routing table when reset interface

[Shbinging]

Description

+------+ +------+
| R1 |-------- | R2 |--------
+------+ +------+
r1-eth0 r2-eth0 r2-eth1

r1 conf

int r1-eth0
    ipv6 address fe80:0:0:0:6731:0:59d3:a4/64
    ip address 8.8.8.8/20
    babel wired

router babel
    network r1-eth0
    redistribute ipv4 connected

r2 conf

int r2-eth0
    ipv6 address fe80:0:0:0:271a:0:2938:4f/64
    ip address 8.8.8.9/20
    babel wired

    
int r2-eth0
    ipv6 address fe80:0:0:0:271a:0:3000:5e/64
    ip address 10.10.10.9/20
    babel wired
    
router babel
    network r2-eth0
    redistribute ipv4 connected

r1's routing table

8.8.0.0/20 metric 96 refmetric 0 id 26:d8:32:ff:fe:09:21:64 seqno 25796 age 5 via r1-eth0 neigh fe80::271a:0:3000:5e nexthop 8.8.8.9 (feasible)
10.10.0.0/20 metric 96 refmetric 0 id 26:d8:32:ff:fe:09:21:64 seqno 25796 age 5 via r1-eth0 neigh fe80::271a:0:3000:5e nexthop 8.8.8.9 (installed)
8.8.0.0/20 metric 0 (exported)

When we reset r1-eth0, the router table of r1 will not show subnetwork in r2-eth1.

router babel
  no network r1-eth0
  network r1-eth0

r1's routing only contains

8.8.0.0/20 metric 0 (exported)

Version

10.2

How to reproduce

Reset one interface, for example

router babel
  no network r1-eth0
  network r1-eth0

Expected behavior

Routing table is updated.

Actual behavior

Routing table is not updated.

Additional context

No response

Checklist

• I have searched the open issues for this bug.
• I have not included sensitive information in this report.

[Shbinging]

Reset interface will cause interface to stop operate, which is fixed. #10893

[github-actions]

This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose label in order to avoid having this issue closed.

[frrbot]

This issue will be automatically closed in the specified period unless there is further activity.