Description of problem: Help of the engine-log-collector contains default path for logs, which is not actually correct. The name of the log file contains date and time when was the help generated. Such a path is not actually default, since it will never exist. Therefore it makes no sense to claim it's a default path. Version-Release number of selected component (if applicable): both 3.3 and 3.4 releases of log-collector Steps to Reproduce: 1. repreat several times: engine-log-collector --help | grep '/var/log' -A 1 Actual results: [root@vm-18-223 ~]# engine-log-collector --help | grep '/var/log' -A 1 --log-file=PATH path to log file (default=/var/log/ovirt-engine/ovirt- log-collector/ovirt-log-collector-20140205112847.log) [root@vm-18-223 ~]# engine-log-collector --help | grep '/var/log' -A 1 --log-file=PATH path to log file (default=/var/log/ovirt-engine/ovirt- log-collector/ovirt-log-collector-20140205112856.log) [root@vm-18-223 ~]# engine-log-collector --help | grep '/var/log' -A 1 --log-file=PATH path to log file (default=/var/log/ovirt-engine/ovirt- log-collector/ovirt-log-collector-20140205112901.log) Expected results: path to log file (default=/var/log/ovirt-engine/ovirt- log-collector/ovirt-log-collector-<TIMESTAMP>.log) or not to report default file at all or log to single file (not creating a new file for each run), then a default file would exist
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.
Verified in 3.5.0-0.1.master.el6
oVirt 3.5 has been released and should include the fix for this issue.