> I am not sure I would still call it a regression and it is certainly an annoying, but it can be workarounded.
it worked before, now it doesn't without manual intervention, that's the basic definition of a regression, no?
after all, there are _always_ workarounds for regressions, so I would not consider it appropriate to call a regression not-a-regression because there is some workaround available.
we are currently affected by this and need to figure out if the workaround is even an acceptable solution, because in a cloud environment you can't/don't want to manually patch libvirt xml for dozens of machines.
> I am not sure I would still call it a regression and it is certainly an annoying, but it can be workarounded.
it worked before, now it doesn't without manual intervention, that's the basic definition of a regression, no?
after all, there are _always_ workarounds for regressions, so I would not consider it appropriate to call a regression not-a-regression because there is some workaround available.
we are currently affected by this and need to figure out if the workaround is even an acceptable solution, because in a cloud environment you can't/don't want to manually patch libvirt xml for dozens of machines.