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 1131909 - [RFE] Preserve client and server installation logs
Summary: [RFE] Preserve client and server installation logs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-20 09:24 UTC by Jiri Belka
Modified: 2018-12-05 19:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-05 19:57:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jiri Belka 2014-08-20 09:24:10 UTC 
Description of problem:
ipaclient-install.log is overwritten with every command execution, this seems odd. it should either append or create a log with timestamp in filename.

Version-Release number of selected component (if applicable):
ipa-client-3.3.3-28.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. run ipa-client-install
2. run again
3.

Actual results:
logged data about first run are lost

Expected results:
logged data should be kept

Additional info:
Comment 2 Martin Kosek 2014-08-20 10:41:55 UTC 
Client and Server install behaves this way on purpose. For the server it makes sense because the log has about 40M and if you are testing many installations on one machine, you could quickly run out of disk space.

But it is a reasonable RFE that should be considered upstream. I will create an upstream ticket.
Comment 3 Martin Kosek 2014-08-20 10:43:08 UTC 
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4501
Comment 6 Petr Vobornik 2016-03-17 15:32:06 UTC 
update: is not planned to be implemented in FreeIPA 4.4. Maybe it will be in 4.5.
Comment 9 Rob Crittenden 2018-12-05 19:57:46 UTC 
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker a long time ago (see link to the upstream ticket above), but it was unfortunately not given priority either in the upstream project, nor in Red Hat Enterprise Linux.

Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.

To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you. Please note that you can still track this request or even offer help in the referred upstream Pagure ticket to expedite the solution.
Note You need to log in before you can comment on or make changes to this bug.