RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 948713 - RHEL6.3 DVD: Unable to read group information from repositories.
Summary: RHEL6.3 DVD: Unable to read group information from repositories.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-05 07:58 UTC by Salim Badakhchani
Modified: 2013-04-11 13:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-11 13:39:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Salim Badakhchani 2013-04-05 07:58:09 UTC 
Description of problem:

Booting a vm of RHEL6.3-20120613.2-Server-x86_64-DVD1.iso the installation halts with the following error:

Unable to read group information from repositories.
  This is a problem with the generation of your install tree.

The DVD has a stock kickstart file placed in the root and is created thus:

mkisofs -J -R -v -T -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o /mnt/media/USB0/iso/RHEL6.3-x86_64-DVD1.iso .

The vm is initialised as follows:

virt-install \
-n redhat-koji \
-r 4096 \
--vcpus=2 \
--os-type=linux \
--os-variant=rhel6 \
--accelerate \
--mac=52:54:00:04:DC:E1 \
--disk=/mnt/media/USB0/vm/RedHat-Koji.img \
--disk=/mnt/media/USB0/iso/RHEL6.3-x86_64-DVD1.iso,device=cdrom \
--location /mnt/media/USB0/iso/RHEL6.3-x86_64-DVD1.iso \
--extra-args="append ks=cdrom initrd=initrd.img ramdisk_size=8192"

The vm boot and the kickstart file is read correctly.  The installation partitions the vm and then the installation halts with the error detailed. 


Version-Release number of selected component (if applicable):

udev-147-2.41.el6.x86_64

How reproducible: 

Every time.


Steps to Reproduce:
1. Mount the DVD and place a kickstart file in root.
2. Create a bootable DVD with the command above.
3. Initialise the vm with the command above.
  
Actual results:

Installation halts

Expected results:

Installation should be completed as per kickstart configuration.

Additional info:

/lib/udev/cdrom_id --debug /dev/sr0
probing: '/dev/sr0'
CDROM_DRIVE_STATUS != CDS_DISC_OK
INQUIRY: [HL-DT-ST][DVD+-RW GT10N   ][A111]
no current profile, assuming no media
GET CONFIGURATION: size of features buffer 0x0150
GET CONFIGURATION: size of features buffer 0x0150
GET CONFIGURATION: feature 'profiles', with 13 entries
profile 0x12 dvd_ram
profile 0x2b dvd_plus_r_dl
profile 0x1b dvd_plus_r
profile 0x1a dvd_plus_rw
profile 0x15 <ignored>
profile 0x14 dvd_rw
profile 0x13 dvd_rw
profile 0x11 <ignored>
profile 0x10 dvd_rom
profile 0x0a cd_rw
profile 0x09 cd_r
profile 0x08 cd_rom
profile 0x02 <ignored>
GET CONFIGURATION: feature 0x0001 <ignored>, with 0x08 bytes
GET CONFIGURATION: feature 0x0002 <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0003 <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0004 <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0010 <ignored>, with 0x08 bytes
GET CONFIGURATION: feature 0x001d <ignored>, with 0x00 bytes
GET CONFIGURATION: feature 0x001e <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x001f <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0020 <ignored>, with 0x0c bytes
GET CONFIGURATION: feature 0x0021 <ignored>, with 0x08 bytes
GET CONFIGURATION: feature 0x0023 <ignored>, with 0x08 bytes
GET CONFIGURATION: feature 0x0024 <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0026 <ignored>, with 0x00 bytes
GET CONFIGURATION: feature 0x002a <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x002b <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x002c <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x002d <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x002e <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x002f <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0037 <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x003b <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0100 <ignored>, with 0x00 bytes
GET CONFIGURATION: feature 0x0103 <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0104 <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0105 <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0106 <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0107 <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0x0108 <ignored>, with 0x08 bytes
GET CONFIGURATION: feature 0x010a <ignored>, with 0x0c bytes
GET CONFIGURATION: feature 0x010b <ignored>, with 0x04 bytes
GET CONFIGURATION: feature 0xffdf <ignored>, with 0x08 bytes
ID_CDROM=1
ID_CDROM_CD=1
ID_CDROM_CD_R=1
ID_CDROM_CD_RW=1
ID_CDROM_DVD=1
ID_CDROM_DVD_R=1
ID_CDROM_DVD_RW=1
ID_CDROM_DVD_RAM=1
ID_CDROM_DVD_PLUS_R=1
ID_CDROM_DVD_PLUS_RW=1
ID_CDROM_DVD_PLUS_R_DL=1
ID_CDROM_MRW=1
ID_CDROM_MRW_W=1


udevadm info --query=all --name=/dev/sr0
P: /devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sr0
N: sr0
L: -100
S: cdrom
S: disk/by-id/ata-HL-DT-ST_DVD+_-RW_GT10N
E: DEVLINKS=/dev/cdrom /dev/disk/by-id/ata-HL-DT-ST_DVD+_-RW_GT10N
E: DEVNAME=/dev/sr0
E: DEVPATH=/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sr0
E: DEVTYPE=disk
E: ID_ATA=1
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_BUS=ata
E: ID_CDROM=1
E: ID_CDROM_CD=1
E: ID_CDROM_CD_R=1
E: ID_CDROM_CD_RW=1
E: ID_CDROM_DVD=1
E: ID_CDROM_DVD_PLUS_R=1
E: ID_CDROM_DVD_PLUS_RW=1
E: ID_CDROM_DVD_PLUS_R_DL=1
E: ID_CDROM_DVD_R=1
E: ID_CDROM_DVD_RAM=1
E: ID_CDROM_DVD_RW=1
E: ID_CDROM_MRW=1
E: ID_CDROM_MRW_W=1
E: ID_MODEL=HL-DT-ST_DVD+_-RW_GT10N
E: ID_MODEL_ENC=HL-DT-ST\x20DVD+\x2f-RW\x20GT10N\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_REVISION=A111
E: ID_SERIAL=HL-DT-ST_DVD+_-RW_GT10N
E: ID_TYPE=cd
E: MAJOR=11
E: MINOR=0
E: SUBSYSTEM=block
E: TAGS=:seat:systemd:uaccess:
E: USEC_INITIALIZED=742941
Comment 1 Harald Hoyer 2013-04-05 09:51:01 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.
Comment 2 Salim Badakhchani 2013-04-05 09:57:13 UTC 
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.
Comment 3 Chris Lumens 2013-04-05 13:36:25 UTC 
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.
Comment 4 Harald Hoyer 2013-04-05 13:52:58 UTC 
(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!!!
Comment 5 Chris Lumens 2013-04-05 13:55:30 UTC 
Cool story.
Comment 6 Salim Badakhchani 2013-04-11 11:26:43 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.