diff options
| author | zyxwvu Shi <shiyuchen.syc@bytedance.com> | 2021-05-26 10:33:55 +0800 |
|---|---|---|
| committer | zyxwvu Shi <shiyuchen.syc@bytedance.com> | 2021-07-06 19:51:39 +0800 |
| commit | 3057d1e45af0c7789a3b7adfcae882b0234fbf4c (patch) | |
| tree | 50ecfddaff20e918dd32722f4b496efb6b36d3a8 | |
| parent | 56fd30a30336ce57886f4a035fad250a766c3c26 (diff) | |
bgpd: Do not delete peer_af when deactivating peer-group.
There is no peer_af allocated in `peer_activate`. Trying to delete
the structure just results in an no-op and a error return value.
The error message "couldn't delete af structure for peer" is
unexpected.
Signed-off-by: zyxwvu Shi <shiyuchen.syc@bytedance.com>
| -rw-r--r-- | bgpd/bgpd.c | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/bgpd/bgpd.c b/bgpd/bgpd.c index 197133cbb4..2f35bbf9e7 100644 --- a/bgpd/bgpd.c +++ b/bgpd/bgpd.c @@ -2315,13 +2315,6 @@ int peer_deactivate(struct peer *peer, afi_t afi, safi_t safi) peer->afc[afi][safi] = 0; group = peer->group; - if (peer_af_delete(peer, afi, safi) != 0) { - flog_err( - EC_BGP_PEER_DELETE, - "couldn't delete af structure for peer %s(%s, %s)", - peer->host, afi2str(afi), safi2str(safi)); - } - for (ALL_LIST_ELEMENTS(group->peer, node, nnode, tmp_peer)) { ret |= non_peergroup_deactivate_af(tmp_peer, afi, safi); } |