Bug 913150 - [abrt] yum-3.4.3-60.fc19: history.py:1656:_create_db_file:OperationalError: table trans_beg already exists
Summary: [abrt] yum-3.4.3-60.fc19: history.py:1656:_create_db_file:OperationalError: t...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3d72e9b3590e487f9f2393abaaf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-20 14:11 UTC by Michael Schwendt
Modified: 2015-02-17 14:47 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:47:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (2.46 KB, text/plain)
2013-02-20 14:11 UTC, Michael Schwendt
no flags Details
File: core_backtrace (623 bytes, text/plain)
2013-02-20 14:11 UTC, Michael Schwendt
no flags Details
File: environ (2.16 KB, text/plain)
2013-02-20 14:11 UTC, Michael Schwendt
no flags Details

Description Michael Schwendt 2013-02-20 14:11:20 UTC
Description of problem:
I had lost contents of /var/lib/yum/history/* and issue, and the first "yum history new" makes ABRT catch the traceback, whereas subsequent "yum history new" don't crash anymore.

Version-Release number of selected component:
yum-3.4.3-60.fc19

Additional info:
cmdline:        /usr/bin/python /bin/yum history new
executable:     /bin/yum
kernel:         3.8.0-0.rc7.git3.1.fc19.x86_64
uid:            0

Truncated backtrace:
history.py:1656:_create_db_file:OperationalError: table trans_beg already exists

Traceback (most recent call last):
  File "/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 316, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 126, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 520, in doCommands
    return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 2974, in doCommand
    ret = self._hcmd_new(base, extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 2873, in _hcmd_new
    base.history._create_db_file()
  File "/usr/lib/python2.7/site-packages/yum/history.py", line 1656, in _create_db_file
    cur.execute(op)
OperationalError: table trans_beg already exists

Local variables in innermost frame:
cur: <sqlite3.Cursor object at 0x24c31f0>
ops: [' CREATE TABLE trans_beg (\n     tid INTEGER PRIMARY KEY,\n     timestamp INTEGER NOT NULL, rpmdb_version TEXT NOT NULL,\n     loginuid INTEGER);\n', ' CREATE TABLE trans_end (\n     tid INTEGER PRIMARY KEY REFERENCES trans_beg,\n     timestamp INTEGER NOT NULL, rpmdb_version TEXT NOT NULL,\n     return_code INTEGER NOT NULL);\n', ' CREATE TABLE trans_with_pkgs (\n     tid INTEGER NOT NULL REFERENCES trans_beg,\n     pkgtupid INTEGER NOT NULL REFERENCES pkgtups);\n', ' CREATE TABLE trans_error (\n     mid INTEGER PRIMARY KEY,\n     tid INTEGER NOT NULL REFERENCES trans_beg,\n     msg TEXT NOT NULL);\n', ' CREATE TABLE trans_script_stdout (\n     lid INTEGER PRIMARY KEY,\n     tid INTEGER NOT NULL REFERENCES trans_beg,\n     line TEXT NOT NULL);\n', ' CREATE TABLE trans_data_pkgs (\n     tid INTEGER NOT NULL REFERENCES trans_beg,\n     pkgtupid INTEGER NOT NULL REFERENCES pkgtups,\n     done BOOL NOT NULL DEFAULT FALSE, state TEXT NOT NULL);\n', ' CREATE TABLE pkgtups (\n     pkgtupid INTEGER PRIMARY KEY,     name TEXT NOT NULL, arch TEXT NOT NULL,\n     epoch TEXT NOT NULL, version TEXT NOT NULL, release TEXT NOT NULL,\n     checksum TEXT);\n', ' CREATE INDEX i_pkgtup_naevr ON pkgtups (name, arch, epoch, version, release);\n']
self: <yum.history.YumHistory instance at 0x23afe18>
_db_file: '//var/lib/yum/history/history-2013-02-20.sqlite'
op: ' CREATE TABLE trans_beg (\n     tid INTEGER PRIMARY KEY,\n     timestamp INTEGER NOT NULL, rpmdb_version TEXT NOT NULL,\n     loginuid INTEGER);\n'
fo: 8

Comment 1 Michael Schwendt 2013-02-20 14:11:23 UTC
Created attachment 700038 [details]
File: backtrace

Comment 2 Michael Schwendt 2013-02-20 14:11:26 UTC
Created attachment 700039 [details]
File: core_backtrace

Comment 3 Michael Schwendt 2013-02-20 14:11:28 UTC
Created attachment 700040 [details]
File: environ

Comment 4 Fedora End Of Life 2013-04-03 16:44:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 5 Fedora End Of Life 2015-01-09 17:42:01 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-02-17 14:47:18 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.