Bug 505098
Summary: | no repomd.xml file during install | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Roger Mach <bigmach> | ||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | rawhide | CC: | anaconda-maint-list, ffesti, james.antill, lcm, pmatilai, rmaximo, tim.lauridsen, vanmeeuwen+fedora | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | anaconda_trace_hash:76f1673c3d05103e09d422310a570cc7718d76e72211ee5fd94e18f767ed0586 | ||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-09-04 14:30:58 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
Roger Mach
2009-06-10 16:14:37 UTC
Created attachment 347252 [details]
Attached traceback automatically from anaconda.
I was mistaken when I originally described this error as being seen during a uefi installation. This was a legacy mode installation from DVD to a disk with a GPT label, which is probably an unusual combination but as far as I know should be supported. This problem has now also occurred during a uefi installation to a disk with a GPT disklabel. I have no idea at all. Can you make this happen if you use rawhide/f12alpha? Created attachment 359737 [details]
anaconda execption report from fedora 12 alpha installation
As requested, I tried installing Fedora 12 Alpha on the same machine where I saw the original issue. I did not get the same error but did hit a different anaconda failure as detailed in the attached exception report.
reassigning this error over to anaconda. Since the original issue appears to be fixed in F12 Alpha, I'm going to close this bug out. We have plenty of reports of the second issue described in comment #5, which I believe are assigned to python-pyblock. |