Bug 782135

Summary: unknown error 695609 encountered while manipulating package kernel-3.1.9-1.fc16.i686
Product: [Fedora] Fedora Reporter: David Juran <djuran>
Component: yumAssignee: Seth Vidal <skvidal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: ffesti, james.antill, maxamillion, pmatilai, tla, zpavlas
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: 2012-01-16 20:23:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
yum output none

Description David Juran 2012-01-16 16:07:56 UTC
Created attachment 555545 [details]
yum output

Description of problem:
Tried to run yum upgrade but failed with the not-too-descriptive message

Transaction Check Error:
  unknown error 695609 encountered while manipulating package kernel-3.1.9-1.fc16.i686


Version-Release number of selected component (if applicable):
yum-3.4.3-7.fc16


Additional info:

Attaching full output of yum -v -d 10 upgrade

Comment 1 Zdeněk Pavlas 2012-01-16 16:22:12 UTC
The above mentioned error is not present in the attached yum output.  Could you double check, please?  Also, could this be a dup of bug 766260? (no space in /boot).

Comment 2 David Juran 2012-01-16 20:23:27 UTC
Hmmm, used yum |tee to capture the output, guess the actual error message came on std err )-:
But yes, Bz 766260 sounds like the right one. I tried to run only "yum upgrade kernel" and then I got a clear message that I was short on space in /boot. After cleaning up /boot, I could run the full transaction.
Closing the bug as a dup, thanks for the pointer.

*** This bug has been marked as a duplicate of bug 766360 ***

Comment 3 David Juran 2012-01-16 20:24:06 UTC

*** This bug has been marked as a duplicate of bug 766260 ***