ah, right, apologies.

bird 2.0.7-4.1 on Debian 11.6, kernel 5.10.136-1

Looks like 2.0.7 was released Oct 16 2019 (https://bird.network.cz/?download), so a fair chance we might be hitting this? It looks like something from 2.0.10 is available from the bullseye backports, with the most recent being 2.0.12 in bookworm or sid. I'll look at pulling one of those in to validate.

...where changes in functions sometimes got ignored.

This might be reaching, but would that explain the difference between what's shown in route export status output versus what's actually being exported?

On Thu, Mar 2, 2023 at 2:39 PM Maria Matejka via Bird-users <bird-users@network.cz> wrote:

Hello!

> We've tried adding a sleep between when the include snippet that changes
> the DRAIN_NODE value is written and when we hit `birdc configure`, but
> that doesn't appear to make any difference. If we execute `birdc
> configure` *twice*, though, everything's fine: The actual exports are
> stopped. That's true without any sleep or break between running
> configure as well; literally just `birdc configure` back to back in the
> script that manages this.
>
> We do not see any indication of issues in the `birdc configure` runs or
> in BIRD's logs.

You are not disclosing the version of BIRD you are using. I vaguely
remember that we fixed this kind of bug several years ago where changes
in functions sometimes got ignored.

Thus if you are not using a recent BIRD version, you are probably
hitting that old bug.

Maria