Requesting exception for VEP 24 (beta) and VEP 192

[Alexander Wels]

I am requesting an exception to graduate VEP 24 [0] to beta (decentralized live migration). All needed PRs are open and small; they just need to get through CI which is congested right now.

I also request an exception for VEP 192 [1]. The PR is posted, but its CI is failing because of a flaky test that another PR of mine should fix. Also finding someone to review has been difficult.

Alexander 

[0] https://github.com/kubevirt/enhancements/issues/24

[1] https://github.com/kubevirt/enhancements/issues/192

[Alex Kalenyuk]

Hey @Jed Lejosne - just making sure it's okay to interpret the approval as the exception being granted. Also, cc @Itamar Holder for awareness 🙏

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/CAKDnqXYtWaxOqrimX_k6aog7u7UETj6%2ByznwgFOrGdYCJYxm4A%40mail.gmail.com.

[Luboslav Pivarc]

Hi Alex,

Please write 2 separate emails next time for clearer separation and streamlined communication. Please also include all the requested points, as written in https://github.com/kubevirt/enhancements#exceptions  ref:
"""
Justification for exception
Additional time period that is required
In case of exception not being granted, what is the impact? (Think about graduation, maturity of the feature, user impact, etc.)
"""

For the VEP 24:

1. The tracking issue doesn't track changes in Beta. Please attend to it.

2. Unfortunately we still have tests being quarantine, therefore the exception cannot be granted as it is a requirement. Again please document the work on the issue.

For the VEP 192:

1. The tracking issue doesn't track changes. Please attend to it.

2. The work was not merged within one week of the original deadline nor was the required time extension mentioned. Therefore this should be considered missed for release 1.9.

It is unfortunate to see this complex feature missing the target again. I am concerned that no red flags were raised during the process. I would like to offer myself as shepherd for the next cycle for this feature.

-Lubo

To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/CAHahevez4vxohbEMxGaNgyKSSrsbauZawX%2BT8GQy8rmyTicRYw%40mail.gmail.com.

[Alexander Wels]

It's Alexander, not Alex

I thought I was following the process exactly, but apparently not. I asked for this exception 8 days ago, and no one mentioned, "Hey, you are not doing this right.Please adjust it. I thought I explained that my PRs were stuck in CI congestion, and you are aware that CI (in particular the check flakes) is failing frequently on the infrastructure right now. So it took me a long time to get the critical fix merged (it is finally merged, by the way), which will allow me to actually unquarantine the tests. I also had some drive by reviews where someone asked why I was doing something, and after I explained or changed the code to address the comment, and that reviewer ghosted me. And I had to explain to the approver that the reviewer wasn't responding after I addressed their comments, asking for approval.

Anyway, I understand the process is the process, and I didn't follow it correctly.

On Wed, Jul 1, 2026 at 3:38 PM 'Luboslav Pivarc' via kubevirt-dev <kubevi...@googlegroups.com> wrote:

Hi Alex,

Please write 2 separate emails next time for clearer separation and streamlined communication. Please also include all the requested points, as written in https://github.com/kubevirt/enhancements#exceptions  ref:
"""
Justification for exception
Additional time period that is required
In case of exception not being granted, what is the impact? (Think about graduation, maturity of the feature, user impact, etc.)
"""

For the VEP 24:

1. The tracking issue doesn't track changes in Beta. Please attend to it.

Added the missing links.

 

2. Unfortunately we still have tests being quarantine, therefore the exception cannot be granted as it is a requirement. Again please document the work on the issue.

Well the feature is there, the bugs are fixed, and the tests will come out of quarantine (since the fix was merged). The ONLY reason this is not beta is because of the process and the problems with CI.

 

For the VEP 192:

1. The tracking issue doesn't track changes. Please attend to it.

Added the missing links.

 

2. The work was not merged within one week of the original deadline nor was the required time extension mentioned. Therefore this should be considered missed for release 1.9.

It is unfortunate to see this complex feature missing the target again. I am concerned that no red flags were raised during the process. I would like to offer myself as shepherd for the next cycle for this feature.

It is unfortunate, this is an extension to the decentralized live migration. So this would have been the first version where the alpha of that would be available. I guess we will have to wait for version 1.10

 

-Lubo

On Tue, Jun 30, 2026 at 10:30 AM 'Alex Kalenyuk' via kubevirt-dev <kubevi...@googlegroups.com> wrote:

Hey @Jed Lejosne - just making sure it's okay to interpret the approval as the exception being granted. Also, cc @Itamar Holder for awareness 🙏

On Wed, Jun 24, 2026 at 2:40 AM 'Alexander Wels' via kubevirt-dev <kubevi...@googlegroups.com> wrote:

