Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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
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.
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