Red Hat Bugzilla – Bug 864204
AttributeError: 'YumConf' object has no attribute '_repos_persistdir'
Last modified: 2014-02-05 07:29:54 EST
Description of problem:
enter installation source and selected closest mirror,
maybe i did it too quickly?
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: /usr/bin/python /sbin/anaconda
:The following was filed automatically by anaconda:
:anaconda 18.12 exception report
:Traceback (most recent call first):
: File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 487, in getReposFromConfigFile
: thisrepo.base_persistdir = self.conf._repos_persistdir
: File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 557, in getReposFromConfig
: self.getReposFromConfigFile(repofn, repo_age=thisrepo_age)
: File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 677, in _getRepos
: File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1005, in <lambda>
: repos = property(fget=lambda self: self._getRepos(),
: File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 343, in repos
: return self._yum.repos.repos.keys()
: File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 354, in baseRepo
: if repo_name in self.repos and \
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/software.py", line 123, in ready
: self.payload.baseRepo is not None)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 197, in _updateCompleteness
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 255, in _update_spokes
:AttributeError: 'YumConf' object has no attribute '_repos_persistdir'
Created attachment 623728 [details]
Created attachment 623729 [details]
Created attachment 623730 [details]
Created attachment 623731 [details]
Created attachment 623732 [details]
Created attachment 623733 [details]
Created attachment 623734 [details]
Created attachment 623735 [details]
Created attachment 623736 [details]
Created attachment 623737 [details]
Created attachment 623738 [details]
Created attachment 623739 [details]
Created attachment 623740 [details]
Created attachment 623741 [details]
Discussed at 2012-10-10 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-10/f18beta-blocker-review-3.2012-10-10-16.05.log.txt . We agreed there is not enough information on the circumstances to trigger this, and it looks like no-one else is hitting it (no CCs added by abrt). Reartes, can you reproduce this? Can you say precisely what image you booted (TC2 x86-64 DVD? or what?) Can anyone else reproduce this? I tried booting the DVD image and quickly switching to the remote mirror install source a couple of times and could not reproduce this. We agreed if we don't have more reports or more concrete details by next week, this bug will be rejected as a blocker.
The current iso is Fedora-18-Beta-TC3-x86_64-DVD.iso (previously it was TC2).
I can reproduce it reliably with guests BTRFS-1, BTRFS-2, BTRFS-3,
and something interesting happened with guest FNEXT-DBT1.
With FNEXT-DBT1, some times it did not happen, one time i got a 'stuck' anaconda, one time (rhbz 865173), and also could reproduce this bug-report.
Tried switching video from SPICE/QLX to VNC/Cirrus, but no effect.
Also tried with vesa, no effect.
I also tried on another guest, which does NOT have internet access (private network) and it experienced the same issue.
I also tired a physical host and as expected i could not reproduce it.
Discussed at 2012-10-17 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-17/f18beta-blocker-review-4.2012-10-17-16.00.log.txt . Although Reartes can reproduce this no-one else seems to be able to, and no-one has been added to CC on this report by libreport which would indicate they'd hit it. Since no-one but Reartes seems to be able to hit this, it's tentatively rejected as a blocker. It can be re-proposed if data emerges to indicate this is hitting more testers.
In current anaconda versions, you cannot change INSTALLATION SOURCE until SOFTWARE SELECTION has finished resolving dependencies.
Also you can't enter SOFTWARE selection after INSTALLATION SOURCE has finished setting up the installation source.
Additionally, one cannot just enter INSTALLATION SOURCE intermediately after 'accepting fate', there is a pause for both INSTALLATION SOURCE and SOFTWARE SELECTION.
It looks like the bug (if it still ever exists) cannot be triggered in current anaconda versions.
If what i said is correct, maybe the bug-report can be closed.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora
'version' of '18'.
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 prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 to Fedora 18's end of life.
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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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
Thank you for reporting this bug and we are sorry it could not be fixed.