Red Hat Bugzilla – Bug 859855
AttributeError: 'NoneType' object has no attribute 'name'
Last modified: 2014-02-05 07:17:15 EST
Version-Release number of selected component:
libreport version: 2.0.12
cmdline: /usr/bin/python /sbin/anaconda
Created attachment 616405 [details]
Created attachment 616406 [details]
Created attachment 616407 [details]
Created attachment 616408 [details]
Created attachment 616409 [details]
Created attachment 616410 [details]
Created attachment 616411 [details]
Created attachment 616412 [details]
Created attachment 616413 [details]
Created attachment 616414 [details]
Created attachment 616415 [details]
Created attachment 616416 [details]
Created attachment 616417 [details]
Created attachment 616418 [details]
Created attachment 616419 [details]
Created attachment 616420 [details]
Encountered while I have tried to upgrade F17 to F18 using preupgrade tool. It was clean install, fully updated.
Proposing as F18 beta blockerbug per criterion: "The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation (from any official install medium) of the previous stable Fedora release, either via preupgrade or by booting to the installer manually. The upgraded system must meet all release criteria"
Always reproducible under the same conditions.
Given that we're moving upgrade stuff out of anaconda, there's not really anything for us to fix here. Just as an extra point, though, whatever's writing out your kickstart file is doing it wrong:
# ks.cfg generated by preupgrade
bootloader --upgrade --location=none
OK, I was using preupgrade, so I think that it was preupgrade what wrote my kickstart file. Changing component to "preupgrade".
As preupgrade is being deprecated for F18 and fedup won't be using kickstarts or anaconda, it doesn't make any sense to have this sitting in the proposed blocker list, really.
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.