Hello,
I have an issue with a behaviour change in knot 3.4.1.
Before 3.4.1, trying to send a conf-abort command using knotc to knot when there was no
pending transaction properly returned an error, but since 3.4.1, instead of receiving an
error, the connection hangs, and failed after a timeout.
Some digging shows that this is due to a change in commit
69328dd7799253978605f7dac29175945971e63f
Instead of returning and error as it should, ctl_process skip the command processing when
it does not expect a conf-abort command.
Is this a bug, or is this behaviour intended ?
Just to give you some context about my use case, I wrote a daemon that is using libknot to
sync the dns configuration, and as knot does not supports multiple transaction, it has to
make sure there is no dangling transaction before trying to apply changes (in case the
daemon did crash while applying a previous change). Until 3.4.1, it did that by simply
sending a conf-abort before starting the new transaction.
Thanks