> I reported this upstream (see linked bug), and it got triaged and added to the kea2.3.0 milestone [1].
I can't find it in that page, do you have a direct link to the issue perhaps?
> I reported this upstream (see linked bug), and it got triaged and added to the kea2.3.0 milestone [1].
I can't find it in that page, do you have a direct link to the issue perhaps?