Bug 1458754 - [RFE] It is not possible to add sockets to RHEV host via Satellite
Summary: [RFE] It is not possible to add sockets to RHEV host via Satellite
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Compute Resources - RHEV
Version: 6.2.9
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: 6.4.0
Assignee: Shira Maximov
QA Contact: Lukáš Hellebrandt
Depends On:
Blocks: 1505576 1589779
TreeView+ depends on / blocked
Reported: 2017-06-05 11:53 UTC by Konstantin Trufanov
Modified: 2019-11-05 23:05 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-10-16 15:27:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Foreman Issue Tracker 22117 Normal Closed Add support for specifying number for sockets for oVirt 2020-03-26 05:15:00 UTC
Red Hat Product Errata RHSA-2018:2927 None None None 2018-10-16 15:28:58 UTC

Description Konstantin Trufanov 2017-06-05 11:53:10 UTC
Description of problem:

When creating or modifying the hosts within RHEV it throw the following error:


  2017-06-02 10:44:39,413+02 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-8) [] 
Operation Failed: [Cannot add VM. Maximum number of cpu per socket exceeded]


  2017-06-02 10:44:39 b86ea2db [app] [I] Failed to save: Failed to create a compute sbr-virt-rhv-nested (RHEV) instance ktruf-maxcpu.sysmgmt.lan: Cannot add VM. Maximum number of cpu per socket exceeded


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

6.2.9 Satellite

RHEV 3.6, 4.0, 4.1

How reproducible:

All the time

Steps to Reproduce:
1. Create hosts within Satellite WebUI at RHEV with more then 16 CPUs
2. Get error

Actual results:

VM is not created 

Expected results:

Vm is created successfully as per RHEV documentation with up to 240 cores for RHEV 3.6 and 4.0 and 288 for RHEV 4.1 

Additional info:

The limits for RHEV is the following:

MaxSocket  = 16
MaxNumOfCpuPerSocket  = 16
MaxNumOfThreadsPerCpu = 8

Despite the fact that number of cores are limited to 16 it is possible to split it over the virtual sockets so it would have number_of_sockers*number_of_cpus cores.

The correct parameters could be passed to RHEV via API.


          <topology cores="2" sockets="9"/>

In this example number or cores would be 18.

Comment 3 Ivan Necas 2017-06-07 11:40:04 UTC
Connecting redmine issue http://projects.theforeman.org/issues/10395 from this bug

Comment 4 Lukáš Hellebrandt 2017-10-03 10:35:10 UTC

1) Create a RHEV computing resource (infrastructure -> computing resources)
2) Create a new host from WebUI (hosts -> new host), using that computing resource in the "Deploy on" field

Result: "Failed to create a compute RHEV test (RHEV) instance testrhevhost.testdomain: Cannot add VM. Max number of cpu per socket exceeded"

Comment 6 Lukáš Hellebrandt 2017-10-04 12:04:09 UTC
FailedQA with Sat6.3 snap 18 and both RHEV 3.5.7-0.1 and RHEV

When trying to create a host with 24 CPUs, the following error occurs and the host isn't created:
"Unable to save
Failed to create a compute RHEV test (RHEV) instance testhost.testdomain: Cannot add VM. Max number of cpu per socket exceeded"

Creating the host manually in RHEV works so this shouldn't be caused by some limit set on that RHEV instance. There is one host with 2 sockets, 6 cores per socket and 2 threads per core, which is enough for a 6:2:2 config; but even if it wasn't, it should be at least possible to create a host and not run it.

Note: When creating a guest in RHEV manually, it is not enough to set 24 cores: one must specifically set the setup of 6:2:2. This might be where things go wrong.

Comment 7 Michal Skrivanek 2017-10-24 06:09:29 UTC
Current supported topology maximum is 16 sockets, 16 cores/socket

Comment 9 Craig Donnelly 2017-12-12 20:46:04 UTC

When you tested this, did you use the same user for RHV for the compute resource login as you did to login to the RHV WebUI and create the custom host?

Comment 10 Lukáš Hellebrandt 2018-01-02 09:56:11 UTC

Comment 11 Ivan Necas 2018-01-02 17:40:38 UTC
Created redmine issue http://projects.theforeman.org/issues/22117 from this bug

Comment 12 orabin 2018-01-03 09:13:58 UTC
Choosing the number of cores was fixed by http://projects.theforeman.org/issues/10395 but Satellite does not have an option to choose number of sockets.
I'm changing this to a RFE to add the number of sockets.

Comment 14 Bryan Kearney 2018-01-08 14:54:47 UTC
I cleaned up the sat-6.3.0? flag. It was set to backlog on 3 January.

Comment 17 pm-sat@redhat.com 2018-06-25 14:21:41 UTC
Upstream bug assigned to oprazak@redhat.com

Comment 18 Tomer Brisker 2018-09-06 07:33:28 UTC
This was already in foreman 1.18.0, looks like automation missed it somehow. Moving to ONQA

Comment 19 Lukáš Hellebrandt 2018-09-10 13:02:38 UTC
Verified with Sat 6.4 snap 20.

Used reproducer from comment 4 with 8 cores and 3 sockets. Tested with both APIv3 and APIv4. The VM got created with 24 cores as 3:8:1.

I think "Cores" should actually be worded as "Cores per socket". I will verify this BZ as it's much better now than it was and create a different BZ about this nitpick issue.

Comment 21 errata-xmlrpc 2018-10-16 15:27:35 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.


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