Back to bug 2170093
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-02-15 15:59:01 UTC | Pool ID | sst_cs_software_management_rhel_8 | |
| Vaibhav Bhope | 2023-02-15 15:59:59 UTC | Summary | dnf-automatic returns "success" even if the called dnf command returns error | dnf-automatic returns "success" ( zero exit status return ) even if the called dnf command returns error |
| Vaibhav Bhope | 2023-02-15 16:00:23 UTC | Priority | unspecified | medium |
| Red Hat One Jira (issues.redhat.com) | 2023-02-15 16:02:49 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-148771 | |
| Pavla Kratochvilova | 2023-02-20 13:41:40 UTC | CC | pkratoch | |
| Keywords | Triaged | |||
| Martin Banas | 2023-03-21 06:53:03 UTC | CC | mbanas | |
| Jan Kolarik | 2023-03-23 14:28:55 UTC | CC | jkolarik | |
| Assignee | packaging-team-maint | jkolarik | ||
| Brian J. Murrell | 2023-04-03 13:32:47 UTC | CC | brian | |
| Jan Kolarik | 2023-04-04 06:22:12 UTC | Link ID | Github rpm-software-management/dnf/issues/1918 | |
| Jan Kolarik | 2023-04-19 07:05:33 UTC | Link ID | Red Hat Bugzilla 1341086 | |
| Status | NEW | ASSIGNED | ||
| Jan Kolarik | 2023-04-20 10:17:17 UTC | Status | ASSIGNED | POST |
| Jan Kolarik | 2023-04-23 05:38:46 UTC | Status | POST | ASSIGNED |
| Jan Kolarik | 2023-05-02 07:44:33 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Doc Text | Cause: dnf-automatic returns success exit code even if one of the items during the transaction was not successfully completed Consequence: dnf-automatic incorrectly reports the status of the overall transaction which can be a security risk on machines using it for automatic deployment of erratas Fix: calculating the overall exit status is fixed to report any problem with packages during the transaction Result: exit status should reflect any problem with packages during the transaction and is matching the behavior with the dnf command |
|||
| Mariya Pershina | 2023-05-16 14:05:14 UTC | Docs Contact | mpershin | |
| CC | mpershin | |||
| Jan Kolarik | 2023-05-17 10:27:15 UTC | Status | ASSIGNED | POST |
| Jan Kolarik | 2023-06-05 06:44:04 UTC | Fixed In Version | dnf-4.7.0-18.el8 | |
| Blocks | 2212262 | |||
| Nicola Sella | 2023-06-07 08:59:01 UTC | CC | nsella | |
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2023-06-13 12:45:56 UTC | Status | MODIFIED | ON_QA |
| Martin Banas | 2023-06-14 08:19:21 UTC | Status | ON_QA | VERIFIED |
| Mariya Pershina | 2023-08-15 08:31:01 UTC | Doc Text | Cause: dnf-automatic returns success exit code even if one of the items during the transaction was not successfully completed Consequence: dnf-automatic incorrectly reports the status of the overall transaction which can be a security risk on machines using it for automatic deployment of erratas Fix: calculating the overall exit status is fixed to report any problem with packages during the transaction Result: exit status should reflect any problem with packages during the transaction and is matching the behavior with the dnf command | .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. |
Back to bug 2170093