Bug #8097
Invalid maximum core counts are listed
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Pull request:
Description
On a single core VM, I see the cores dropdown list 1-8 as valid options, but none of those above 1 are valid (subject to #8096). The form does appear to query for the max_cpu_count, but I guess that's either inaccurate at some lower layer, or it doesn't correspond to cpuset configuration.
Associated revisions
History
#1
Updated by The Foreman Bot over 8 years ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-docker/pull/38 added
- Pull request deleted (
)
#2
Updated by Daniel Lobato Garcia over 8 years ago
Updated by - Status changed from Ready For Testing to Closed
Fixes #8096 #8097: Improve cpuset cpushare form