Bug 1196326 - VMware VM & Template refresh doesn't properly set cores and sockets
Summary: VMware VM & Template refresh doesn't properly set cores and sockets
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Insight
Version: 5.3.0
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.3.4
Assignee: Brandon Dunne
QA Contact: Ramesh A
URL:
Whiteboard:
Depends On: 1184990
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-25 17:16 UTC by Brandon Dunne
Modified: 2019-02-15 14:04 UTC (History)
9 users (show)

Fixed In Version: 5.3.4.1
Doc Type: Bug Fix
Doc Text:
In the previous version of CloudForms Management Engine, provisioning a virtual machine from a VMWare template resulted in the wrong number of CPU sockets and cores being assigned to the virtual machine. This was because the VMWare provisioning work flow did not gather this information from the template due to a performance issue resulting from this process. This bug was fixed by gathering the CPU socket and core information in a manner that did not result in a performance impact. The correct CPU socket and core information should now be available when provisioning from a VMWare template in the new version of CloudForms Management Engine.
Clone Of: 1184990
Environment:
Last Closed: 2015-04-29 13:19:55 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0890 0 normal SHIPPED_LIVE cfme (5.3.4) bug fix and enhancement update 2015-04-29 17:18:32 UTC

Comment 2 Ramesh A 2015-04-22 12:22:31 UTC 
Good to go.  Verified and working fine in 5.3.4.2.20150415125246_f5d5c91
Comment 4 errata-xmlrpc 2015-04-29 13:19:55 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://rhn.redhat.com/errata/RHBA-2015-0890.html
Note You need to log in before you can comment on or make changes to this bug.