This message was deleted.

I'm a dummy. I should have checked GitHub.

I don't think this has been discussed broadly, but, yeah, v1.7.2 will pick up recent fixes for copyfail etc. via updates to SL Micro, but we got held up slightly with the release due to a pending kubevirt update IIRC @salmon-city-57654

yeah, as @ambitious-daybreak-95996 mentioned, we will include fixes for copyfail, etc but currently we are working on the Kubevirt issue. Once the work is done, we will try to move v1.7.2 forward.

We have our end of term maintenance window coming up in two weeks and I was just trying to figure out what'd be needed for planning. Sounds like we'll pick up the update in the next window. Thanks!

Do you have the link for the kubevirt issue we can follow along with? We're waiting for the nic bonding fixes before before we go to 1.7.x

[backport v1.7] [BUG] pcidevice passthorugh is broken on VM with hot plugged volume this is what we are working on. For the nic bonding issue, I thought you mentioned [BUG] NIC persistent naming workaround fails in bonded environments, right? If so, this is already included in the v1.7 branch (which means it will ship with v1.7.2)