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.

Description of problem:
Unable to read package metadata. This may be due to a missing repodata directory. Please ensure that your install tree has been correctly generated.


Version-Release number of selected component (if applicable):
RHEL-7.0-20120620.n.0

How reproducible:
time to time

Steps to Reproduce:
1. clen job : https://beaker.engineering.redhat.com/jobs/254882
  
Actual results:
There are more details at ticket:
https://engineering.redhat.com/rt/Ticket/Display.html?id=158782

the installation does not start as it throws the following error:

┌──────────────────────────┤ Error ├──────────────────────────┐
│ │
│ Unable to read package metadata. This may be due to a │
│ missing repodata directory. Please ensure that your │
│ install tree has been correctly generated. │
│ │
│ failure: │
│ repodata/5fe459f4ca7fb3dbceee846c9d5aecac592e84f9f38dba │
│ 4daf081041b5190c47-primary.sqlite.bz2 from anaconda-0: │
│ [Errno 256] No more mirrors to try. │
│ │
│ ┌────────────────┐ ┌──────┐ ┌───────┐ ┌──────────┐ │
│ │ Exit installer │ │ Edit │ │ Retry │ │ Continue │ │
│ └────────────────┘ └──────┘ └───────┘ └──────────┘ │
│ │
│ │
└─────────────────────────────────────────────────────────────┘


Expected results:
machine is installed

Additional info:

You need to attach the anaconda logs to this bug report as individual, uncompressed attachments.  Doing anything else prevents us from searching bugzilla in the future.  Please do this every time you file an anaconda bug or we will have to close things as INSUFFICIENT_DATA.

Created attachment 596394 [details]
anaconda.log from RHEL-7.0-20120626.n.0 Server x86_64

anaconda.log from one of my jobs attached

So this was looking on the NFS mount storage.bos.redhat.com:/vol/engineering/devarchive/redhat/nightly/RHEL-7.0-20120626.n.0/compose/Server/x86_64/os/ and trying to read repodata from there.  It wasn't able to find the repodata file on that mount.  Is it possible that mount was out of sync at the time of the install attempt?  Were you able to reproduce the problem at a later time?