- Issued:
- 2014-04-09
- Updated:
- 2014-04-09
RHBA-2014:0393 - Bug Fix Advisory
Synopsis
rhevm-reports 3.3.2 bug fix update
Type/Severity
Bug Fix Advisory
Red Hat Insights patch analysis
Identify and remediate systems affected by this advisory.
Topic
An updated rhevm-reports package that fixes a bug is now available.
Description
The Red Hat Enterprise Virtualization reports package provides a suite of
pre-configured reports and dashboards that enable you to monitor the system. The
reports module is based on JasperReports and JasperServer, and can also be used
to create ad-hoc reports.
All Red Hat Enterprise Virtualization reports and data warehouse users are
advised to upgrade to this updated package which addresses this issue.
Changes to the ovirt-engine-reports component:
- Previously, when the Red Hat Enterprise Virtualization Manager was configured
using a password that contained special characters, those special characters
would be escaped when stored in the 10-setup-database.conf file. However, the
rhevm-reports-setup command would not recognize such characters as being escaped
and would therefore fail to run. Now, escaped characters are correctly
interpreted. (BZ#1072405)
- Previously, the rhevm-reports-setup command would fail when run on a system
configured to use the Brazilian Portuguese language (pt_BR). This was caused by
an error in using the status of a service as a conditional, which resulted in
the postgresql service not being restarted. Now, the conditional is dependent on
a return code, and the rhevm-reports-setup command restarts the postgresql
service without issue. (BZ#1074952)
- Previously, the rhevm-reports-setup command would sometimes fail to establish
PKI trust the machine on which the Red Hat Enterprise Virutalization Manager was
installed, causing the command to fail. Now, the method of retrieving the root
certificate authority certificate from the SSL session has been revised to
support a greater variety of SSL configurations. (BZ#1064827)
- Previously, running the rhevm-reports-setup command after upgrading reports
from version 3.2 to version 3.3 would fail if the Apache httpd was stopped. This
would cause the command to exit before writing to the 10-setup-database.conf
file, resulting in a new engine_reports user being created with a random
password and preventing the rhevm-reports-setup command from succeeding in the
future. Now, the writing of credentials is performed earlier in the setup
process, ensuring that credentials are correctly written even in the event of a
failure. (BZ#1072466)
- Previously, the BR18 report would contain inaccurate values under some
circumstances. This was caused by the 'Unknown OS' value being changed to 'Other
OS' and the reports query filtering results in accordance with the previous
value. Now, results are filtered in accordance with the operating system ID
instead of the operating system text description, allowing the BR18 report to
display the correct values. (BZ#1059268)
Solution
Before applying this update, make sure all previously-released errata
relevant to your system have been applied.
Affected Products
- Red Hat Virtualization 3.3 x86_64
Fixes
- BZ - 1059268 - [rhevm-reports] - BR18 - the numbers of OSs are incorrect
- BZ - 1064827 - ssl2jkstrust.py does not get root ca from chain in some cases
- BZ - 1072405 - ovirt-engine-reports-setup does not handle escape characters in the 10-setup-database.conf ENGINE_DB_PASSWORD
- BZ - 1072466 - [RHEV] Upgrading rhevm-reports from 3.2 to 3.3 without Apache running fails and prevents any future rhevm-reports-setup from succeeding
- BZ - 1074952 - rhevm-reports-setup error on a system installed in Brazilian Portuguese
CVEs
(none)
References
(none)
Red Hat Virtualization 3.3
SRPM | |
---|---|
rhevm-reports-3.3.2-3.el6ev.src.rpm | SHA-256: c83931a4639b9fa610efc9798852b579b8badbe2e8d75472f4c1b6ccbeef68b7 |
x86_64 | |
rhevm-reports-3.3.2-3.el6ev.noarch.rpm | SHA-256: 51454d9cc524ac1c68ccb22cf84c0959e3d4f0677468045e98a4ead9e3be8ca7 |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.