Bug 1253142 - If Quotas are enabled, even in Audit mode, active VMs' disks cannot be edited
Summary: If Quotas are enabled, even in Audit mode, active VMs' disks cannot be edited
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.0
Hardware: Unspecified
OS: Linux
medium
high
Target Milestone: ovirt-3.5.5
: 3.5.5
Assignee: Dudi Maroshi
QA Contact: Artyom
URL:
Whiteboard: sla
Depends On: 1193643
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-13 06:15 UTC by rhev-integ
Modified: 2019-07-16 11:59 UTC (History)
15 users (show)

Fixed In Version: ovirt-engine-3.5.5-1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1193643
Environment:
Last Closed: 2015-10-26 18:33:07 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1351393 0 None None None Never
Red Hat Product Errata RHBA-2015:1938 0 normal SHIPPED_LIVE Red Hat Enterprise Virtualization Manager 3.5.5 update 2015-10-26 22:31:23 UTC
oVirt gerrit 43951 0 ovirt-engine-3.5 MERGED core: Allow VM disks editing after enabling quota on data center Never
oVirt gerrit 44768 0 master MERGED core: Allow VM disks editing after enabling quota on data center Never
oVirt gerrit 44769 0 ovirt-engine-3.6 MERGED core: Allow VM disks editing after enabling quota on data center Never

Comment 1 Artyom 2015-09-20 13:34:23 UTC
Verified on rhevm-3.5.5-0.1.el6ev.noarch

Comment 2 Eyal Edri 2015-10-12 17:36:52 UTC
setting missing ovirt-3.5.5 milestone for 3.5.5 bugs.

Comment 4 errata-xmlrpc 2015-10-26 18:33:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1938.html


Note You need to log in before you can comment on or make changes to this bug.