Bug 1260518 - Require multiple local storage domains as supported function
Summary: Require multiple local storage domains as supported function
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.3
Hardware: All
OS: Linux
high
urgent
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Allon Mureinik
QA Contact: Elad
URL:
Whiteboard:
Depends On: 1266132
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-07 06:50 UTC by Marcus West
Modified: 2019-04-28 10:50 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-09 21:13:03 UTC
oVirt Team: Storage


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0376 normal SHIPPED_LIVE Red Hat Enterprise Virtualization Manager 3.6.0 2016-03-10 01:20:52 UTC
Red Hat Knowledge Base (Solution) 285953 None None None 2015-12-16 16:25:59 UTC

Description Marcus West 2015-09-07 06:50:21 UTC
Require multiple local storage domains as supported function

Comment 4 Marina Kalinin 2015-12-16 17:45:18 UTC
Allon, would it matter if the host is RHEL6 or RHEL7?
Specific customer interested in this feature is currently using RHEL6 hosts and interested in having this on RHEL6.

Comment 6 Allon Mureinik 2016-01-03 13:17:00 UTC
(In reply to Marina from comment #4)
> Allon, would it matter if the host is RHEL6 or RHEL7?
> Specific customer interested in this feature is currently using RHEL6 hosts
> and interested in having this on RHEL6.
Unless there's some specific bug in some underlying component in either version, it shouldn't matter.

Comment 7 Elad 2016-01-05 09:19:15 UTC
Tested storage sanity using multiple local data domains reside on different host drives. No special issues were found, all cases has passed.


Used:
rhevm-3.6.1.3-0.1.el6.noarch
vdsm-4.17.15-0.el7ev.noarch

Comment 10 errata-xmlrpc 2016-03-09 21:13:03 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/RHEA-2016-0376.html


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