Bug 322431 - Transaction test fails
Transaction test fails
Product: Fedora
Classification: Fedora
Component: yumex (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Tim Lauridsen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-10-07 15:52 EDT by Tim McConnell
Modified: 2007-12-06 10:05 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-12-06 10:05:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim McConnell 2007-10-07 15:52:52 EDT
Description of problem: Yumex hangs while in transaction test part of updating 

Version-Release number of selected component (if applicable):

How reproducible: Attempt to install/upgrade computer via Yumex 

Steps to Reproduce:
1.Launch Yumex 
2. Choose multiple packages to install/ update, add to queue, then click okay
when prompted.
3. Run until Yumex hangs
Actual results: 11:14:02 : --> Finished Dependency Resolution
11:14:17 : Downloading Packages:
13:30:57 : Checking GPG Signatures:
13:30:58 : Running Transaction Test
Traceback (most recent call last):
  File "/usr/share/yumex/yumex.py", line 173, in on_queueProcess_clicked
    rc = self.processPackageQueue(self.queue.packages)
  File "/usr/share/yumex/yumex.py", line 622, in processPackageQueue
    quit = self.processTransaction()
  File "/usr/share/yumex/yumex.py", line 660, in processTransaction
  File "/usr/share/yumex/yumapi.py", line 338, in _doTransactionTest
    self.populateTs( keepold=0 ) # sigh
  File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 223, in populateTs
    self.ts.addInstall(hdr, (hdr, rpmfile), txmbr.ts_state)
_rpm.error: adding package to transaction failed

Expected results: No failures

Additional info:
Comment 1 Tim McConnell 2007-12-06 10:05:06 EST
error hasn't reproduced itself for a while must of been fixed 

Note You need to log in before you can comment on or make changes to this bug.