Hide Forgot
Description of problem: In anaconda, probably during the installation of the package lvm2, the message "Running in chroot, ignoring request." is written to the standard output. It happens during the call of the method dnf.Base.do_transaction. Other messages are processed in our subclass of dnf.callback.TransactionProgress, logs are in our logs, but I am not able to prevent that one message from appearing on the standard output. Version-Release number of selected component (if applicable): python3-dnf-1.1.10-3 How reproducible: Every time. Steps to Reproduce: I can provide the steps for anaconda, if necessary. Actual results: "Running in chroot, ignoring request." in the standard output. Expected results: No such message in the standard output, unless it is processed that way in a subclass of dnf.callback.TransactionProgress.
"Running in chroot, ignoring request." is a systemd message and it's triggered by systemctl used in lvm2 postinstall scripts.
Looks like RPM just prints this into stdout, so there is no way to get such messages from RPM's callbacks.
Eh. Rpm prints no such thing. See comment #1, maybe lvm2 needs a redirect to /dev/null someplace?
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
*** This bug has been marked as a duplicate of bug 1552971 ***