RHBA-2015:0039 - Bug Fix Advisory

Topic

Updated gluster-nagios-common, rhsc-monitoring-uiplugin,
rhsc-setup-plugins, org.ovirt.engine-root, rhevm-branding-rhev,
otopi, ovirt-host-deploy, nagios-server-addons, and rhsc-doc
packages that fix multiple bugs and adds various enhancements
are now available for Red Hat Storage Console 3.

Description

Red Hat Storage Console is a powerful and simple web based Graphical User
Interface for managing a Red Hat Storage environment. It helps storage
administrators to easily create and manage multiple storage pools.

This advisory fixes various bugs in the Red Hat Storage Console Monitoring
User Interface Plug-in, Red Hat Storage Console Setup Plug-in, and Red Hat
Storage Console nagios-server-addons. Space precludes documenting all of
these changes in this advisory. Users are directed to the Red Hat Storage
3 Technical Notes, linked to in the References section, for information on
the most significant of these changes.

This update also adds the following new enhancements:

• A navigation link is added to the GlusterFS Monitoring Home page

in the Trends tab of Red Hat Storage Console. (BZ# 1138143)

• A new command is introduced to enable and disable monitoring using

the command line interface (CLI) after setting up Red Hat Storage Console.
When monitoring is enabled on the server, the Trends tab is displayed
with host and cluster utilization details. (BZ# 1111079)

• An enhancement has been added to brick utilization to display both the

thin-logical volume utilization and the actual thin pool utilization for
bricks with thin-logical volume. (BZ# 1143995)

All users of Red Hat Storage are advised to install these updated packages.

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
https://access.redhat.com/articles/11258

Affected Products

• Red Hat Gluster Storage Server for On-premise 3 for RHEL 6 x86_64
• Red Hat Gluster Storage Management Console (for RHEL Server) 3 x86_64
• Red Hat Gluster Storage Nagios Server 3 for RHEL 6 x86_64

Fixes

• BZ - RHBA-2015:0039 - [RHSC] Host after being rebooted, goes to non-responsive state momentarily before coming UP
• BZ - RHBA-2015:0039 - [RHSC] Adding Host - Error while executing action: A Request to the Server failed
• BZ - RHBA-2015:0039 - [RHSC] "VdcBLLException: NO_UP_SERVER_FOUND" in seen in engine logs
• BZ - RHBA-2015:0039 - From GuideMe link, adding Host using SSH PublicKey Authentication fails with "Error while executing action: Cannot install Host with empty password."
• BZ - RHBA-2015:0039 - [Nagios] - When glusterd is stopped, all the process displays incorrect status information.
• BZ - RHBA-2015:0039 - [RHSC] - Editing server when in Maintenance to move it to a different cluster, results in "Error While executing action: Host CPU type is not supported in this cluster compatibility version or is not supported at all".
• BZ - RHBA-2015:0039 - [Nagios] - nagios_server.conf gets overridden when updating nagios server and nodes with the latest rpms.
• BZ - RHBA-2015:0039 - [Nagios] Typo error in auto-config message
• BZ - RHBA-2015:0039 - Summary message during "rhsc-setup" regarding upgrading the RHS nodes to 3.0 to enable Nagios monitoring is missing the tag
• BZ - RHBA-2015:0039 - [Nagios] Cluster - quorum service displays information about a volume even after it is deleted
• BZ - RHBA-2015:0039 - [Nagios] Cluster auto-config service is warning with "(null)" status information when glusterd is down on some nodes in the cluster
• BZ - RHBA-2015:0039 - [Nagios] - when one brick in replicate volume goes faulty and if the other one is active geo replication volume status should be shown as 'PARTIAL_FAULTY'
• BZ - RHBA-2015:0039 - [New] - Geo-Replication status says "warning" and status informtion says "georeplication status could not be determined - Another transaction is in progress for vol_repmaster.Please try again after some time"
• BZ - RHBA-2015:0039 - [Nagios] Volume utilization is unknown with status information "Invalid host name <hostname-of-RHS-node>" when glusterd is stopped
• BZ - RHBA-2015:0039 - No option provided to DISABLE Nagios Monitoring either from RHSC UI or from CLI
• BZ - RHBA-2015:0039 - No option provided to RE-ENABLE Nagios Monitoring either from RHSC UI or from CLI, after disabling it once
• BZ - RHBA-2015:0039 - [Trends] Print icon and Refresh icon doesn't look like clickable buttons
• BZ - RHBA-2015:0039 - [Nagios] - Error message needs to be improved when discovery.py is run with a host which has the same host name of the host which is already being monitored by nagios.
• BZ - RHBA-2015:0039 - [Nagios] - When nagios-server-addons rpm is updated, default host and default service comes back.
• BZ - RHBA-2015:0039 - [Nagios] - When nagios-server-addons rpm is updated, email and snmp config files gets overriden.
• BZ - RHBA-2015:0039 - [Nagios] - Show y-axis values in percentage in the cluster utilization graph, the scale of the graph should not change as per utilization
• BZ - RHBA-2015:0039 - [EARLY ACCESS] glusterpmd.log very chatty
• BZ - RHBA-2015:0039 - [Nagios] - When all the nodes in a cluster are down, cluster status shows 'UP' with status information as 'OK:None of the volumes are in critical state'
• BZ - RHBA-2015:0039 - [Nagios] Volume status is seen to be in warning status with status information "null" when glusterd is stopped on one RHS node.
• BZ - RHBA-2015:0039 - [RHSC] Installation of host, should start the glusterpmd service if monitoring is enabled
• BZ - RHBA-2015:0039 - [RFE][RHSC] Provide a link to nagios web interface from RHSC in case monitoring is enabled
• BZ - RHBA-2015:0039 - [Nagios] - Discovery.py does not check for the correctness of nagios configuration before restarting nagios service
• BZ - RHBA-2015:0039 - [Nagios] Auto-config removes all the configuration if the host used for discovery is detached from the cluster.
• BZ - RHBA-2015:0039 - [Nagios] Quorum service is seen to be OK when it should actually be in CRITICAL state
• BZ - RHBA-2015:0039 - Brick utilization shows incorrect data for thinly provisioned LVs
• BZ - RHBA-2015:0039 - gluster bricks marked down in ovirt after vdsm restarted
• BZ - RHBA-2015:0039 - [RHSC] - Upgrading RHSC from 3.0.2 to 3.0.3 fails.
• BZ - RHBA-2015:0039 - [Nagios] - PING service status shows UNKNOWN with status information as "check_ping: %s:Warning threshold must be integer or percentage!"
• BZ - RHBA-2015:0039 - Add an info msg in rhsc-setup to ask the user to run auto-discovery to start monitoring
• BZ - RHBA-2015:0039 - [RHSC] - Updating from 2.1U5 to 3.0.3 fails with error ***L:ERROR Internal error: type object 'Stages' has no attribute 'CONFIG_DB_CREDENTIALS'
• BZ - RHBA-2015:0039 - [RHSC] - yum update rhsc-setup does not pull in ovirt-host-deploy package.
• BZ - RHBA-2015:0039 - [RHSC] - Reinstalling of host does not change the status to up.

CVEs

(none)

References

• http://www.redhat.com/security/updates/classification/#normal