Bug 1135976
| Summary: | Edit pinned vm placement option clear vm cpu pinning options without any error message | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Artyom <alukiano> | ||||
| Component: | Frontend.WebAdmin | Assignee: | Andrej Krejcir <akrejcir> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Artyom <alukiano> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | --- | CC: | bugs, dfediuck, gklein, mavital, melewis, mgoldboi, rbalakri, sbonazzo, srevivo, ykaul | ||||
| Target Milestone: | ovirt-4.1.0-alpha | Keywords: | Triaged | ||||
| Target Release: | 4.1.0.2 | Flags: | rule-engine:
ovirt-4.1+
rule-engine: planning_ack+ rgolan: devel_ack+ mavital: testing_ack+ |
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: |
Previously, CPU pinning information could be silently lost. Now, a pop-up warning that CPU pinning information will be lost displays when a user saves a virtual machine. This means that the user is aware the CPU pinning information will be lost and has the choice to cancel the operation.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-02-01 14:37:45 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: | 1419434 | ||||||
| Attachments: |
|
||||||
oVirt 3.5.1 has been released, re-targeting to 3.5.2 as marked as urgent / high severity Re-targeting to 3.5.3 since this bug has not been marked as blocker for 3.5.2 and we have already released 3.5.2 Release Candidate. Too risky for 3.5.Z - re-targeting for 3.6 Einav - do you have an RFE on marking changes in other side tabs visible to the user? (In reply to Roy Golan from comment #3) > Too risky for 3.5.Z - re-targeting for 3.6 > > Einav - do you have an RFE on marking changes in other side tabs visible to > the user? no - feel free to open one. thanks. 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. this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high oVirt 3.6.0 has been released on November 4th, re-targeting to 3.6.1 since this bug has been marked as high severity ovirt 3.6.1 is GA. moving all open bugs to 3.6.2 ovirt 3.6.1 was GA'd, all open bugs should move to 3.6.2. The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified. Verified ovirt-engine-4.1.0-0.2.master.20161212172238.gitea103bd.el7.centos.noarch Error message golden_env_mixed_virtio_0: ACTION_TYPE_FAILED_VM_CANNOT_BE_PINNED_TO_CPU_WITH_UNDEFINED_HOST |
Created attachment 933317 [details] screenshots Description of problem: If I have pinned vm(pinned to host and not migratable) with cpu pinning options and change placement option, ui automatically will clear cpu pinning options without any error message. Version-Release number of selected component (if applicable): ovirt-engine-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch How reproducible: Always Steps to Reproduce: 1. Create pinned vm with cpu pinning 2. Change placement option and check cpu pinning 3. Actual results: UI clear automatically cpu pinning without inform user about it Expected results: Or show error message, that user will lost cpu pinning, or like in 3.4 light with red conflict options(if conflict options on different tabs it's useful to light tabs as well) Additional info: It's actual for most conflict parameters in UI edit window