BIRD continues exporting routes but reports no exports

[Hugo Slabbert]

A slight update on this:

3f477ccb
<https://gitlab.nic.cz/labs/bird/-/commit/3f477ccb03ed99cf6754baaca179fcf791bcda55>
does appear to be in 2.0.7, which we're running, so if that's the issue
that may not be the problem.

This looked to be successful initially when upgrading to 2.0.10. But, I
then checked a box that was still running 2.0.7 and where we could repro
it. I simply restarted bird there, and then could no longer repro it.

So, just restarting bird at 2.0.7 was sufficient to clear the problem, at
least temporarily, and the bump to 2.0.10 then wasn't a clear test, given
that's obviously a fresh instance of bird running.

We'll try to validate if the problem eventually returns on the 2.0.7
box(es) after a restart, and if it does *not* return on the 2.0.10
instance, but we don't have a clear timeline at the moment on this if it's
something that pops up "in a while" of bird running.

On Thu, Mar 2, 2023 at 2:54 PM Hugo Slabbert <
hugo.slabbert at menlosecurity.com> wrote:

> Was this perhaps 3f477ccb
> <https://gitlab.nic.cz/labs/bird/-/commit/3f477ccb03ed99cf6754baaca179fcf791bcda55>
> ?
>
> Filters: Function body comparison result now used.
>> Function bodies were compared in post-parse time, yet the result was not
>> used and the functions were incorrectly considered the same as before.
>
>
>
> Now the result is used to reload affected protocols.
>
>
> On Thu, Mar 2, 2023 at 2:51 PM Hugo Slabbert <
> hugo.slabbert at menlosecurity.com> wrote:
>
>> 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 at 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
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20230302/c4185249/attachment.htm>