Actions
Bug #23196
closedDefault values of cores sockets in new VM should be 1
Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - oVirt
Target version:
Difficulty:
Triaged:
No
Description
When creating VM, it is not possible to create vm without cores and sockets,
The correct behavior should be that the cores and sockets default values should be 1.
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5427 added
Updated by Shira Maximov over 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset c0e00d6c1f01aa28f0317344be5514467b1edc64.
Updated by The Foreman Bot over 6 years ago
- Pull request https://github.com/theforeman/foreman/pull/5457 added
Updated by Tomer Brisker about 6 years ago
- Translation missing: en.field_release set to 353
- Triaged set to No
Updated by Ivan Necas about 6 years ago
- Has duplicate Bug #24219: The empty field for sockets (which is the default) causes ovirt provisioning to fail added
Updated by Ivan Necas about 6 years ago
- Target version changed from 1.19.0 to 1.18.1
Proposing for 1.18.1, as it's a regression in terms of requiring the user to perform some additional clicks before she can provision properly.
Updated by Tomer Brisker about 6 years ago
- Target version changed from 1.18.1 to 1.19.0
- Fixed in Releases 1.19.0, 1.20.0 added
Updated by Tomer Brisker about 6 years ago
- Category set to Compute resources - oVirt
Actions