Bug 948713
Summary: | RHEL6.3 DVD: Unable to read group information from repositories. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Salim Badakhchani <salimb> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED NOTABUG | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3 | CC: | harald |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-04-11 13:39:06 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Salim Badakhchani
2013-04-05 07:58:09 UTC
Oh, this sounds like a completely different error: Unable to read group information from repositories. This is a problem with the generation of your install tree. Apparently anaconda was already started, so there should be no problem with the virtual CDROM. Btw, I wasn't asking for the commands to be run on the host machine, but the virtual machine, where the installation is running. Agreed, the virtual CDROM seems fine the problem is occurs at the point the packages need to be installed. I will try and execute the commands on the vm in the mean time and get back to you. Thanks, Sal. It's hard to tell without /tmp/anaconda.log and /tmp/storage.log, but just a guess: There's no ID_FS_TYPE for your cdrom, so anaconda's not picking up that there's a cdrom to install from. We've seen this problem a lot in the past. Getting those log files will confirm. (In reply to comment #3) > It's hard to tell without /tmp/anaconda.log and /tmp/storage.log, but just a > guess: There's no ID_FS_TYPE for your cdrom, so anaconda's not picking up > that there's a cdrom to install from. We've seen this problem a lot in the > past. Getting those log files will confirm. Note that the udev output was _not_ on the virtual machine where anaconda was running in!!! Cool story. Hi I recreated the image and I don't see the problem any more. It would seem that the image was faulty? Please go ahead and close this. Thanks, Sal. |