Update - the fix for ovirt-engine that Liran previously mentioned on this thread was merged.

@Michaal R about your question below, I don't think there is a workflow that fits all - it depends on the issue.
Even in this thread - the issue on the VDSM side required your help in validating the fix on your environment, while the fix in ovirt-engine could be validated by us with the VM specification you provided (we added a unit test with the specification of your VM btw). 
As I see it, this thread went well - you provided us with information that enabled us to identify the issues and validate their fixes, which is great

On Tue, Nov 21, 2023 at 3:41 PM Michaal R via Users <users@ovirt.org> wrote:
I'm curious... When code changes like this occur (as I've never been even adjacent to such things, even in my professional life), what's the workflow like? Are there things users that spark such changes can do to help in these situations (like testing and such)? I'll be honest, I'm kinda nerdy giddy about seeing how this thread plays out with this issue (or issues), as I've kinda always wanted to be able to submit something that could be made better, and even just know that an update to a product or service was because I made the report and submitted the evidence needed to help.

Sorry if that seems weird.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/4HPEEHXCLTQED6VV7CUMRT7DSQSD3PS4/