Bug 1327848 - [RFE] lack of warning message when someone is trying to add RHEV-H already managed by one RHEV-M to the other RHEV-M
Summary: [RFE] lack of warning message when someone is trying to add RHEV-H already ma...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.6
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-16 20:06 UTC by Olimp Bockowski
Modified: 2022-04-21 06:44 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-22 09:10:14 UTC
oVirt Team: Infra
Target Upstream Version:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45825 0 None None None 2022-04-21 06:44:00 UTC

Description Olimp Bockowski 2016-04-16 20:06:54 UTC
Description of problem:

When RHEV-H is managed by one RHEV-M then it is still possible to add the same RHEV-H to the other RHEV-M without any question or warning.
RHEV is enterprise solution and in enterprise environment there are quite often tens or hundreds hypervisors and at least 2 RHEV-M (prod and test purpose). So it is very easy to make a mistake and accidentally add wrong RHEV-H to the other Manager

Version-Release number of selected component (if applicable):
rhevm-3.5.8-0.1.el6ev.noarch

How reproducible:
every time

Steps to Reproduce:
1. set one RHEV-M1, add RHEV-H
2. set the other RHEV-M2
3. add RHEV-H already managed by RHEV-M1 to the other Manager (RHEV-M2)

Actual results:
No message that RHEV-H is already managed. It is possible to add RHEV-H every time

Expected results:
Warning message and ask for conformation

Additional info:

Comment 20 Moran Goldboim 2018-07-22 09:10:14 UTC
Closing this RFE due to low request rate and overall low priority.
if needed please reopen with customer/use-case attached.


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