Hello,

After upgrading to 2026.04.10-0031-rolling, I started seeing a constantly running python process consuming around 6 - 50% CPU, even when the system is idle.

Problem
The process continuously executes:

/bin/cli-shell-api --show-active-only showConfig interfaces
This happens in a loop and does not stop.

Debugging
I attached strace to the process and observed repeated executions:

strace: Process 6134 attached

strace: Process 16362 attached
[pid 16362] execve("/bin/cli-shell-api", ["/bin/cli-shell-api", "--show-active-only", "showConfig", "interfaces"], ...) = 0
[pid 16362] +++ exited with 0 +++
--- SIGCHLD ...

strace: Process 16363 attached
[pid 16363] execve("/bin/cli-shell-api", ["/bin/cli-shell-api", "--show-active-only", "showConfig", "interfaces"], ...) = 0
[pid 16363] +++ exited with 0 +++
--- SIGCHLD ...

... repeats continuously

It looks like something is polling interface configuration in a tight loop.

Configuration note
This is a very minimal setup — I am only using BGP (no complex services or additional features configured).

Expected behavior
The system should not continuously call cli-shell-api when there are no configuration changes, and CPU usage should remain low.

Actual behavior
A python process continuously spawns cli-shell-api, causing constant CPU load (~6 - 50%).

Regression
After rolling back to 2026.04.01-0034-rolling, the issue is no longer reproducible:

CPU usage returns to normal

Looping behavior disappears

Conclusion
This appears to be a regression introduced in 2026.04.10-0031-rolling, possibly related to a component repeatedly querying interface configuration.