Bug 651780

Summary: bacula / wrong argument in /usr/libexec/bacula/make_catalog_backup.pl
Product: Red Hat Enterprise Linux 6 Reporter: Leon Fauster <leonfauster>
Component: baculaAssignee: Jan Görig <jgorig>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: azelinka, johnny, moongloom, ovasik, pkovar
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: bacula-5.0.0-8.el6 Doc Type: Bug Fix
Doc Text:
Prior to this update, the make_catalog_backup.pl script created a MySQL configuration file, which had the file permissions set to world-writeable and world-readable so that MySQL did not accept the configuration file with these permissions and the MySQL database login configuration was not used. As a result, it was not possible to complete a MySQL database dump. With this update, the configuration file is now created with correct permissions, and the MySQL database login configuration is used by MySQL so that it is now possible to complete the MySQL database dump as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-31 09:16:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Leon Fauster 2010-11-10 09:36:21 UTC
==========================================
Description of problem:

the release 5.0.0 has a bug in /usr/libexec/bacula/make_catalog_backup.pl
the umask argument in line 92 in wrong - this is correct in the upstream version (5.0.3)


==========================================
How reproducible:

executing make_catalog_backup.pl will generate .my.cnf in /var/spool/bacula
with wrong permissions which leads to fail in trying to reading it.

==========================================
Version-Release number of selected component (if applicable):

5.0.0-7.el6

Comment 4 Suzanne Logcher 2011-02-15 21:44:54 UTC
This issue was proposed for RHEL 6.1 FasTrack but did not get resolved in time.
It has been moved to RHEL 6.2 FasTrack.

Comment 7 Jan Görig 2011-06-08 16:23:21 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause
- make_catalog_backup.pl creates MySQL configuration file world-writeable and readable
- MySQL doesn't accept config with these permissions and database login configuration isn't used
Consequence
- database dump isn't completed
Fix
- file is created with correct permissions
Result
- login configuration is used by MySQL and dump is completed

Comment 9 Petr Kovar 2011-06-15 16:05:45 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,9 +1 @@
-Cause
+Prior to this update, the make_catalog_backup.pl script created a MySQL configuration file, which had the file permissions set to world-writeable and world-readable so that MySQL did not accept the configuration file with these permissions and the MySQL database login configuration was not used. As a result, it was not possible to complete a MySQL database dump. With this update, the configuration file is now created with correct permissions, and the MySQL database login configuration is used by MySQL so that it is now possible to complete the MySQL database dump as expected.-- make_catalog_backup.pl creates MySQL configuration file world-writeable and readable
-- MySQL doesn't accept config with these permissions and database login configuration isn't used
-Consequence
-- database dump isn't completed
-Fix
-- file is created with correct permissions
-Result
-- login configuration is used by MySQL and dump is completed

Comment 12 errata-xmlrpc 2011-08-31 09:16:49 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-1232.html

Comment 13 Lukáš Nykrýn 2011-10-13 08:07:52 UTC
*** Bug 745017 has been marked as a duplicate of this bug. ***

Comment 14 Petr Hracek 2013-02-18 09:46:28 UTC
*** Bug 911574 has been marked as a duplicate of this bug. ***