Project

General

Profile

Actions
Copy link

Bug #24219

closed

The empty field for sockets (which is the default) causes ovirt provisioning to fail

Added by Ivan Necas about 6 years ago. Updated about 6 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

1. go to host create form
2. try to provision on ovirt, without using any template (leaving the Virutal Machine tab untouched: notice the sockets field being empty)
3. result Failed to create a compute oVirt (oVirt) instance nell-diller.inecas.ovirt.test: Fault reason is "Operation Failed". Fault detail is "[Minimum number of sockets cannot be less then 1]". HTTP response code is 409.

Expected:

It should behave as before #22117

Related issues 2 (0 open — 2 closed)

Related to Foreman - Bug #22117: Add support for specifying number for sockets for oVirtClosedShira MaximovActions
Is duplicate of Foreman - Bug #23196: Default values of cores sockets in new VM should be 1 ClosedShira MaximovActions
Actions
Copy link
 #1

Updated by Ivan Necas about 6 years ago

  • Related to Bug #22117: Add support for specifying number for sockets for oVirt added
Actions
Copy link
 #2

Updated by Ivan Necas about 6 years ago

  • Status changed from New to Duplicate
Actions
Copy link
 #3

Updated by Ivan Necas about 6 years ago

  • Is duplicate of Bug #23196: Default values of cores sockets in new VM should be 1 added
Actions
Copy link

Also available in: Atom PDF