Bug 679466

Summary: KeyError: <pyanaconda.yuminstall.AnacondaYumRepo object at 0x7f409f7333d0>
Product: [Fedora] Fedora Reporter: John Poelstra <poelstra>
Component: anacondaAssignee: Radek Vykydal <rvykydal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: alexandre.dutriaux, aphixe, awilliam, clydekunkel7734, jlaska, jonathan, linux, neoh.ys, pourtouteslesclasses, reb, rhe, richardfearn, rvykydal, shiliu, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:ba9e5b20a09115c7f6e5b9507854dcf315540775c1c876b71d553f37812615e5 RejectedBlocker
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-23 12:12:23 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
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda. none

Description John Poelstra 2011-02-22 16:16:26 UTC
The following was filed automatically by anaconda:
anaconda 15.20.1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/yum/sqlitesack.py", line 233, in _sql_MD
    cache = getattr(self.sack, MD + 'db')[self.repo]
  File "/usr/lib/python2.7/site-packages/yum/sqlitesack.py", line 46, in newFunc
    return func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/yum/sqlitesack.py", line 388, in returnPrco
    cur = self._sql_MD('primary', sql, (self.pkgKey,))
  File "/usr/lib/python2.7/site-packages/yum/packageSack.py", line 890, in _delPackageFromIndex
    for (n, fl, (e,v,r)) in obj.returnPrco('conflicts'):
  File "/usr/lib/python2.7/site-packages/yum/packageSack.py", line 904, in delPackage
    self._delPackageFromIndex(obj)
  File "/usr/lib/python2.7/site-packages/yum/transactioninfo.py", line 302, in remove
    self._inSack.delPackage(txmbr.po)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/yuminstall.py", line 1373, in resetPackageSelections
    self.ayum.tsInfo.remove(txmbr.pkgtup)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/backend.py", line 216, in doBasePackageSelect
    anaconda.backend.resetPackageSelections()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 211, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 130, in gotoNext
    self.moveStep()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1257, in nextClicked
    self.anaconda.dispatch.gotoNext()
KeyError: <pyanaconda.yuminstall.AnacondaYumRepo object at 0x7f409f7333d0>

Comment 1 John Poelstra 2011-02-22 16:16:30 UTC
Created attachment 480168 [details]
Attached traceback automatically from anaconda.

Comment 2 John Poelstra 2011-02-22 16:28:43 UTC
This happened install RC1 from DVD.

Selected the x86_64 updates testing as an additional repo to install from.  Received an error message about unresolved deps so I went backwards and unchecked the updates testing repo and clicked forward. Then I got the traceback below.

Comment 3 James Laska 2011-02-22 16:46:02 UTC
(In reply to comment #2)
> This happened install RC1 from DVD.
> 
> Selected the x86_64 updates testing as an additional repo to install from. 
> Received an error message about unresolved deps so I went backwards and
> unchecked the updates testing repo and clicked forward. Then I got the
> traceback below.

You know I have to ask :)  Does this happen if you aren't selecting and unselecting repos?  Does the default repo selection produce this error?  We have positive test results of testing while adding repos, I suspect this error *only* happens if you hit a 'unresolved dep' dialog, and go back.

If the default path does not result in this traceback, I'm in favor of resolving this post-Alpha.  If the default path results in this failure, definitely an Alpha blocker.

Comment 4 Radek Vykydal 2011-02-22 16:48:18 UTC
Seems very much like bug #622376.

