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 1162290 - RepoError: database disk image is malformed
Summary: RepoError: database disk image is malformed
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.1
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Will Woods
QA Contact: Release Test Team
URL:
Whiteboard: abrt_hash:6298e1e89ab7a67dcb10e8e9150...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-10 18:53 UTC by Bill Sanford
Modified: 2015-04-02 18:17 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-02 18:17:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
File: anaconda-tb (349.83 KB, text/plain)
2014-11-10 18:53 UTC, Bill Sanford 		no flags Details
File: anaconda.log (7.74 KB, text/plain)
2014-11-10 18:53 UTC, Bill Sanford 		no flags Details
File: environ (404 bytes, text/plain)
2014-11-10 18:53 UTC, Bill Sanford 		no flags Details
File: lsblk_output (1.08 KB, text/plain)
2014-11-10 18:53 UTC, Bill Sanford 		no flags Details
File: nmcli_dev_list (1.23 KB, text/plain)
2014-11-10 18:53 UTC, Bill Sanford 		no flags Details
File: os_info (510 bytes, text/plain)
2014-11-10 18:53 UTC, Bill Sanford 		no flags Details
File: program.log (15.98 KB, text/plain)
2014-11-10 18:53 UTC, Bill Sanford 		no flags Details
File: storage.log (30.23 KB, text/plain)
2014-11-10 18:53 UTC, Bill Sanford 		no flags Details
File: syslog (64.08 KB, text/plain)
2014-11-10 18:53 UTC, Bill Sanford 		no flags Details
File: ifcfg.log (1.07 KB, text/plain)
2014-11-10 18:53 UTC, Bill Sanford 		no flags Details
File: packaging.log (138.31 KB, text/plain)
2014-11-10 18:53 UTC, Bill Sanford 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1167948 0 unspecified CLOSED IOError: [Errno 9] Bad file descriptor 2021-02-22 00:41:40 UTC

Internal Links: 1167948

Description Bill Sanford 2014-11-10 18:53:46 UTC 
Description of problem:
I was installing RHEL-7.1-20141029.0 on RHEV-M 3.5 (vt9/el6)

Version-Release number of selected component:
anaconda-19.31.104-1

The following was filed automatically by anaconda:
anaconda 19.31.104-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/yum/sqlitesack.py", line 55, in newFunc
    raise Errors.RepoError, str(e)
  File "/usr/lib/python2.7/site-packages/yum/sqlitesack.py", line 1714, in searchNevra
    for pkg in self.searchNames(names=[name]):
  File "/usr/lib/python2.7/site-packages/yum/sqlitesack.py", line 46, in newFunc
    return func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/yum/packageSack.py", line 595, in _computeAggregateListResult
    sackResult = apply(method, args)
  File "/usr/lib/python2.7/site-packages/yum/packageSack.py", line 403, in searchNevra
    return self._computeAggregateListResult("searchNevra", name, epoch, ver, rel, arch)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4787, in install
    ver=nevra_dict['version'], rel=nevra_dict['release'])
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3906, in selectGroup
    pkg_warning_level='debug2')
  File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1294, in _selectYumGroup
    self._yum.selectGroup(groupid, group_package_types=pkg_types)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1409, in _applyYumSelections
    self._selectYumGroup("core")
  File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1513, in checkSoftwareSelection
    self._applyYumSelections()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/software.py", line 123, in checkSoftwareSelection
    self.payload.checkSoftwareSelection()
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 211, in run
    threading.Thread.run(self, *args, **kwargs)
RepoError: database disk image is malformed

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=/distrotrees/68480/initrd method=http://download.eng.bos.redhat.com/rel-eng/RHEL-7.1-20141029.0/compose/Server/x86_64/os/ repo=http://download.eng.bos.redhat.com/rel-eng/RHEL-7.1-20141029.0/compose/Server/x86_64/os/  BOOT_IMAGE=/distrotrees/68480/kernel 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.10.0-195.el7.x86_64
product:        Red Hat Enterprise Linux 7"
release:        Red Hat Enterprise Linux Workstation release 7.1 Beta (Maipo)
release_type:   pre-release
type:           anaconda
version:        Red Hat Enterprise Linux Workstation"
Comment 1 Bill Sanford 2014-11-10 18:53:48 UTC 
Created attachment 955939 [details]
File: anaconda-tb
Comment 2 Bill Sanford 2014-11-10 18:53:49 UTC 
Created attachment 955940 [details]
File: anaconda.log
Comment 3 Bill Sanford 2014-11-10 18:53:50 UTC 
Created attachment 955941 [details]
File: environ
Comment 4 Bill Sanford 2014-11-10 18:53:50 UTC 
Created attachment 955942 [details]
File: lsblk_output
Comment 5 Bill Sanford 2014-11-10 18:53:51 UTC 
Created attachment 955943 [details]
File: nmcli_dev_list
Comment 6 Bill Sanford 2014-11-10 18:53:52 UTC 
Created attachment 955944 [details]
File: os_info
Comment 7 Bill Sanford 2014-11-10 18:53:53 UTC 
Created attachment 955945 [details]
File: program.log
Comment 8 Bill Sanford 2014-11-10 18:53:54 UTC 
Created attachment 955946 [details]
File: storage.log
Comment 9 Bill Sanford 2014-11-10 18:53:55 UTC 
Created attachment 955947 [details]
File: syslog
Comment 10 Bill Sanford 2014-11-10 18:53:56 UTC 
Created attachment 955948 [details]
File: ifcfg.log
Comment 11 Bill Sanford 2014-11-10 18:53:57 UTC 
Created attachment 955949 [details]
File: packaging.log
Comment 13 Brian Lane 2014-11-11 02:29:17 UTC 
Is this reproducible? It looks like the yum metadata was somehow corrupted.
Comment 14 Marian Csontos 2014-11-25 16:49:00 UTC 
Another user experienced a similar problem:

Simply running installation.
(This may be temporary issue with server - the installation passed right before.)

cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   repo=http://10.34.48.241/pub/rhel/nightly/latest-RHEL-7/compose/Server/x86_64/os
hashmarkername: anaconda
kernel:         3.10.0-206.el7.x86_64
package:        anaconda-19.31.109-1
product:        Red Hat Enterprise Linux 7"
reason:         RepoError: database disk image is malformed
release:        Red Hat Enterprise Linux Workstation release 7.1 Beta (Maipo)
release_type:   pre-release
version:        Red Hat Enterprise Linux Workstation"
Comment 16 Petr Sklenar 2015-01-13 12:51:43 UTC 
Another user experienced a similar problem:

I click into change keyboard layout

cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=/distrotrees/68905/initrd method=http://download-01.eng.brq.redhat.com/pub/rhel/nightly/RHEL-7.1-20150112.n.0/compose/Workstation/x86_64/os/ repo=http://download-01.eng.brq.redhat.com/pub/rhel/nightly/RHEL-7.1-20150112.n.0/compose/Workstation/x86_64/os/  BOOT_IMAGE=/distrotrees/68905/kernel 
hashmarkername: anaconda
kernel:         3.10.0-221.el7.x86_64
package:        anaconda-19.31.118-1
product:        Red Hat Enterprise Linux 7"
reason:         RepoError: database disk image is malformed
release:        Red Hat Enterprise Linux Workstation release 7.1 Beta (Maipo)
release_type:   pre-release
version:        Red Hat Enterprise Linux Workstation"
Comment 17 Petr Sklenar 2015-01-13 12:53:25 UTC 
I could see this issue too. I was trying to change keyboard layout.
Comment 18 Petr Sklenar 2015-01-13 13:19:44 UTC 
but now i tried that again and it seems to be working.
If its due to yum metadata isn't possible that anaconda tries to download it again?
Comment 19 Marian Csontos 2015-01-13 15:37:40 UTC 
(In reply to Petr Sklenar from comment #18)
> but now i tried that again and it seems to be working.
> If its due to yum metadata isn't possible that anaconda tries to download it
> again?

I guess it was downloading them in background while you were in the keyboard screen.

Perhaps it would be worth having Bug 1103452 fixed to see if that's the cause here as well as in the Bug 1167948.
Comment 20 David Cantrell 2015-04-02 18:17:57 UTC 
This happens during nearly every RHEL release.  Nightly trees end up with corrupted yum metadata and it resolves after a few days.  With so many trees being constructed and copied around, we're bound to hit this from time to time.  Still file the bugs because it may indicate another problem, but usually it's just this harmless problem due to our internal infrastructure and development processes.
Note You need to log in before you can comment on or make changes to this bug.