do the regressions on 1.36 justify postponing the beta.0 for tomorrow?

7 views
Skip to first unread message

Daniel Hiller

unread,
May 20, 2026, 10:34:24 AMMay 20
to kubevirt-dev
Hey all,

as was just discussed in today's community meeting we are approaching the 1.36 lanes switch to required date tomorrow.

Since we might need to quarantine some tests for that (see [1]) should we postpone the date for beta.0 by one week or pull through with this?

--

Kind regards,


Daniel Hiller

He / Him / His

Principal Software Engineer, KubeVirt CI, OpenShift Virtualization

Red Hat

dhi...@redhat.com   

Red Hat GmbH, Registered seat: Werner von Siemens Ring 12, D-85630 Grasbrunn, Germany  
Commercial register: Amtsgericht Muenchen/Munich, HRB 153243,
Managing Directors: Ryan Barnhart, Charles Cachera, Avril Crosse O'Flaherty  

Alex Kalenyuk

unread,
May 20, 2026, 10:44:23 AMMay 20
to Daniel Hiller, kubevirt-dev
Hey Daniel, from the sig-storage perspective, I don't think we should. The race is isolated to live migration with hotplug volumes,
which, for a beta.0, I think is acceptable. We will likely have this fixed in the next milestone (PR ready).

I'll let others chime in about the other bug but I think we could use similar reasoning there too.

--
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/CAK%2BeyL45WHf3pL%3D7ODpBA2L3VgxOZi3eVv33Pv4Gyijx%3DFuX3w%40mail.gmail.com.

Luboslav Pivarc

unread,
May 21, 2026, 4:07:12 AMMay 21
to Alex Kalenyuk, Daniel Hiller, kubevirt-dev
Hi Daniel,

I think a blocking tracker is sufficient for these issues. 

-Lubo

Reply all
Reply to author
Forward
0 new messages