Bug 1710245 - Hosted-Engine deployment via Cockpit uses 4vCPU w/ 16348 GB instead of 16384
Summary: Hosted-Engine deployment via Cockpit uses 4vCPU w/ 16348 GB instead of 16384
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: cockpit-ovirt
Version: 4.3.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.3.4
: 4.3.1
Assignee: Ido Rosenzwig
QA Contact: Wei Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-15 07:43 UTC by Ido Rosenzwig
Modified: 2019-06-20 14:48 UTC (History)
13 users (show)

Fixed In Version: cockpit-ovirt-0.13.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-20 14:47:59 UTC
oVirt Team: Integration
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1560 0 None None None 2019-06-20 14:48:02 UTC
oVirt gerrit 100023 0 'None' 'MERGED' 'Change recommended memory size to 16384 instead of 16348' 2019-12-09 04:38:03 UTC
oVirt gerrit 100025 0 'None' 'MERGED' 'Change recommended memory size to 16384 instead of 16348' 2019-12-09 04:38:03 UTC

Description Ido Rosenzwig 2019-05-15 07:43:24 UTC 
Description of problem:
Hosted-Engine deployment via Cockpit uses 4vCPU w/ 16348 MB instead of 16384 
( 1024*16=16384 )


How reproducible:
100*

Steps to Reproduce:
1. Deploy hosted-engine with more than 16GB memory via cockpit
2. See that the recommended memory is 16348 instead of 16384
3.
Comment 2 Wei Wang 2019-05-29 09:27:54 UTC 
Test Version:
RHVH-4.3-20190523.0-RHVH-x86_64-dvd1.iso
cockpit-ovirt-dashboard-0.13.0-1.el7ev.noarch

Test Steps:
According to comment 0

Result:
The recommended memory is 16384

Move the bug status to "VERIFIED"
Comment 4 errata-xmlrpc 2019-06-20 14:47:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:1560
Note You need to log in before you can comment on or make changes to this bug.