I am requesting an exception to graduate VEP 24 [0] to beta (decentralized live migration). All needed PRs are open and small; they just need to get through CI which is congested right now.

I also request an exception for VEP 192 [1]. The PR is posted, but its CI is failing because of a flaky test that another PR of mine should fix. Also finding someone to review has been difficult.

Alexander 

[0] https://github.com/kubevirt/enhancements/issues/24

[1] https://github.com/kubevirt/enhancements/issues/192

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/CAKDnqXYtWaxOqrimX_k6aog7u7UETj6%2ByznwgFOrGdYCJYxm4A%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/CAHahevez4vxohbEMxGaNgyKSSrsbauZawX%2BT8GQy8rmyTicRYw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/CAFTR0GW%3DoPpbeg8WPCLcX%3DfXNWbTuWetCnkkaWy%3D8sc11SwmpQ%40mail.gmail.com.

[Luboslav Pivarc]

Hi,

On Thu, Jul 2, 2026 at 3:36 AM Alexander Wels <aw...@redhat.com> wrote:

It's Alexander, not Alex

I apologize, Alexander. I hit reply on Alex's response and I guess it auto-filled... For my defence it was late at night after another hot day here.

 

I thought I was following the process exactly, but apparently not. I asked for this exception 8 days ago, and no one mentioned, "Hey, you are not doing this right.Please adjust it. I thought I explained that my PRs were stuck in CI congestion, and you are aware that CI (in particular the check flakes) is failing frequently on the infrastructure right now. So it took me a long time to get the critical fix merged (it is finally merged, by the way), which will allow me to actually unquarantine the tests. I also had some drive by reviews where someone asked why I was doing something, and after I explained or changed the code to address the comment, and that reviewer ghosted me. And I had to explain to the approver that the reviewer wasn't responding after I addressed their comments, asking for approval.

I appreciate you following the process. I wish somebody would raise the following once you raised the exception. According to our policy https://github.com/kubevirt/kubevirt/blob/main/docs/quarantine.md#getting-tests-out-of-quarantine, de-quarantine can take some time as we need a proof that the flake was addressed (actual bug in this case). I ran "/test pull-kubevirt-check-dequarantine-test" to speed up the process as the doc suggests. 

I believe the process and this specific requirement to not have quarantine tests is proving to be a good decision, given how much feedback it provided and continues to provide. 

 

Anyway, I understand the process is the process, and I didn't follow it correctly.

On Wed, Jul 1, 2026 at 3:38 PM 'Luboslav Pivarc' via kubevirt-dev <kubevi...@googlegroups.com> wrote:

Hi Alex,

Please write 2 separate emails next time for clearer separation and streamlined communication. Please also include all the requested points, as written in https://github.com/kubevirt/enhancements#exceptions  ref:
"""
Justification for exception
Additional time period that is required
In case of exception not being granted, what is the impact? (Think about graduation, maturity of the feature, user impact, etc.)
"""

For the VEP 24:

1. The tracking issue doesn't track changes in Beta. Please attend to it.

Added the missing links.

Thank you!
 

 

2. Unfortunately we still have tests being quarantine, therefore the exception cannot be granted as it is a requirement. Again please document the work on the issue.

Well the feature is there, the bugs are fixed, and the tests will come out of quarantine (since the fix was merged). The ONLY reason this is not beta is because of the process and the problems with CI.

The process just asks us not to have quarantine tests, it shows that the failures are usually production bugs. I think there are multiple examples in this case, if I am not mistaken.

However, we could do the following: set a deadline for when the tests need to be out of quarantine and if that deadline is met, merge the promotion. The rationale is that the period between branch cut and release is actually for fixes and testing, which is what you are doing. Sort of another exception.

I do wonder what others feel. @Jed Lejosne You have spent an enormous amount of time with this feature, how confident are you with this feature at this point?

Note: Beta now means this will be enabled by default.

-Lubo

 

 

For the VEP 192:

1. The tracking issue doesn't track changes. Please attend to it.

Added the missing links.

Thank you!
 

[Alexander Wels]

Yeah, I found some issues with the check quarantine lane. I have fixes and the last run failed on 499 out of 500 :( It seemed to find an actual edge case so I fixed that one and it is running again. I will continue working on de-quarantining those tests. Hopefully nothing else will be found.

Note that the user must perform specific actions to use decentralized live migration, it won't affect regular live migrations at all.

At this point it is what it is. I was a little frustrated working so hard to try and get this in on time, only to fail due to what seemed like procedural issues. But you are correct that there were still some actual issues that needed to be addressed. If it doesn't make it, it doesn't make it.