Bug 1877847
Summary: | [RFE] Requesting to include /usr/sbin/yum-complete-transaction in RHEL 8 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Rajesh Dulhani <rdulhani> |
Component: | yum | Assignee: | Lukáš Hrázký <lhrazky> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | swm-qe |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.2 | CC: | james.antill, jcastran, kwalker, lhrazky, mharbi, packaging-team-maint, pkratoch, robert.freeman |
Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
Target Release: | 8.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-04-26 06:35:17 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: |
Description
Rajesh Dulhani
2020-09-10 15:03:48 UTC
Our issue with the /usr/sbin/yum-complete-transaction command being missing, has to do with our thousands of lines of satellite automation patching scripts. Which is based on the output of this command "yum-complete-transaction" , several different supporting automation scripts will trigger. I need to know if this is going to be added back or not ? Could someone please let me know, if it is going to be added back, please give me an estimate of time. Thank you Rob Freeman 918.406.9534 The problem with interrupted transaction can be resolved by `yum remove --duplicates`. It removes duplicates from the system and reinstall potential broken packages. In the second step I can recommend to try to redo the broken transaction using `yum history redo <transaction id>`. The transaction ID can be taken from output of `yum history` which lists all transactions. Hello Rob, Sorry about the late response. I think we'll need more details about this. We are not planning to add support for the old format that yum-complete-transaction has used. Do you really have thousands of lines specifically working with this file format? What are you doing with it? What are the reasons for that? We should figure out a new solution to what you need, the old format was not good and it doesn't make sense from technical standpoint to support it. We have a new JSON format for storing transactions, which is used by the `dnf history store` and `dnf history replay` commands. The store command works with transactions from the transaction history. We can add support for storing unfinished transactions, though it will likely not be automatically e.g. after pressing 'n' when asked whether to perform a transaction. Instead, we'd add a switch, e.g. `dnf install foo --store-transaction` which would (instead of doing the install) just store the file. The syntax of that is up for discussion. It looks like that provided information about existing functionality resolved the issue because there is no update from the reporter for nearly one year. Therefore I consider the issue as resolved. Please feel free to reopen the bug with additional information including user cases. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |