Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionVladimír Sedmík
2019-08-07 09:17:21 UTC
Description of problem:
When creating a host on Satellite using API the host is created successfully, but always with one CPU only, regardless the core request specified in JSON.
Version-Release number of selected component (if applicable):
Satellite 6.6.0 snap 14:
satellite-6.6.0-5.beta
tfm-rubygem-foreman_kubevirt-0.1.4-1
tfm-rubygem-fog-kubevirt-1.3.1-1
How reproducible:
always
Steps to Reproduce:
1. Specify a JSON request file like the following one, update with appropriate org, loc and other ids, choose "cores" count > 1:
vim req.json
{ "location_id" : "2",
"organization_id" : "1",
"host" : {
"name" : "test-api-4c",
"location_id" : "2",
"organization_id" : "1",
"compute_resource_id" : "1",
"provision_method" : "build",
"compute_attributes" : {
"cores" : "4",
"memory": "1073741824",
"volumes_attributes": {
"0": { "storage_class": "gluster-default-volume", "capacity": "2" }
}
},
"operatingsystem_id": "1",
"architecture_id" : "1",
"interfaces_attributes": {
"0" : {
"domain_id" : "1",
"name" : "test-api-4c",
"ip": "172.16.0.108",
"subnet_id" : "1",
"mac" : "00:03:14:15:92:04",
"managed" : "1",
"primary" : "1",
"provision" : "1",
"type": "Nic::Managed",
"virtual" : "0",
"compute_attributes" : {
"cni_provider" : "pod",
"network" : "ovs-net-1"
}
}
}
}
}
2. curl -u admin:password -H "Content-Type: application/json" -X POST -d @req.json --insecure https://<sat_fqdn>/api/hosts
3. Check the newly created host at the Satellite and OCP side.
Actual results:
The cores count is 1 regardless the value specified in JSON.
Expected results:
Cores count matching the value given in req.json file.
Additional info:
It is possible to create a host with more CPUs via UI successfully.
Tested against OCP v3.
Changing this into documentation BZ, the correct way to send the cores in 'cpu_cores'
I will change the documentation for this in hammer_cli_foreman_kubevirt and in foreman_kubevirt repositories.
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/RHSA-2020:1454
Description of problem: When creating a host on Satellite using API the host is created successfully, but always with one CPU only, regardless the core request specified in JSON. Version-Release number of selected component (if applicable): Satellite 6.6.0 snap 14: satellite-6.6.0-5.beta tfm-rubygem-foreman_kubevirt-0.1.4-1 tfm-rubygem-fog-kubevirt-1.3.1-1 How reproducible: always Steps to Reproduce: 1. Specify a JSON request file like the following one, update with appropriate org, loc and other ids, choose "cores" count > 1: vim req.json { "location_id" : "2", "organization_id" : "1", "host" : { "name" : "test-api-4c", "location_id" : "2", "organization_id" : "1", "compute_resource_id" : "1", "provision_method" : "build", "compute_attributes" : { "cores" : "4", "memory": "1073741824", "volumes_attributes": { "0": { "storage_class": "gluster-default-volume", "capacity": "2" } } }, "operatingsystem_id": "1", "architecture_id" : "1", "interfaces_attributes": { "0" : { "domain_id" : "1", "name" : "test-api-4c", "ip": "172.16.0.108", "subnet_id" : "1", "mac" : "00:03:14:15:92:04", "managed" : "1", "primary" : "1", "provision" : "1", "type": "Nic::Managed", "virtual" : "0", "compute_attributes" : { "cni_provider" : "pod", "network" : "ovs-net-1" } } } } } 2. curl -u admin:password -H "Content-Type: application/json" -X POST -d @req.json --insecure https://<sat_fqdn>/api/hosts 3. Check the newly created host at the Satellite and OCP side. Actual results: The cores count is 1 regardless the value specified in JSON. Expected results: Cores count matching the value given in req.json file. Additional info: It is possible to create a host with more CPUs via UI successfully. Tested against OCP v3.