Bug 2016341 - Allocating VM from a Pool shows popup with UNKNOWN values
Summary: Allocating VM from a Pool shows popup with UNKNOWN values
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.8.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.5.2
: ---
Assignee: Shmuel Melamud
QA Contact: Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-21 10:34 UTC by nicolas
Modified: 2022-08-30 08:47 UTC (History)
5 users (show)

Fixed In Version: ovirt-engine-4.5.2.1
Clone Of:
Environment:
Last Closed: 2022-08-30 08:47:42 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.5?


Attachments (Terms of Use)
UNKNOWN values shown. (69.16 KB, image/png)
2021-10-21 10:34 UTC, nicolas
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 556 0 None Merged core: Add missing AttachUserToVmFromPoolAndRun job properties 2022-08-09 10:29:06 UTC
Red Hat Issue Tracker RHV-43864 0 None None None 2021-10-21 11:01:25 UTC

Description nicolas 2021-10-21 10:34:51 UTC
Created attachment 1835541 [details]
UNKNOWN values shown.

Description of problem:

When a user allocates a VM from a VmPool a popup shows "Finished Allocating VM <UNKNOWN> from VM Pool name to User <UNKNOWN>". The event is correctly logged into the Events logs, though.

Version-Release number of selected component (if applicable):

4.4.8.6

How reproducible:

Always

Steps to Reproduce:
1. Assign a non-administrative user the VmPool Permission over a pool.
2. Enter the oVirt UI with that user and acquire one machine from that pool.

Actual results:

In the Admin Panel you can see "Finished Allocating VM <UNKNOWN> from VM Pool name to User <UNKNOWN>".

Expected results:

The <UNKNOWN> fields should be replaced with real values.

Additional info:

Attaching a snapshot.

Comment 1 RHEL Program Management 2021-10-21 12:23:58 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 2 Tamir 2022-08-09 12:14:48 UTC
Verified on RHV 4.5.2-4.

Env:
    - Engine instance with RHV 4.5.2-4 (ovirt-engine-4.5.2.1-0.1.el8ev) and RHEL 8.6 installed.
    - 2 hosts with RHV 4.5.2-4 and RHEL 8.6 and with vdsm-4.50.2.2-1.el8ev.

Steps:

From WebAdmin:

1. Create a 4.7 data center and a 4.7 cluster.
2. Install the hosts and create a new NFS storage domain.
3. Create a RHEL VM pool from a template with size: 1.
4. In the same pool, Add a UserRole permission to a non-administrative user (user1).

From the VM Portal:

5. Login the VM portal with user1.
6. Allocate the VM from the VM pool to user1.

From WebAdmin:

7. In Tasks, Check that the message "Allocating VM {VM_NAME} from VM Pool {POOL_NAME} to User user1" with the VM name and the VM pool name values is displayed.
8. In Events, Check that the message "User user1 successfully attached to VM {VM_NAME} in VM Pool {POOL_NAME}" with the VM name and the VM pool name values is displayed.

Results (As Expected):
1. The 4.7 data center and the 4.7 cluster were created.
2. The hosts were installed and the NFS storage domain was created.
3. The pool and one VM were created.
4. The UserRole permission was added under the created pool to the non-administrative user (user1).
5. user1 is logged in the VM portal.
6. The VM from the created VM pool was allocated to user1.
7. The message "Allocating VM {VM_NAME} from VM Pool {POOL_NAME} to User user1" with the VM name and the VM pool name values is displayed.
8. The message "User user1 successfully attached to VM {VM_NAME} in VM Pool {POOL_NAME}" with the VM name and the VM pool name values is displayed

Comment 3 Sandro Bonazzola 2022-08-30 08:47:42 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.