oVirt Discovery: Red Hat Virtualization (RHV) Servers are missing 'Is virtual' flag, Runs on/Hosted on relationship, and Virtualization metadata - Known Error

oVirt Discovery: Red Hat Virtualization (RHV) Servers are missing 'Is virtual' flag, Runs on/Hosted on relationship, and Virtualization metadata Description Windows Servers discovered through oVirt / Red Hat Virtualization (RHV) are not correctly set as Virtual:

The 'Is virtual' field on the Windows Server CI is false/unticked. There is no Runs on / Hosted on relationship between the Windows Server CI and the RHV Virtual Machine CI Virtualization metadata is missing which would normally be expected to be populated by Cloud Provider patterns (e.g. AWS, Azure, OCI, GCP) and Hypervisors (e.g. VMware, Hyper‑V) Steps to Reproduce

Install 'Discovery and Service Mapping Patterns' v1.29.0 (this will also be seen in 1.30.0) Run oVirt Discovery Actual behaviour:

Observe no virtualisation relationship is created by the 'Get Object Id For oVirt Windows Server' Pattern. The Virtual Computer Check businss rule, which is relied on to do this for other patterns, also never runs, because 'Is virtual' is set as false.

Expected behaviour:

The 'Is virtual' field on the Windows Server CI should be true/ticked. A Runs on / Hosted on relationship between the Windows Server CI and the RHV Virtual Machine CI should be created. Virtualization metadata is added. Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.

The workaround adds a new Pattern extension to the existing Windows OS - Servers pattern:

Get Object Id For oVirt Windows Server /sa_pattern.do?sys_id=e85ca561c397f21413debdac050131cf /sa_pattern_extension_8e150f1a1b509194fe29a717ec4bcba0

This is inlcuded in the attached update set: PRB1998928sys_remote_update_set_ae44b5edc397f21413debdac050131d0.xml

Warning: it is possible that the final fix will have different records and sys_ids, potentially causing conflicts or duplicates. To avoid problems, back out the update set before upgrading to the fixed Discovery and Service Mapping Patterns app version (planned for June 2026 - check the Fixed In section to confirm).