OTBR addon crashes after upgrade to core 2024.5.2 -> 2024.5.3

[barrelful]

The problem

OTBR integration stopped working with status: Failed setup, will retry.

What version of Home Assistant Core has the issue?

core-2024.5.3

What was the last working version of Home Assistant Core?

core-2024.5.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

otbr

Link to integration documentation on our website

https://www.home-assistant.io/integrations/otbr/

Diagnostics information

On the logs of the addon I see:

[17:58:15] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
otbr-agent[175]: 00:00:27.207 [N] Mle-----------: RLOC16 a400 -> fffe
otbr-agent[175]: 00:00:27.285 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[175]: 00:00:33.785 [N] RouterTable---: Allocate router id 41
otbr-agent[175]: 00:00:33.785 [N] Mle-----------: RLOC16 fffe -> a400
otbr-agent[175]: 00:00:33.789 [N] Mle-----------: Role detached -> leader
otbr-agent[175]: 00:00:33.789 [N] Mle-----------: Partition ID 0x44d76dc9
otbr-agent[175]: 00:00:33.811 [W] Platform------: [netif] ADD [U] fd1b:2449:e0f:4c96:0:ff:fe00:a400 failed (InvalidArgs)
otbr-agent[175]: 00:00:33.811 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:33.812 [W] Platform------: [netif] ADD [U] fd1b:2449:e0f:4c96:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[175]: 00:00:33.812 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[175]: 00:00:34.314 [W] Platform------: [netif] ADD [U] fd1b:2449:e0f:4c96:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[175]: 00:00:34.314 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:34.314 [W] Platform------: [netif] ADD [U] fd1b:2449:e0f:4c96:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[175]: 00:00:34.315 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:34.469 [W] Platform------: [netif] ADD [U] fdc9:3007:f70b:1:ee25:e8f3:e59b:630d failed (InvalidArgs)
otbr-agent[175]: 00:00:34.469 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:44.750 [W] Platform------: [netif] ADD [U] fd1b:2449:e0f:4c96:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[175]: 00:00:44.750 [W] Platform------: [netif] Failed to process event, error:InvalidArgs

Example YAML snippet

N/A

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (otbr) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of otbr can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign otbr Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

otbr documentation
otbr source
_{^{(message by IssueLinks)}}

[barrelful]

@puddly maybe related to #117089 ?

[puddly]

That PR just updates a translation string. Not related.

[agners]

The InvalidArgs messages are quite common and usually don't indicate a fatal error:

otbr-agent[175]: 00:00:33.812 [W] Platform------: [netif] Failed to process event, error:InvalidArgs

Can you share the Core logs? It should have more details why setup of the integration fails.

[barrelful]

@agners that is correct. I reverted the backup from Core 2024.5.2 and it is back working as normal but logs still have error:InvalidArgs.

[barrelful]

Actually I re-updated, and it seems to be working. Not sure then what was the cause. But then I close this issue until I have it again.

[barrelful]

Now it happened again upgrading from 2024.5.4 -> 2024.5.5.

What makes me puzzled is the simple fact of restoring the backup to 2024.5.4 and upgrading again fixes the issue, and also not very handy.

[agners]

it is back working

How do you determine working/non-working exactly?