Created attachment 1812455 [details] AffinityOperationCanceled.png Description of problem: While adding a new affinity group conflicting with another existing group the user gets an error window talking about VM Ids which looks hard readable. It would be more user-friendly to have VM names in this window. Version-Release number of selected component (if applicable): How reproducible:100% Steps to Reproduce: 1. Create affinity group A with VM1 and VM2 positive VM Affinity Rule. 2. Create affinity group B with VM1 and VM2 negative VM Affinity Rule. Actual results: Error while executing action: Affinity Group collision detected in unified affinity group of VMs: e8b47916-4cb9-41f6-b114-00dc3e2d05b8,6d5009b3-e731-42b4-a6ad-8927a6d61238 and negative affinity group: B with VMs: e8b47916-4cb9-41f6-b114-00dc3e2d05b8,6d5009b3-e731-42b4-a6ad-8927a6d61238 Expected results: VM names instead of IDs in the Error message Additional info:
trivial? please fix or close if no capacity
the bug is on_qa , but still happens on the last available build . tested on ovirt-engine-4.5.2-0.3.el8ev.noarch
Tested on Software Version:4.5.0.7-0.9.el8ev and successfully reproduced with attached print screen. Will wait to resolve the engine upgrade issue of "nothing provides sos >= 4.2-20 needed by ovirt-log-collector-4.4.7-2.el8ev.noarch" to be able to upgrade the engine to latest ovirt-engine-setup-4.5.2.2-0.1.el8ev.noarch.
Created attachment 1905022 [details] Screen shot of reproduced issue from 11.08.22.
Works fine on: ovirt-engine-setup-4.5.2.2-0.1.el8ev.noarch ovirt-hosted-engine-ha-2.5.0-1.el8ev.noarch ovirt-hosted-engine-setup-2.6.5-1.1.el8ev.noarch Linux 4.18.0-372.19.1.el8_6.x86_64 #1 SMP Mon Jul 18 11:14:02 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux Screenshot have been attached.
Created attachment 1905545 [details] Screenshot of properly working names for VMs and also for hosts.
Created attachment 1905546 [details] Only VMs without hosts conflicting affinity group fixed names
This bugzilla is included in oVirt 4.5.2 release, published on August 10th 2022. Since the problem described in this bug report should be resolved in oVirt 4.5.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.