Bug 913798

Summary: [RHSC] Peer-probe notification on the console says "You can Import them to oVirt engine or Detach them from the cluster."
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: rhscAssignee: Kanagaraj <kmayilsa>
Status: CLOSED ERRATA QA Contact: Shruti Sampat <ssampat>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: dtsang, knarra, mmahoney, pprakash, rhs-bugs, sankarshan, shaines
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard: https://engineering.redhat.com/trac/rhs-tests/ticket/912
Fixed In Version: qa7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-23 22:25:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Shruti Sampat 2013-02-22 05:51:40 UTC
Created attachment 701002 [details]
screenshot

Description of problem:
---------------------------------------
Peer probe from gluster CLI results in a notification to appear on the Console which says the following - 
"Some new hosts are detected in the cluster. You can Import them to oVirt engine or Detach them from the cluster."

It should say Red Hat Storage Console instead of oVirt Engine.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.0-0.qa6.el6rhs 

How reproducible:
Always

Steps to Reproduce:
1. Peer probe from a server in the cluster to another server.
  
Actual results:
The notification appearing on the Console says 'oVirt Engine' as described above.

Expected results:
It should say Red Hat Storage Console instead of oVirt Engine.

Additional info:
Find screenshot attached.

Comment 2 Shireesh 2013-03-01 07:22:39 UTC
We'll just make it generic by using the term "engine" instead of "oVirt engine".

Comment 3 Dustin Tsang 2013-03-08 18:38:35 UTC
verified in 2.1.0-0.qa7.el6rhs

Comment 4 Scott Haines 2013-09-23 22:25:38 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.

http://rhn.redhat.com/errata/RHBA-2013-1262.html