Project

General

Profile

Actions

Bug #14038

closed

Selecting multiple cores per socket not working against vmware provider (image cloning)

Added by Ivan Necas about 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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:


Related issues 1 (1 open0 closed)

Related to Foreman - Bug #10873: "cores per socket" field should be disabled for Virtual H/W Version 10 when creating VMware VMNewTimo Goebel06/18/2015Actions
Actions #1

Updated by Ivan Necas about 8 years ago

  • Category changed from Compute resources to Compute resources - VMware
Actions #2

Updated by The Foreman Bot about 8 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
Actions #3

Updated by Anonymous about 8 years ago

  • Related to Bug #10873: "cores per socket" field should be disabled for Virtual H/W Version 10 when creating VMware VM added
Actions #4

Updated by Ivan Necas almost 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #5

Updated by Dominic Cleal almost 8 years ago

  • translation missing: en.field_release set to 141
Actions

Also available in: Atom PDF