Bug 2212262
| Summary: | dnf-automatic returns "success" ( zero exit status return ) even if the called dnf command returns error | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Jan Kolarik <jkolarik> |
| Component: | dnf | Assignee: | Jan Kolarik <jkolarik> |
| Status: | CLOSED ERRATA | QA Contact: | Eva Mrakova <emrakova> |
| Severity: | medium | Docs Contact: | Mariya Pershina <mpershin> |
| Priority: | medium | ||
| Version: | 9.3 | CC: | brian, james.antill, jkolarik, jrohel, mbanas, mpershin, pkratoch, swm-qe, vbhope |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | dnf-4.14.0-8.el9 | Doc Type: | Bug Fix |
| Doc Text: |
.The `dnf-automatic` command now correctly reports the exit status of transactions
Previously, the `dnf-automatic` command returned a successful exit code of a transaction even if some actions during this transaction were not successfully completed. This could cause a security risk on machines that use `dnf-automatic` for automatic deployment of errata. With this update, the issue has been fixed and `dnf-automatic` now reports every problem with packages during the transaction.
|
Story Points: | --- |
| Clone Of: | 2170093 | Environment: | |
| Last Closed: | 2023-11-07 08:54:41 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2170093 | ||
| Bug Blocks: | |||
|
Description
Jan Kolarik
2023-06-05 06:44:04 UTC
Originally fixed in the RHEL 8 bug: https://bugzilla.redhat.com/show_bug.cgi?id=2170093. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (dnf bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:6645 |