#4501 [RFE] Preserve client and server installation logs
Closed: wontfix 5 years ago Opened 9 years ago by mkosek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1131909

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:

Note: We should use the same mechanism for ipaupgrade.log. Currently it is always appended to, which gets confusing after a few upgrade runs.

We could log to /var/log/ipa/$TIMESTAMP-server-install.log, and, for backwards compatibility, symlink /var/log/ipaserver-install.log to the latest file written there.

In #4830 (duplicate), jmritenour suggests naming the log e.g. ipaclient-install-2015_01_09_08-17.log.

def logging_setup(options):
    import datetime
    datetime = datetime.datetime.now()
    stamp = datetime.strftime('%Y_%m_%d_%H-%M')
    log_file = "/var/log/ipaclient-install-"+stamp+".log"

Moving to 4.3, we are too close to 4.2 deadline to be able to handle stretch RFEs.

freeipa triage: let's wait with the log changes(#5726, #5728, #4501, #5724) to next major release where we will have better picture of the desired state(also in relation with journald and other efforts) and how backwards compatibility should be handled.

To not forget the initial patch: https://www.redhat.com/archives/freeipa-devel/2016-March/msg00166.html

Metadata Update from @mkosek:
- Issue assigned to mbasti
- Issue set to the milestone: Future Releases

7 years ago

Metadata Update from @mbasti:
- Assignee reset

6 years ago

Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.

Metadata Update from @rcritten:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata