Red Hat Training

A Red Hat training course is available for Red Hat Gluster Storage

3.2. Red Hat Storage Console

Issues related to Red Hat Storage Console

  • BZ#1164662
    The Trends tab in the Red Hat Storage Console appears to be empty after the ovirt engine restarts. This is due to the Red Hat Storage Console UI-plugin failing to load on the first instance of restarting the ovirt engine.
    Workaround: Refresh(F5) the browser page to load the Trends tab.
  • BZ#1165269
    When you add a Red Hat Storage node in the Red Hat Storage Console using its IP address and remove it from the Red Hat Storage trusted Storage Pool, and consequently use the FQDN of the node to add it again to the Trusted Storage pool, the operation fails. This results in the node becoming unresponsive.
    Workaround: Remove the unresponsive node from the Red Hat Storage Trusted Storage Pool and try adding it again.
  • BZ#1166563
    During the initial set up of the Red Hat Storage Console setup tool, if you disable the monitoring feature and later enable it using the command - rhsc-monitoring enable, the answer file in the Red Hat Storage Console setup tool file would not get updated with the new value. Consequently if you upgrade the Red Hat Storage Console and execute the Red Hat Storage Console setup again, it looks for the value in the answer file and finds that monitoring is not enabled and accordingly sets it to the disabled state.
    Workaround: Execute the rhsc-monitoring enable command again.
  • BZ#1167305
    The Trends tab on the Red Hat Storage Console does not display the thin-pool utilization graphs in addition to the brick utilization graphs. Currently, there is no mechanism for the UI plugin to detect if the volume is provisioned using the thin provisioning feature.
  • BZ#1167572
    On editing the cluster version in the Edit Cluster dialog box on the Red Hat Storage Console, the compatible version field gets loaded with the highest available compatibility version by default, instead of the current version of the cluster.
    Workaround: Select the correct version of the cluster in the Edit Cluster dialog box before clicking on the OK button.
  • BZ#916095
    If Red Hat Storage node is added to the cluster using IP address and the same Red Hat Storage node is later added using the FQDN (Fully Qualified Domain Name), the installation fails.
  • BZ# 990108
    Resetting the user.cifs option using the Create Volume operation on the Volume Options tab on the Red Hat Storage Console reports a failure.
  • BZ# 978927
    Log messages that Red Hat Storage Console is trying to update VM/Template information are displayed.
  • BZ# 880509
    When run on versions higher than Firefox 17, the Red Hat Storage Console login page displays a browser incompatibility warning. Red Hat Storage Console can be best viewed in Firefox 17 and higher versions.
  • BZ# 1049759
    When rhsc-log-collector command is run, after collecting logs from different servers, the Terminal becomes garbled and unusable.
    Workaround: Run the reset command.
  • BZ# 1054366
    In Internet Explorer 10, while creating a new cluster with Compatibility version 3.3, the Host drop down list does not open correctly. Also, if there is only one item, the drop down list gets hidden when the user clicks on it.
  • BZ# 1053395
    In Internet Explorer, while performing a task, an error message Unable to evaluate payload is displayed.
  • BZ# 1056372
    When no migration is occurring, incorrect error message is displayed for the stop migrate operation.
  • BZ# 1049890
    When gluster daemon service is restarted, failed Rebalance is started automatically and the status is displayed as Started in the Red Hat Storage Console.
  • BZ# 1048426
    When there are more entries in Rebalance Status and remove-brick Status window, the column names scrolls up along with the entries while scrolling the window.
    Workaround: Scroll up the Rebalance Status and remove-brick Status window to view the column names.
  • BZ# 1053112
    When large sized files are migrated, the stop migrate task does not stop the migration immediately but only after the migration is complete.
  • BZ# 1040310
    If the Rebalance Status dialog box is open in the Red Hat Storage Console while Rebalance is being stopped from the Command Line Interface, the status is currently updated as Stopped. But if the Rebalance Status dialog box is not open, the task status is displayed as Unknown because the status update relies on the gluster Command Line Interface.
  • BZ# 1051696
    When a cluster with compatibility version 3.2 contains Red Hat Storage 2.1 U2 nodes, creating Volume with bricks in root partition fails and the force option to allow bricks in root partition is not displayed.
    Workaround: Do not create bricks in root partition or move the Cluster Compatibility Version to 3.3.
  • BZ# 838329
    When incorrect create request is sent through REST api, an error message is displayed which contains the internal package structure.
  • BZ# 1049863
    When Rebalance is running on multiple volumes, viewing the brick advanced details fails and the error message could not fetch brick details, please try again later is displayed in the Brick Advanced Details dialog box.
  • BZ# 1022955
    Rebalance or remove-brick cannot be started immediately after stopping Rebalance or remove-brick, when a large file migration is in progress, as part of the previous operation (rebalance or remove-brick), even though it says it has stopped.
  • BZ# 1015455
    The information on successfully completed Rebalance volume task is cleared from the Red Hat Storage Console after 5 minutes. The information on failed tasks is cleared after 1 hour.
  • BZ# 1038691
    The RESTful Service Description Language (RSDL) file displays only the response type and not the detailed view of the response elements.
    Workaround: Refer the URL/API schema for detailed view of the elements of response type for the actions.
  • BZ# 1024184
    If there is an error while adding bricks, all the "." characters of FQDN / IP address in the error message will be replaced with "_" characters.
  • BZ# 982625
    Red Hat Storage Console allows adding Red Hat Storage 2.0+ and Red Hat Storage 2.1 servers into a 3.0 Cluster which is not supported in Red Hat Storage.
  • BZ# 975399
    When Gluster daemon service is restarted, the host status does not change to UP from Non-Operational immediately in the Red Hat Storage Console. There would be a 5 minute interval for auto-recovery operations which detect changes in Non-Operational hosts.
  • BZ# 971676
    While enabling or disabling Gluster hooks, the error message displayed if all the servers are not in UP state is incorrect.
  • BZ# 1054759
    A vdsm-tool crash report is detected by Automatic Bug Reporting Tool (ABRT) in Red Hat Storage Node as the /etc/vdsm/vdsm.id file was not found during the first time.
    Workaround: Execute the command /usr/sbin/dmidecode -s system-uuid > /etc/vdsm/vdsm.id before adding the node to avoid the vdsm-tool crash report.
  • BZ# 1057122
    While configuring the Red Hat Storage Console to use a remote database server, on providing either yes or no as input for Database host name validation parameter, it is considered as No.
  • When remove-brick operation fails on a volume, the Red Hat Storage node does not allow any other operation on that volume.
    Workaround: Perform commit or stop for the failed remove-brick task, before another task can be started on the volume.
  • BZ# 1060991
    In Red Hat Storage Console, Technology Preview warning is not displayed for stop remove-brick operation.
  • BZ# 1057450
    Brick operations like adding and removing a brick from Red Hat Storage Console fails when Red Hat Storage nodes in the cluster have multiple FQDNs (Fully Qualified Domain Names).
    Workaround: Host with multiple interfaces should map to the same FQDN for both Red Hat Storage Console and gluster peer probe.
  • BZ# 958803
    When a brick process goes down, the brick status is not updated and displayed immediately in the Red Hat Storage Console as the Red Hat Storage Console synchronizes with the gluster Command Line Interface every 5 minutes for brick status.
  • BZ# 1038663
    Framework restricts displaying delete actions for collections in RSDL display.
  • BZ# 1061677
    When Red Hat Storage Console detects a remove-brick operation which is started from gluster Command Line Interface, engine does not acquire lock on the volume and Rebalance task is allowed.
    Workaround: Perform commit or stop on remove-brick operation before starting Rebalance.
  • BZ# 1061813
    After stopping, committing, or retaining bricks from the Red Hat Storage Console UI, the details of files scanned, moved, and failed are not displayed in the Tasks pane.
    Workaround: Use Status option in Activities column to view the details of the remove-brick operation.
  • BZ# 924826
    In Red Hat Storage Console, parameters related to Red Hat Enterprise Virtualization are displayed while searching for Hosts using the Search bar.
  • BZ# 1062612
    When Red Hat Storage 2.1 Update 2 nodes are added to 3.2 cluster, users are allowed to perform Rebalance and remove-brick tasks which are not supported for 3.2 cluster.
  • BZ# 977355
    When resolving a missing hook conflict, if one of the servers in the cluster is not online, an error message is displayed without the server name. Hence, the server which was down can not be identified.
    Workaround: Identify the information on the server which was down from the Hosts tab.
  • BZ# 1046055
    While creating volume, if the bricks are added in root partition, the error message displayed does not contain the information that Allow bricks in root partition and re-use the bricks by clearing xattrs option needs to be selected to add bricks in root partition.
    Workaround: Select Allow bricks in root partition and re-use the bricks by clearing xattrs option to add bricks in root partition.
  • BZ# 1060991
    In Red Hat Storage Console UI, Technology Preview warning is not displayed for stop remove-brick operation.
  • BZ# 1066130
    Simultaneous start of Rebalance on volumes that span same set of hosts fails as gluster daemon lock is acquired on participating hosts.
    Workaround: Start Rebalance again on the other volume after the process starts on first volume.
  • BZ# 1086718
    The Red Hat Access Plug-in related answers are not written to the answer file correctly when the rhsc-setup --generate-answer=answer-file command is executed and hence the next offline execution of rhsc-setup (rhsc-setup --offline --config-append=answer-file) asks Red Hat Access Plug-in related questions again.
    Workaround:
    1. Add the entry given below in the answer-file OVESETUP_SYSTEM/configureRedhatAccessPlugin=bool:False
    2. Execute the Red Hat Storage Console setup script in the offline mode rhsc-setup --offline --config-append=answer-file
  • BZ# 1086723
    Auto installation of Red Hat Storage Console using the answer file in Red Hat Storage Console-2.1.2 fails with the following warning message:
    [WARNING] Current installation does not support upgrade. It is recommended to clean your installation using rhsc-cleanup and re-install.
    Workaround:
    1. Execute the command: yum update rhsc-setup
    2. Perform the Red Hat Storage Console auto installation using the answer-file with the command: rhsc-setup --config-append=answer-file

