Bug 1255405
Summary: | User with VmImporterExport on system can't import vm | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Ondra Machacek <omachace> |
Component: | General | Assignee: | Martin Sivák <msivak> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ondra Machacek <omachace> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.6.0 | CC: | alukiano, amureini, bugs, dfediuck, gklein, lpeer, lsurette, mavital, mgoldboi, pstehlik, rbalakri, rgolan, Rhev-m-bugs, sbonazzo, v.astafiev, yeylon, ykaul, ylavi |
Target Milestone: | ovirt-3.6.3 | Flags: | rule-engine:
ovirt-3.6.z+
rule-engine: blocker+ mgoldboi: planning_ack+ rgolan: devel_ack+ pstehlik: testing_ack+ |
Target Release: | 3.6.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
The new Disk QoS policy permissions were not added to the Import/Export user.
Consequence:
User with correct Import permissions could not import disks when a QoS setting was associated with it.
Fix:
All users with Import/Export permissions at the time of update (both built in and custom) get the Disk profile permissions.
Result:
Importing VM with disk profiles now works properly.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-02-18 11:11:01 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: | 1108153 |
Description
Ondra Machacek
2015-08-20 13:41:53 UTC
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 We need to make sure VmImportExport must have assign disk profile action group in its definition. should be and easy fix and not risky. Also we need to make sure that cpu profile behaves the same. Meital I think this is regression from 3.5? I believe it was working. Can you help reproduce on 3.5? VmImporterExport is role which was introduced in 3.6. So we can't try on 3.5. Checked on rhevm-3.5.7-0.1.el6ev.noarch We do not have such role under 3.5, so it is not regression. |