RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1428690 - ipa-backup does not create log file at /var/log/
Summary: ipa-backup does not create log file at /var/log/
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-03 07:23 UTC by Seshadri
Modified: 2020-12-14 08:17 UTC (History)
13 users (show)

Fixed In Version: ipa-4.6.5-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:09:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure freeipa c b384b297f44e3fb96b1509affabcd9f0011592a7 0 None None None 2019-08-28 08:04:01 UTC
Red Hat Product Errata RHBA-2019:2241 0 None None None 2019-08-06 13:09:26 UTC

Description Seshadri 2017-03-03 07:23:14 UTC
Description of problem:

I accidentally ran into this issue when I tried to run ipa-backup command on a machine that was no more an IPA server. Ran the ipa-backup command on the machine and it failed suitably indicating that IPA server is not configured, which is fine. It went on to state that more information can be found in /var/log/ipabackup.log

But no such file was created. See below:

[root@someidm0X ~]# ipa-backup 
IPA is not configured on this system.
The ipa-backup command failed. See /var/log/ipabackup.log for more information
[root@someidm0X ~]# ls /var/log/ipabackup.log
ls: cannot access /var/log/ipabackup.log: No such file or directory

Version-Release number of selected component (if applicable):
[root@someidm0X ~]# ipa-server-install --version
4.4.0
[root@someidm0X ~]# ipa-backup --version
4.4.0

How reproducible:
Everytime

Steps to Reproduce:
1. Install the ipa-server packages.
2. Do NOT configure IPA server.
3. Run ipa-backup command.

Actual results:
ipa-backup command fails and reports that /var/log/ipabackup.log contains more information, even though such a file is not created.

Expected results:
Option 1:
ipa-backup command fails, creates /var/log/ipabackup.log and adds failure details there.
Option 2:
ipa-backup command fails, does not notify user that more information is available in /var/log/ipabackup.log 

Additional info:
NA

Comment 4 Petr Vobornik 2017-03-31 13:39:31 UTC
Upstream ticket:
https://pagure.io/freeipa/issue/6843

Comment 5 Petr Vobornik 2017-03-31 13:43:01 UTC
It's a bug in ipa tools framework. 

Verification of installation is done even before logging is initialized and the error message is standard part of error reporting. Fix is more complex than it seems. 

Might be fixed in next major upstream version.

Comment 8 Christian Heimes 2018-05-03 15:36:15 UTC
Fixed upstream
master:
https://pagure.io/freeipa/c/648d7c0d38ef99196531e94cd9803c630e7fb05c

Comment 10 Florence Blanc-Renaud 2018-08-24 07:16:31 UTC
Fixed upstream
ipa-4-6:
https://pagure.io/freeipa/c/9182917280a5c2590fa677729db54b38a9ac4d1f

Comment 14 Tibor Dudlák 2019-07-30 10:02:41 UTC
Fixed upstream
master:
https://pagure.io/freeipa/c/402246a72990f77591f5efaec7ff0bc0cf82f416

Comment 16 errata-xmlrpc 2019-08-06 13:09:02 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2241

Comment 17 François Cami 2019-08-27 10:06:43 UTC
Fixed upstream
master:
https://pagure.io/freeipa/c/a71c59c7c881ffcc76ba9b02d02ddd31a0f829b6

Comment 18 François Cami 2019-08-27 14:09:00 UTC
Fixed upstream
ipa-4-8:
https://pagure.io/freeipa/c/0010d07c5d703da95f46bb334922d15322db0ccc

Comment 20 François Cami 2019-08-28 07:59:45 UTC
Fixed upstream
ipa-4-7:
https://pagure.io/freeipa/c/b384b297f44e3fb96b1509affabcd9f0011592a7


Note You need to log in before you can comment on or make changes to this bug.