Bug 1326817
| Summary: | Impossible to edit HE VM CPU number because it show only number of sockets that you defined at deploy time | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Artyom <alukiano> | ||||
| Component: | BLL.HostedEngine | Assignee: | Roy Golan <rgolan> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | meital avital <mavital> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.6.5 | CC: | alukiano, bugs | ||||
| Target Milestone: | --- | Flags: | rule-engine:
planning_ack?
rule-engine: devel_ack? rule-engine: testing_ack? |
||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-04-13 16:02:21 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1304387 | ||||||
| Attachments: |
|
||||||
Uh, but it behaves like this for me with normal VMs also. You first edit the total number of vCPUs and only after that you can select the topology iirc. Did you try using REST btw? It is my mistake host only has 2 CPU's, I checked it on the host with 4 CPU's and it worked fine. |
Created attachment 1146848 [details] screenshot Description of problem: Impossible to edit HE VM CPU number because it shows only number of sockets that you defined at deploy time Version-Release number of selected component (if applicable): rhevm-3.6.5.3-0.1.el6.noarch How reproducible: Always Steps to Reproduce: 1. Deploy HE and add storage domain to engine to auto-import it 2. Open HE VM update window via webadmin and change number of CPU's 3. Actual results: The engine does not give to change number of CPU's because HE VM list of sockets that engine show equal to one that you define at deploy time(see screenshot) Expected results: The engine must show list of sockets that include greater values, like for regular VM(1..12) Additional info: