Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 573492
Summary: | AttributeError: 'NoneType' object has no attribute 'format' | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Miller <cjm> |
Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | alweiner7, cjm, cye, jlaska, jonathan, kiosso, sir.zhangwei, vanmeeuwen+fedora |
Target Milestone: | --- | Keywords: | CommonBugs |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | anaconda_trace_hash:022e0b1f18a8e1684b6889fc34cb2f07ee72eee1b4501a38314eccc13c64ca99 https://fedoraproject.org/wiki/Common_F13_bugs#hdinstall-with-mirrorlist-repo | ||
Fixed In Version: | anaconda-14.12-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-06-07 14:09:45 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
Chris Miller
2010-03-15 00:39:13 UTC
Created attachment 400086 [details]
Attached traceback automatically from anaconda.
Can you please test again with F13 alpha and let me know if this is still a bug there? Thanks. I will happily test anything you like. Please provide instructions how I can deploy F13-alpha anaconda, as I'm not exactly certain how to do this. I suspect I simply need a new initrd.img? Is that right? *** Bug 573673 has been marked as a duplicate of this bug. *** On the console: Running anaconda 12.46, the Fedora system installer - please wait/ 23:02:37 Starting VNC... 23:02:38 The VNC server is now running. 23:02:38 You choose to execute vnc with a password. 23:02:38 Please manually connect your vnc client to 10.1.2.40:1 to begin the install. Traceback (most recent call last): File "/usr/bin/anaconda", line 961, in <module> startSsh() File "/usr/bin/anaconda", line 418, in startSsh os.execv("/sbin/sshd", args) OSError:[Errno 2] No such file or directory 23:02:38 Starting graphical installation. Installation in progress via kickstart monitored with vnc... ... and unhandled exception. 574085 was added. *** Bug 574085 has been marked as a duplicate of this bug. *** Created attachment 400477 [details]
Kickstart config -- package list deleted.
Created attachment 400478 [details]
boot menu
Radek - it looks to me like mirrorFailureCB needs to be updated to handle the possibility that there are multiple kinds of repos involved and that the failure may be coming from a remote HTTP/FTP repo, so it doesn't make any sense to try to eject the media. Chris - I don't think your kickstart file is going to do what you want. You've got the harddrive command as well as two repo commands specifying the base repo. You're therefore likely getting the base packages installed from those remote repos instead of your hard drive. Hi CL, For whatever reason, if I install from JUST the local archive, then I get version conflicts, so I added some remote repos to resolve the version problems. Since I am using a stock F12 DVD as my local, I don't understand why I should be getting version problems. In the interest of full disclosure, I used revisor to construct the package list that I use in ks.cfg, and revisor had the benefit of the most current remote archives and updates, so possibly permitted selections that would have been excluded without such access -- dunno. If I specify "harddrive" and a set of repos, I assumed that the installation would look at the harddrive first and then satisfy any "install for dependancy" requirements from remote repos and finally apply updates that might be available. Am I assuming too much? In over a dozen installation attempts, I have had zero sessions that got past the first package and that seems like an inordinate failure rate for the remote repos. Is there something else happening? Hi CL, Apparently I did not get BOTH initrd.img and install.img updated to F13-Alpha. My apologies for the mis-information. Using all F13-Alpha -- initrd.img, install.img and vmlinuz, I had zero problems using the local harddisk archive of packages. I can believe my results because the welcome banner advertised anaconda 13.32 Modifying the ks.cfg to include the five additional archives, causes an unhandled exception, which you have now identified. If there is anything else I can do to help, please let me know. For example, if you have a test version that you want me to run, please tell me. Thanks, Chris. Hi CL, I don't know if this helps, but apparently when I use --mirrorlist instead of --baseurl with the repo directive, there are no problems. At least, I have gotten past the installation of the first package. I will update you about the ultimate conclusion of this installation. Thanks, Chris. Created attachment 404362 [details]
Attached traceback automatically from anaconda.
(In reply to comment #9) > Radek - it looks to me like mirrorFailureCB needs to be updated to handle the > possibility that there are multiple kinds of repos involved and that the > failure may be coming from a remote HTTP/FTP repo, so it doesn't make any sense > to try to eject the media. I sent a patch taking care of that for review. *** Bug 588485 has been marked as a duplicate of this bug. *** = Steps to reproduce = 1. Boot the netinst.iso of Fedora 13 Final TC1, boot with "askmethod" 2. Choose a pre-existing partition containing a DVD ISO and images/install.img file. 3. Proceed with installation 4. At reposetup screen, attempt to add an http package repository (per instructions at https://fedoraproject.org/wiki/QA:Testcase_Additional_Http_Repository) (In reply to comment #16) > = Steps to reproduce = > > 1. Boot the netinst.iso of Fedora 13 Final TC1, boot with "askmethod" > 2. Choose a pre-existing partition containing a DVD ISO and images/install.img > file. > 3. Proceed with installation > 4. At reposetup screen, attempt to add an http package repository (per > instructions at > https://fedoraproject.org/wiki/QA:Testcase_Additional_Http_Repository) For step#4 ... add a mirrorlist URL, but do *not* select "[ ] Is a mirrorlist". This is easy to document and workaround. Created attachment 417365 [details]
Attached traceback automatically from anaconda.
*** Bug 597011 has been marked as a duplicate of this bug. *** *** Bug 597008 has been marked as a duplicate of this bug. *** Created attachment 417984 [details]
Attached traceback automatically from anaconda.
*** Bug 597682 has been marked as a duplicate of this bug. *** Chris Miller, can you upload the kickstart file you are using when encountering this failure? Thanks! Added link to proposed Common_F13_Bugs documentation describing this issue. https://fedoraproject.org/wiki/Common_F13_bugs#hdinstall-with-mirrorlist-repo Created attachment 419431 [details]
Requested ks.cfg
Requested ks.cfg
Please note that the configuration as uploaded is the final and successful version. You will notice that I have repro's commented out. On the day the bug reports were filed, I was using either the mirror list, or fedoraproject directly. It was only after I commented them out and used anl.gov that I succeeded. You should be able to tell from the traceback what what was [un]commented at the time of each report.
Chris.
Created attachment 424001 [details]
Attached traceback automatically from anaconda.
This should be fixed in anaconda-14.12-1. The traceback should be gone (It happened e.g. when hd: or cdrom: repo and additional non-media repo was used, and download of package from non-media repo failed). *** Bug 627077 has been marked as a duplicate of this bug. *** Created attachment 455491 [details]
Attached traceback automatically from anaconda.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |