Bug 1254910
| Summary: | Numa nodes list of VM should be changed only when Vm status is down | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Tomer Saban <tsaban> |
| Component: | General | Assignee: | bugs <bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | Artyom <alukiano> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | --- | CC: | amureini, bugs, dfediuck, istein, lsurette, mavital, mgoldboi, msivak, rbalakri, rgolan, srevivo, ykaul |
| Target Milestone: | --- | Flags: | sbonazzo:
ovirt-4.2-
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-26 09:04:04 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: | |||
|
Description
Tomer Saban
2015-08-19 08:48:46 UTC
Please put a reproducer here. note: this means that numa nodes list should be exported to ovf as well. I think its relatively small but important fix that will allow to have numa info on export/import. Doron? Description of problem: oVirt allows changing pinning of numa nodes even when VM is in status up which is illegal because this changes should only occur when VM is down. How reproducible: 100% Steps to Reproduce: 1.Create new VM and run it. 2.On subtab Host->Start Running On: change to specific host with numa support. 3.Migration Options: choose "Do not allow migration" 4.Click Numa Pinning and change something in the numa pinning. Actual results: Numa pinning has changed even though the VM is running. Expected results: Message should popup saying that the changes will take place only on next reboot. (In reply to Roy Golan from comment #1) > Please put a reproducer here. > > note: this means that numa nodes list should be exported to ovf as well. > > I think its relatively small but important fix that will allow to have numa > info on export/import. Doron? Roy, how will it influence hosted engine upgrade? ie- We should prefer 3.6 stabilization now ad this seems to be a non-trivial change. 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 reply to Doron Fediuck from comment #3) > (In reply to Roy Golan from comment #1) > > Please put a reproducer here. > > > > note: this means that numa nodes list should be exported to ovf as well. > > > > I think its relatively small but important fix that will allow to have numa > > info on export/import. Doron? > > Roy, how will it influence hosted engine upgrade? > ie- We should prefer 3.6 stabilization now ad this seems to be a non-trivial > change. No direct influence on HE as it doesn't support numa config atm. This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA. Patch is in Abandoned state - moving back to ASSIGNED. oVirt 4.0 beta has been released, moving to RC milestone. Nobody is working on this atm. Moving to the next release. (In reply to Martin Sivák from comment #12) > Nobody is working on this atm. Moving to the next release. The next release is 4.1. But realistically, this should go to 4.2 or closed. You are right, it might be better to mark it for reevaluation then. We will decide on this bug's faith with Moran. We won't be perusing this issue any more. If someone needs it, patches are welcomed. |