As reported in the linked forum thread; comprehensive details provided therein. To be reproduced with (some version of) the provided case, however, it seems clear that the legacy thread lock is no longer appropriate after the move to async for handlers /config, /config-sync (https://vyos.dev/T7588) , and in fact dangerous for at least the second case.
Description
Description
Details
Details
- Version
- -
- Is it a breaking change?
- Perfectly compatible
- Issue type
- Bug (incorrect behavior)
- Forum thread
- https://forum.vyos.io/t/vyos-https-api-becomes-unresponsive-during-concurrent-config-file-load-operations/17278
Related Objects
Related Objects
- Mentioned In
- T9307: http-api: concurrent libvyosconfig entry from configure threadpool and event loop crashes vyos-http-api with SIGSEGV
rVYOSONEXe0f173bba7fd: Merge pull request #4976 from routerarchitects/http-api-deadlock-fix
rVYOSONEX5b47c96a6d1f: http-api: T8235: Use asyncio lock to prevent deadlock in config-file handler - Mentioned Here
- T7588: Vyconf: Call libvyosconfig functions from main thread under http-api