Bug 1090503

Summary: [abrt] yum: drpm.py:259:_wait:AssertionError
Product: [Fedora] Fedora Reporter: jonathan <jonaternet>
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: admiller, chsnow123, packaging-team-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9f929a29049b967368fd5cae84a0e70e9206b7fd
Whiteboard: abrt_hash:0bdcd45d39dc82a2b23950b63a0f21d6b6cc2b0e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:15:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description jonathan 2014-04-23 13:33:22 UTC
Description of problem:
di d a yum update. it froze at some point, sso I did ctrl-c then yum update again :

Install    4 Packages (+1 Dependent package)
Upgrade  237 Packages
Remove     3 Packages

Total size: 753 M
Total download size: 362 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for openclient-testing
Traceback (most recent call last):
  File "/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 355, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 261, in main
    return_code = base.doTransaction()
  File "/usr/share/yum-cli/cli.py", line 670, in doTransaction
    problems = self.downloadPkgs(downloadpkgs, callback_total=self.download_callback_total_cb) 
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 2434, in downloadPkgs
    presto.rebuild(po)
  File "/usr/lib/python2.7/site-packages/yum/drpm.py", line 289, in rebuild
    self.dequeue_max()
  File "/usr/lib/python2.7/site-packages/yum/drpm.py", line 325, in dequeue_max
    if not self.dequeue(block=False):
  File "/usr/lib/python2.7/site-packages/yum/drpm.py", line 331, in dequeue
    self._wait()
  File "/usr/lib/python2.7/site-packages/yum/drpm.py", line 259, in _wait
    assert pid in self.jobs
AssertionError

Version-Release number of selected component:
yum-3.4.3-137.fc20

Additional info:
reporter:       libreport-2.2.1
cmdline:        /usr/bin/python /bin/yum update
executable:     /bin/yum
kernel:         3.13.9-200.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            0

Truncated backtrace:
drpm.py:259:_wait:AssertionError

Traceback (most recent call last):
  File "/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 355, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 261, in main
    return_code = base.doTransaction()
  File "/usr/share/yum-cli/cli.py", line 670, in doTransaction
    problems = self.downloadPkgs(downloadpkgs, callback_total=self.download_callback_total_cb)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 2434, in downloadPkgs
    presto.rebuild(po)
  File "/usr/lib/python2.7/site-packages/yum/drpm.py", line 289, in rebuild
    self.dequeue_max()
  File "/usr/lib/python2.7/site-packages/yum/drpm.py", line 325, in dequeue_max
    if not self.dequeue(block=False):
  File "/usr/lib/python2.7/site-packages/yum/drpm.py", line 331, in dequeue
    self._wait()
  File "/usr/lib/python2.7/site-packages/yum/drpm.py", line 259, in _wait
    assert pid in self.jobs
AssertionError

Local variables in innermost frame:
self: <yum.drpm.DeltaInfo instance at 0x2dc6170>
code: 0
pid: 4069
block: False
num: 0

Comment 1 jonathan 2014-04-23 13:33:26 UTC
Created attachment 888911 [details]
File: backtrace

Comment 2 jonathan 2014-04-23 13:33:28 UTC
Created attachment 888912 [details]
File: environ

Comment 3 chsnow123@gmail.com 2015-03-08 19:44:37 UTC
Is there a workaround for this issue?

Comment 4 chsnow123@gmail.com 2015-03-09 15:41:42 UTC
(In reply to chsnow123 from comment #3)
> Is there a workaround for this issue?

http://unix.stackexchange.com/questions/188936/fedora-20-assertionerror-on-yum-update-yum-install

Comment 5 Fedora End Of Life 2015-05-29 11:39:14 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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.

Comment 6 Fedora End Of Life 2015-06-29 20:15:04 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.