4.2. Red Hat Gluster Storage Web Administration

When the user runs the systemctl reload command, the command returns an error. In addition, the monitoring integration configuration, the gluster integration configuration and the tendrl notifier configuration do not reload.

Workaround: Run systemctl restart command of Monitoring integration, Gluster integration and tendrl-notifier services and the configuration will be reloaded.

An unexpected reboot of storage nodes leads to service misconfiguration. As a result of this, bricks are marked ‘Down’ on the user interface.

Workaround: To get the correct status of the brick, node-agent and gluster-integration services need to be restarted.

On the Red Hat Gluster Storage Web Administration Console, the sort button does not work for Firefox. Thus clusters, hosts, volumes and other columns remain unsorted.

Workaround: To avail the sort button functionality, choose Chrome browser.

When the entire gluster cluster goes down because the hosts go down simultaneously, the WA dashboard only displays information about the cluster and the nodes being unhealthy. It does not provide detailed information about the health of the bricks and volumes.

During the installation of Red Hat Gluster Storage Web Administration, if the server has multiple active IP addresses, tendrl-ansible fails to execute the playbook and the installation fails.

Workaround: The variable {{ lookup('dig', ansible_fqdn) }} needs to be changed with the IP address that the user would want the system to be set up with.

For all the clusters that are currently managed by Web Administration, un-managing one cluster will result in all the clusters being unmanaged. You will have to re-import any cluster that is required.