IT SBIT Services
Schneeberger
DEEN
Known update issues

Veeam KubeVirt Proxy 1.0.3: fixes leaked data mover pods, slow snapshot detection, missing VM settings

FixedKnown issue

← All entries

Summary

Veeam KubeVirt Proxy (KVP) 1.0.3, released on 2026-10-27, resolves three issues: leaked backup data mover pods that block new backups, slow detection of snapshot status changes, and VirtualMachine settings missing from backups. The Veeam Plug-In for KubeVirt (also known as Veeam Plug-In for Red Hat OpenShift Virtualization) uses this proxy. The release also updates the ubi10/ubi-minimal package to address CVE-2026-114406 and CVE-2026-77214.

Symptoms

  • When backup finalization takes longer than five minutes, the backup data mover pods are not removed. The leaked pods keep their CPU requests, so new data mover pods stay in the Pending state and new backups cannot start.
  • The data mover proxy process takes too long to detect changes in snapshot status, which increases the risk that the freeze fails.
  • VirtualMachine settings introduced in KubeVirt 1.5 and later are not included in backups and are missing after restore.

Affected

  • Veeam KubeVirt Proxy versions earlier than 1.0.3
  • Veeam Plug-In for KubeVirt (Veeam Plug-In for Red Hat OpenShift Virtualization)
  • Restore points created with earlier KVP versions still lack the VirtualMachine settings from KubeVirt 1.5 and later

Workaround

No workaround known.

Fix

Fixed in Veeam KubeVirt Proxy 1.0.3 (2026-10-27). The fix is not retroactive: restore points captured with earlier versions still lack the missing VirtualMachine settings.

Recommendation

Upgrade Veeam KubeVirt Proxy to 1.0.3 following the upgrade instructions in KB4880. Check for pods stuck in Pending state caused by leaked data mover pods. Create new restore points after the upgrade, as older ones remain incomplete for VirtualMachine settings from KubeVirt 1.5 and later.

Sources

Compiled from the sources listed and translated with AI (Claude); status and dates come from the vendor. The vendor’s statements are authoritative. Updated 1 Nov 2026, 15:36.

Where the information comes from

We continuously read the vendors’ official sources, community reports and trade media and summarise them in our own words, with a link to the source:

  • Microsoft: Windows release health (Windows 10/11, Server 2016 to 2025), Windows message center, known issues of Microsoft 365 Apps (Outlook, Excel, Word, PowerPoint), Edge, Intune, Autopilot, Windows 365 and Entra Connect, Microsoft KB articles with timelines, Exchange and Windows IT Pro blogs, optionally Microsoft 365 service health and message center
  • other vendors: Veeam KB, Citrix (known issues), Ubuntu and Debian (regressions), Broadcom (VMware), Fortinet, Cisco, Mozilla, Let’s Encrypt
  • community (title, short excerpt and link only, without the names of the authors): Microsoft Q&A, Microsoft Tech Community (discussions), Veeam R&D Forums, Eleven Forum
  • targeted web research with AI (Claude), e.g. on the updates of the month – this also finds discussions on Reddit and in forums; such entries are labelled as community reports until the vendor confirms them
  • early warning from trade media (title and link only): Born’s Tech and Windows World, BleepingComputer, AskWoody, Windows Latest, Windows Central, gHacks, The Windows Club, Deskmodder, Dr. Windows, WindowsArea, Frankys Web, heise online

Summary and translation with AI (Claude by Anthropic) – without any data of visitors.

Affected? We can help.

We check whether your systems are affected, apply workarounds properly and plan for dated changes in good time.

Get in touchRSS feed