Comment 5 James Laska 2011-02-22 16:56:04 UTC
(In reply to comment #4)
> Seems very much like bug #622376.

@Radek - Ah yes, the reproducer John describes does seem to match that issue.

Do you need any debug feedback regarding the updates.img images you posted in bug#622376?

Comment 6 Chris Lumens 2011-02-22 17:02:27 UTC
Looks like a dupe to me too.

Comment 7 Radek Vykydal 2011-02-22 17:27:03 UTC
I have a on-liner patch (https://bugzilla.redhat.com/show_bug.cgi?id=622376#c5
- a bit of hack) that resolves bug #622376. It was tested by myself and a
reporter and I believe it would solve this one too, here is updates.img for
anaconda 15.20-1:
http://rvykydal.fedorapeople.org/updates.679466.img

If the bz gets escalated I'll repost the patch on a-d-l. If not, I'd wait for
yum backend clean-up/rewrite
(http://fedoraproject.org/wiki/Anaconda/Features/YuminstallCleanup). I tried to
clean things up partly in the name of the #622376, but didn't get feedback on
a-d-l.

Comment 8 John Poelstra 2011-02-22 17:44:21 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > This happened install RC1 from DVD.
> > 
> > Selected the x86_64 updates testing as an additional repo to install from. 
> > Received an error message about unresolved deps so I went backwards and
> > unchecked the updates testing repo and clicked forward. Then I got the
> > traceback below.
> 
> You know I have to ask :)  Does this happen if you aren't selecting and
> unselecting repos?  Does the default repo selection produce this error?  We
> have positive test results of testing while adding repos, I suspect this error
> *only* happens if you hit a 'unresolved dep' dialog, and go back.
> 
> If the default path does not result in this traceback, I'm in favor of
> resolving this post-Alpha.  If the default path results in this failure,
> definitely an Alpha blocker.

Yes, following the default path (not adding any addional repos) it installed fine.

Comment 9 Adam Williamson 2011-02-22 19:02:14 UTC
Discussed with jlaska out-of-meeting-cycle. Our call for this is not an Alpha blocker: to hit it you have to perform actions which don't come under any of the Alpha criteria.

Comment 10 He Rui 2011-02-24 08:18:36 UTC
Created attachment 480682 [details]
Attached traceback automatically from anaconda.

Comment 11 He Rui 2011-02-24 08:25:18 UTC
(In reply to comment #2)
> This happened install RC1 from DVD.
> 
> Selected the x86_64 updates testing as an additional repo to install from. 
> Received an error message about unresolved deps so I went backwards and
> unchecked the updates testing repo and clicked forward. Then I got the
> traceback below.

I had similar steps. Generally, when receive an warning message such as upresolved deps, or low disk space and click 'back' to select package repo again, this issue would happen after clicking next.

Comment 12 Andrew Jamison 2011-03-11 01:54:01 UTC
Created attachment 483624 [details]
Attached traceback automatically from anaconda.

Comment 13 Clyde E. Kunkel 2011-03-30 18:36:07 UTC
Created attachment 488863 [details]
Attached traceback automatically from anaconda.

Comment 14 efreeti 2011-04-16 10:44:06 UTC
Created attachment 492560 [details]
Attached traceback automatically from anaconda.

Comment 15 Al 2011-04-25 05:34:33 UTC
Created attachment 494616 [details]
Attached traceback automatically from anaconda.

Comment 16 efreeti 2011-04-26 06:22:09 UTC
Created attachment 494818 [details]
Attached traceback automatically from anaconda.

Comment 17 Clyde E. Kunkel 2011-04-30 18:52:16 UTC
Created attachment 495989 [details]
Attached traceback automatically from anaconda.

Comment 18 Jason 2011-05-05 18:40:57 UTC
Created attachment 497187 [details]
Attached traceback automatically from anaconda.

Comment 19 Alexandre Dutriaux 2011-05-13 17:53:31 UTC
Created attachment 498830 [details]
Attached traceback automatically from anaconda.

Comment 20 Jason 2011-05-14 02:24:38 UTC
Created attachment 498887 [details]
Attached traceback automatically from anaconda.

Comment 21 Reb 2011-05-18 19:36:04 UTC
Created attachment 499680 [details]
Attached traceback automatically from anaconda.

Comment 22 Alan Liu 2011-06-20 03:41:21 UTC
Created attachment 505526 [details]
Attached traceback automatically from anaconda.

Comment 23 Radek Vykydal 2011-06-23 12:12:23 UTC

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

Comment 24 Richard Fearn 2011-08-13 11:34:09 UTC
Created attachment 518145 [details]
Attached traceback automatically from anaconda.