Actions
Bug #14038
closed
Selecting multiple cores per socket not working against vmware provider (image cloning)
Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1314352
Description of problem:
Selecting multiple cores per socket not working against vmware provider (image cloning)
Version-Release number of selected component (if applicable):
sat6.1.7
How reproducible:
always
Steps to Reproduce:
1. Defaine new VNware ESX host from the image.
2. Assign different to default=1 value to Cores per Socket.
3. Create a host
Actual results:
Deployed machine shows "Cores per socket" = 1
Expected results:
Deployed machine shows "Cores per socket" given value as well as machine resizes on several sockets in Vmware cluster
Additional info:
Updated by Ivan Necas almost 9 years ago
- Category changed from Compute resources to Compute resources - VMware
Updated by The Foreman Bot almost 9 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ivan Necas
- Pull request https://github.com/theforeman/foreman/pull/3274 added
Updated by Anonymous almost 9 years ago
- Related to Bug #10873: "cores per socket" field should be disabled for Virtual H/W Version 10 when creating VMware VM added
Updated by Ivan Necas almost 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 17c277d5733cf4b814f3d5b357269f38bafcfa8f.
Updated by Dominic Cleal almost 9 years ago
- Translation missing: en.field_release set to 141
Actions