Bug 1275060
| Summary: | [TEXT] Improve error message when adding a numa node to a vm pinned to multiple hosts | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Artyom <alukiano> | ||||
| Component: | Backend.Core | Assignee: | Tomer Saban <tsaban> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | meital avital <mavital> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.6.0.2 | CC: | alukiano, bugs, dfediuck, rgolan | ||||
| Target Milestone: | --- | ||||||
| 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-06 11:31:35 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: | |||||||
| Attachments: |
|
||||||
Artyom, numa stuff is under sla. Please set both the component as well. I set whiteboard sla and I do not see bll.sla under component. (In reply to Artyom from comment #2) > I set whiteboard sla and I do not see bll.sla under component. You're right. Doron? SLA is not component specific, and it runs across the stack. BZ reassigned. Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone. I think we should allow numa pinning with more than one host cause technically we don't have a problem migrating it. Doron? (In reply to Roy Golan from comment #7) > I think we should allow numa pinning with more than one host cause > technically > we don't have a problem migrating it. > > Doron? We may consider it in 4.0 (updated targets). Closing old issues based on capacity. Please re-open only if relevant and needed. |
Created attachment 1086216 [details] engine log Description of problem: If I try to add numa node to vm that pinned to multiple hosts, action failed with error message "Update VM NUMA node failed.", I believe this message do not describe why update failed. Version-Release number of selected component (if applicable): rhevm-3.6.0.2-0.1.el6.noarch How reproducible: Always Steps to Reproduce: 1. Pin vm to multiple hosts 2. Add numa node to vm 3. Actual results: Action failed with error message "Update VM NUMA node failed." Expected results: Action failed with more informative error or we need just fade numa node window in case if vm pinned to multiple hosts(the same as we doing if vm not pinned to hosts) Additional info: