Description of problem: Currently, ovirt-host-deploy logs have these file names: ovirt-host-deploy-something.log - For deploy (New or Reinstall) actions ovirt-host-mgmt-something.log - For all other actions. These other actions include: - Check for updates - Update - Enroll Certificates Each of these should have a different log file name prefix, so that it's possible to have e.g. different rotation policies. Opening this bug for the engine side. host-deploy itself writes the logs on the host side, it can probably be nice if there it has the same prefix too, but is not important usually - because if successful, they are removed there after being copied to the engine, and the file name on the engine is set by the engine.
AFAIK in 4.2 we don't produce any logs for "check for update", only for actual update, but let's look at this within 4.3 cycle and let's make necessary adjustments to be able to define different logrotate settings for each flow log files.
Martin - not sure how your new Summary is different from bug 1519414. If you want to just close current, fine. If you think that some other specific solution is better than what I proposed in comment 0, why not add details?
(In reply to Yedidyah Bar David from comment #5) > Martin - not sure how your new Summary is different from bug 1519414. If you > want to just close current, fine. If you think that some other specific > solution is better than what I proposed in comment 0, why not add details? There are several new Ansible flows added in 4.2 and other planned in 4.3 and each of them could specify its own logfile (hardcoded in engine source code). So we need to make sure everything is documented and properly added to logrotate
(In reply to Martin Perina from comment #4) > AFAIK in 4.2 we don't produce any logs for "check for update", only for > actual update, but let's look at this within 4.3 cycle and let's make > necessary adjustments to be able to define different logrotate settings for > each flow log files. Any update on this? Also commented on bug 1519414. Do you want to close current? OK for me. Do we keep logs for ansible-based "check-for-updates"? Couldn't find them. If you want to keep it open for that, or anything similar, fine for me as well.
(In reply to Yedidyah Bar David from comment #8) > (In reply to Martin Perina from comment #4) > > AFAIK in 4.2 we don't produce any logs for "check for update", only for > > actual update, but let's look at this within 4.3 cycle and let's make > > necessary adjustments to be able to define different logrotate settings for > > each flow log files. > > Any update on this? > > Also commented on bug 1519414. > > Do you want to close current? OK for me. > > Do we keep logs for ansible-based "check-for-updates"? Couldn't find them. > If you want to keep it open for that, or anything similar, fine for me as > well. We can't have full Ansible log available for check-for-update, because we are using output filter to return list of packages which can be updated. Full log will be available only after we switch to ansible-runner. To mitigate the issue we are working on passing error using stderr tracked by BZ1658544. As mentioned above closing as current release