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.
Bug 1364606 - Unable to select more than 8 CPU in VMware for Provisioning
Summary: Unable to select more than 8 CPU in VMware for Provisioning
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources
Version: 6.2.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Amir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-05 22:36 UTC by anerurka
Modified: 2020-08-13 08:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:51:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Verified screenshot (16.78 KB, image/png)
2017-08-23 12:29 UTC, Amir
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 5901 0 None None None 2016-08-09 17:22:57 UTC

Description anerurka 2016-08-05 22:36:13 UTC
Description of problem:

Unable to select more than 8 CPU in VMware for Provisioning 

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

V.6.2

How reproducible:

Steps to Reproduce:

1. Login to Satellite Server

- Infracture --> Compute Profile --> Select Compute Profiles --> Click VM Ware

- Maximum number of CPU is 8

Actual results:

Maximum number of CPU is 8

Expected results:

Can not select more than 8 CPU

Additional info:

Similar Bug in upstream --> http://projects.theforeman.org/issues/5901

Comment 1 Bryan Kearney 2016-08-09 18:16:56 UTC
Upstream bug component is Compute Resources

Comment 3 Bryan Kearney 2016-08-25 10:17:59 UTC
Upstream bug assigned to oprazak

Comment 4 Bryan Kearney 2016-08-25 10:18:02 UTC
Upstream bug assigned to oprazak

Comment 5 Bryan Kearney 2016-09-19 14:18:20 UTC
Upstream bug assigned to mhulan

Comment 6 Bryan Kearney 2016-09-19 14:18:24 UTC
Upstream bug assigned to mhulan

Comment 7 Bryan Kearney 2016-09-22 10:18:54 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/5901 has been resolved.

Comment 9 Amir 2017-08-23 12:29:52 UTC
Created attachment 1317073 [details]
Verified screenshot

Verified.
Version Tested: Satellite-6.3 Snap 12
I performed the following steps to verify this issue:
  1. Created a valid vmware compute resource
  2. Infrastructure -> compute profile -> edit vmware
  3. Changing number of cpu above 8              
   
 Verified that changing number of cpu to above 8 has succeeded

Comment 10 Satellite Program 2018-02-21 16:51:07 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/RHSA-2018:0336


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