| Summary: | yum complete transaction failure | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dave Jones <davej> |
| Component: | yum | Assignee: | Packaging Maintenance Team <packaging-team-maint> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | fche, ffesti, herrold, james.antill, jzeleny, maxamillion, pfrields, pmatilai, tla, tmraz |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-17 13:48:31 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
package-cleanup --dupes shows sendmail-8.14.5-3.fc16.x86_64 sendmail-8.14.5-2.fc16.x86_64 openssh-server-5.8p2-12.fc16.1.x86_64 openssh-server-5.8p2-14.fc16.1.x86_64 openssh-5.8p2-12.fc16.1.x86_64 openssh-5.8p2-14.fc16.1.x86_64 glibc-2.14.90-2.x86_64 glibc-2.14.90-1.x86_64 glibc-debuginfo-common-2.14.90-2.x86_64 glibc-debuginfo-common-2.14.90-1.x86_64 gawk-4.0.0-1.fc16.x86_64 gawk-3.1.8-3.fc15.x86_64 less-444-1.fc16.x86_64 less-443-1.fc16.x86_64 libusb1-1.0.9-0.1.git212ca37c.fc16.x86_64 libusb1-1.0.8-7.fc15.x86_64 libpng-1.2.44-3.fc15.x86_64 libpng-1.2.46-1.fc16.x86_64 glibc-common-2.14.90-2.x86_64 glibc-common-2.14.90-1.x86_64 I'm just going to rpm -e --justdb the old versions and move on unless there's some specific debugging you want me to do.. package-cleanup --cleandupes ... should be fine. As should using "yum remove", but using rpm -e will only upset yum a little bit (and it should be already unhappy due to the aborted transaction -- so w/e :). any idea why it thought the transaction size changed? > any idea why it thought the transaction size changed?
Yes, it was due to this bit:
--> Processing Dependency: openssh = 5.8p2-12.fc16.1 for package:
openssh-server-5.8p2-12.fc16.1.x86_64
[...]
--> Running transaction check
---> Package openssh-server.x86_64 0:5.8p2-12.fc16.1 will be erased
...likely meaning that yum was told that "openssh-server.x86_64 0:5.8p2-12.fc16.1" was erased, but it didn't really. So y-c-t won't try to re-erase, but that means there are deps. for erases ... and so it then goes into conservative mode and just stops. In theory it could see this and DTRT ... knowing that openssh-server.x86_64 0:5.8p2-12.fc16.1 was part of the transaction, so deleting it is fine.
However in general we've not really worked on y-c-m much, for two reasons:
1. It's just much better when transactions aren't aborted.
2. It's much better when the transactions which are aborted are smaller (and then also the simplest logic tends to just work more often).
3. You can now just re-run the entire transaction with: yum history redo/undo ... which tends to work better anyway (also due to changes in the other parts of yum so it deals better with the situations where the rpmdb is in a weird state).
This happened to me a few days ago, and again today, while installing 5.8p2-15.fc16.1. To work around it, I ended up doing this from the console: yum -y remove openssh-server && yum -y install openssh-server && service ssh restart Oddly, "yum reinstall openssh-server" did *not* work. The openssh-5.8p2-15.fc16.1 is broken due to bad rpm in the buildroot. Also, do you have pam_systemd in /etc/pam.d/password-auth? If not then this is the cause of having the user ssh session killed when the sshd is restarted by systemd. As without pam_systemd in the session the sshd process that takes care of the session runs in the same cgroup as the main sshd daemon and gets killed with it by systemd. The pam_systemd should be automatically put into the PAM configuration by authconfig. 'authconfig --updateall' should help if it is not there. So,m just to confirm ... systemd is force killing everything in the cgroup, including yum? Yes, I suppose so. This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. |
I was doing a yum update, which included updating openssh-server. As part of its cleanup, it decided to kill my ssh connection to the machine being updated. Running Transaction Updating : glibc-2.14.90-2.x86_64 1/34 Updating : glibc-common-2.14.90-2.x86_64 2/34 Updating : openssh-5.8p2-14.fc16.1.x86_64 3/34 Updating : sendmail-8.14.5-3.fc16.x86_64 4/34 Updating : glibc-headers-2.14.90-2.x86_64 5/34 Updating : gawk-4.0.0-1.fc16.x86_64 6/34 Updating : selinux-policy-3.10.0-4.fc16.noarch 7/34 Updating : glibc-debuginfo-common-2.14.90-2.x86_64 8/34 Updating : glibc-debuginfo-2.14.90-2.x86_64 9/34 Updating : selinux-policy-targeted-3.10.0-4.fc16.noarch 10/34 Updating : glibc-devel-2.14.90-2.x86_64 11/34 Updating : sendmail-cf-8.14.5-3.fc16.noarch 12/34 Updating : openssh-server-5.8p2-14.fc16.1.x86_64 13/34 Updating : openssh-clients-5.8p2-14.fc16.1.x86_64 14/34 Updating : 2:libpng-1.2.46-1.fc16.x86_64 15/34 Updating : libusb1-1.0.9-0.1.git212ca37c.fc16.x86_64 16/34 Updating : less-444-1.fc16.x86_64 17/34 Cleanup : glibc-devel-2.14.90-1.x86_64 18/34 Cleanup : glibc-headers-2.14.90-1.x86_64 19/34 Cleanup : selinux-policy-targeted-3.10.0-3.fc16.noarch 20/34 Cleanup : selinux-policy-3.10.0-3.fc16.noarch 21/34 Cleanup : sendmail-cf-8.14.5-2.fc16.noarch 22/34 Cleanup : glibc-debuginfo-2.14.90-1.x86_64 23/34 Cleanup : openssh-clients-5.8p2-12.fc16.1.x86_64 24/34 Cleanup : openssh-server-5.8p2-12.fc16.1.x86_64 25/34 Shared connection to firewall closed. I ssh'd back in, and ran yum-complete-transaction and got .. There are 1 outstanding transactions to complete. Finishing the most recent one The remaining transaction had 9 elements left to run --> Running transaction check ---> Package gawk.x86_64 0:3.1.8-3.fc15 will be erased ---> Package glibc.x86_64 0:2.14.90-1 will be erased ---> Package glibc-common.x86_64 0:2.14.90-1 will be erased ---> Package glibc-debuginfo-common.x86_64 0:2.14.90-1 will be erased ---> Package less.x86_64 0:443-1.fc16 will be erased ---> Package libpng.x86_64 2:1.2.44-3.fc15 will be erased ---> Package libusb1.x86_64 0:1.0.8-7.fc15 will be erased ---> Package openssh.x86_64 0:5.8p2-12.fc16.1 will be erased --> Processing Dependency: openssh = 5.8p2-12.fc16.1 for package: openssh-server-5.8p2-12.fc16.1.x86_64 ---> Package sendmail.x86_64 0:8.14.5-2.fc16 will be erased --> Running transaction check ---> Package openssh-server.x86_64 0:5.8p2-12.fc16.1 will be erased --> Finished Dependency Resolution Dependencies Resolved Transaction size changed - this means we are not doing the same transaction as we were before. Aborting and disabling this transaction. You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest Transaction files renamed to: /var/lib/yum/transaction-all.2011-07-15.18:24.55.disabled /var/lib/yum/transaction-done.2011-07-15.18:24.55.disabled