New commits:
commit fa9b914103be969cab259079863c2a3c33f722d1
Merge: 71652224b6 99440b3014
Author: Andrew Cagney <[email protected]>
Date: Thu Mar 5 15:34:51 2026 -0500
Merge updown: log VTI ip commands
commit 99440b30146c8038ea8eed2a2a794d5606a5a207
Author: Andrew Cagney <[email protected]>
Date: Thu Mar 5 15:34:07 2026 -0500
testing: expect VTI updown ip commands to appear in the logs
commit 2880e1e0f3ad8809d829b0b4b6ccd573ffa934fb
Author: Andrew Cagney <[email protected]>
Date: Thu Mar 5 13:51:43 2026 -0500
updown: log VTI ip commands as they are run
plutodebug=updown is proving to be too big a hammer when
debugging; this is a middle ground.
Yes, this goes against the dogma that the updown scripts only log
errors. But:
- VTI is already logging other stuff
I suspect due to previous debugging efforts
- seeing an error isn't much use without the corresponding command
(I wonder of the non-VTI case should also allow this)
see #2601 Fix the handling of metrics in routes on VTI interfaces.
_______________________________________________
Swan-commit mailing list -- [email protected]
To unsubscribe send an email to [email protected]
