Bug 1578715 - The info icon for the volume in manage gluster is not providing complete information.
Summary: The info icon for the volume in manage gluster is not providing complete info...
Keywords:
Status: CLOSED DUPLICATE of bug 1578717
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-16 09:02 UTC by Mugdha Soni
Modified: 2018-05-16 11:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-16 11:10:42 UTC
Embargoed:


Attachments (Terms of Use)
screenshot of information provided from the info icon. (141.31 KB, image/png)
2018-05-16 09:02 UTC, Mugdha Soni
no flags Details

Description Mugdha Soni 2018-05-16 09:02:43 UTC
Created attachment 1437200 [details]
screenshot of information provided from the info icon.

Description of problem:
----------------------------------------------
In gluster management wizard ,when clicked on the info icon under the volume tab, the "is arbitar"parameter in the info tab is empty.It should have a output displayed there in UI.

Version-Release number of selected component (if applicable):
-----------------------------------------------
cockpit-ovirt-dashboard-0.11.999-0.0.master.el7.noarch


How reproducible:
-----------------------------------------------
Everytime

Steps to Reproduce:
1.Successfully deploy gluster and hosted engine deployment.
2.Successfully create the additional volume on the hosts.
3.Go back to the cockpit UI and click on the info icon under "volumes" tab.

Actual results:
The " is arbitar" parameter has no output even for the arbitar volume created.

Expected results:
The "is arbitar" patameter should have an output.

Comment 2 Sahina Bose 2018-05-16 11:10:42 UTC

*** This bug has been marked as a duplicate of bug 1578717 ***


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