Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionErinn Looney-Triggs
2016-10-06 17:26:38 UTC
Description of problem:
If the satellite server goes down in the middle of a host attempting to update packages, the host will error out and leave a number of incomplete transactions in the yum log. This is less than ideal.
Version-Release number of selected component (if applicable):
katello-agent-2.5.0-5.el7sat.noarch
How reproducible:
Run a bunch of package updates on a system via satellite, in my case I had around 200, reboot satellite at some point, the client will fail with incomplete transactions.
If the agent ran yum-complete-transaction upon startup or at a specified interval, would that solve this?
Comment 2Erinn Looney-Triggs
2016-10-10 16:53:47 UTC
I would say, that would bandaid the problem, probably the better fix is for that agent to pull in all transactions and execute them in bulk, much like yum does itself. But I am not sure of the agent internals and how all of this goes down.
But yes, running yum-complete-transaction would help with the issue, it would probably need to be executed on a semi regular basis, not just when the agent starts.
Comment 4Zach Huntington-Meath
2017-01-10 15:54:18 UTC
This issue is probably a result of updating katello-agent in a mass update. Going to mark as a duplicate of 1291960.
*** This bug has been marked as a duplicate of bug 1291960 ***
Comment 5Erinn Looney-Triggs
2017-01-10 17:03:10 UTC
Umm, no, not if I am understanding this correctly, the one has nothing to do with the other. The packages aren't double installed, though that was an issue too, the transactions simply were not completed if the satellite connection was lost.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.