Download Red Hat Enterprise Virtualization 3.4 Technical Notes

⁠C hapter 7. RHBA-2014 :0393 rhevm-reports
Chapter 7. RHBA-2014:0393 rhevm-reports
T he bugs contained in this chapter are addressed by advisory RHBA-2014:0393. Further information
about this advisory is available at https://rhn.redhat.com/errata/RHBA-2014-0393.html.
ovirt-engine-reports
BZ #10724 05
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 #1074 952
Previously, the rhevm-reports-setup command would fail when run on a system
configured to use certain locales. 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 when the message produced by checking the status
of the service did not contain the words 'dead', 'inactive', or 'stopped'.
Now, the conditional is dependent on a return code, and the rhevm-reportssetup command restarts the postgresql service without issue.
BZ #1064 827
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 #10724 66
Previously, if the rhevm-reports-setup command failed, after upgrading
reports from version 3.2 to version 3.3, it would 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, thus letting the user to try and run it again.
BZ #1059268
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.
Report a bug
17