Bug 250914
Summary: | installation of x86_64 fails | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rudolf Usselmann <rudi> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | jon.stanley, triage |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-06-17 02:06:06 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: |
Description
Rudolf Usselmann
2007-08-05 06:39:59 UTC
FYI I just installed x86_64 F7 release today, although not from DVD (from a install tree that I copied from DVD and burned boot.iso instead and did a HTTP install). No errors were encountered during this. I'll attempt a VMWare install from iso tommorow, but I'm inclined to believe that it will work - the fact that an HTTP install using a tree created using that media seems to prove it. Let us know the md5sum of your media (the original iso file), please. As requested here is the md5sum: %md5sum F-7-x86_64-DVD.iso dd60e7a7f7895cdb2432a4b82f7a5bb1 F-7-x86_64-DVD.iso I do believe the media is good. The "Media Check" does pass as well. And as I said the packages that "appear to be missing" are there and can be opened on another system. I also double checked that the sha1sum matches as to what is in the server: %sha1sum F-7-x86_64-DVD.iso 7cdbd9e1bed9cc9ce2c7970abeaca4da08d2994a F-7-x86_64-DVD.iso I have been comparing how anaconda runs with the 32 bit and 64 bit releases. Apparently the cdrom argument I was questioning above is ok. It looks like the 32 bit install works the same way. I have been monitoring the mounted devices through each step of the installation. It looks like /tmp/cdrom is properly mounted on /mnt/source all the way until it starts the actual install. Basically the last time I have to click a button, when it gives you the window saying "Starting installation process the the last time I see /tmp/cdrom being mounted. After that, it magically disappears, but instead I see /mnt/sysimage being mounted. This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'. 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 7'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 7 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. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Have you encountered the same problem in Fedora 9? Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. Fedora 7 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. Thank you for reporting this bug and we are sorry it could not be fixed. |