Issues related to the Red Hat Storage Console Command Line Interface:

  • BZ# 928926
    When you create a cluster through API, enabling both gluster_service and virt_service is allowed though this is not supported.
  • BZ# 1059806
    In Red Hat Storage Console Command Line Interface, removing a cluster using its name fails with an error message and the same cluster gets deleted if UUID is used in remove command.
  • BZ# 1108688
    An image in the Nagios home page is not transferred via SSL and the Security details displays the following message:
    Connection Partially Encrypted.
  • BZ# 1111549
    In the Red Hat Storage Console, if the name provided in the Name field of the host in the New Host" pop-up is different from the Hostname provided in Nagios, the utilization details for the hosts are not displayed in Trends tab.
  • BZ# 1100960
    Nagios does not support SELinux fully and this impacts rhsc-setup and normal usage of Red Hat Console with Nagios.
    Workaround: Run SELinux in permissive mode.
  • BZ# 1113103
    The Network Utilization graph shows an error that RRD data does not exist.
    Workaround: After midnight of the next day, the sadf output file gets corrected automatically and graph works fine.
  • BZ# 1121612
    The mount points for a host can not be detected from Trends tab in Red Hat Storage Console GUI.
    View mount point Disk Utilization using Nagios GUI.
  • After stopping the rebalance/remove-brick operation from Red Hat Storage Console GUI, clicking on rebalance/remove-brick status button throws Unable to fetch data error.
  • Both Red Hat Storage Console and Hadoop Ambari are using Nagios to monitor Red Hat Storage Server nodes, but there is version conflict for the package nagios-plugins, which blocks the installation of nagios required by Hadoop Ambari. Red Hat Stroage server 3.0 nodes are pre-bundled with latest version of nagios-plugin. If you want to use Red Hat Storage Console, then you will not be able to install Nagios via Ambari and utilize the pre-build hadoop monitors/alerts. HDP 2.0.6 is not supported for Red Hat Storage 3.0 release.

23001%2C+3.0+Update+3+Release+Notes-319-02-2015+16%3A26%3A20Report a bug