Bug 708853

Summary: IntegrityError: trans_data_pkgs.tid may not be NULL
Product: [Fedora] Fedora Reporter: Ugur Celik <admin>
Component: yumAssignee: Fedora Packaging Toolset Team <packaging-team>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: ffesti, gncbilgisayar, james.antill, jonathan, justranger--07, korayharman, maxamillion, pmatilai, tla, ulgenmeric, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: anaconda_trace_hash:35d8a204f5a4226f817b149d700f46c81a57e022957330c19b5fbfe6caf3f3a6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda. none

Description Ugur Celik 2011-05-29 21:10:49 UTC
The following was filed automatically by anaconda:
anaconda 15.31 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/yum/sqlutils.py", line 168, in executeSQLQmark
    return cursor.execute(query, params)
  File "/usr/lib/python2.7/site-packages/yum/history.py", line 735, in trans_data_pid_beg
    VALUES (?, ?, ?)""", (self._tid, pid, state))
  File "/usr/lib/python2.7/site-packages/yum/history.py", line 826, in beg
    self.trans_data_pid_beg(pid, state)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1425, in runTransaction
    self.skipped_packages, rpmdb_problems, cmdline)
  File "/usr/lib/python2.7/site-packages/pyanaconda/yuminstall.py", line 1035, in _run
    self.runTransaction(cb=cb)
  File "/usr/lib/python2.7/site-packages/pyanaconda/yuminstall.py", line 1018, in run
    if self._run(instLog, cb, intf) == DISPATCH_BACK:
  File "/usr/lib/python2.7/site-packages/pyanaconda/yuminstall.py", line 1691, in doInstall
    rc = self.ayum.run(self.instLog, cb, anaconda.intf)
  File "/usr/lib/python2.7/site-packages/pyanaconda/backend.py", line 208, in doInstall
    return anaconda.backend.doInstall(anaconda)
  File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 211, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 130, in gotoNext
    self.moveStep()
  File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1257, in nextClicked
    self.anaconda.dispatch.gotoNext()
  File "/usr/lib/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback
    self.intf.icw.nextClicked()
  File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1278, in handleRenderCallback
    self.currentWindow.renderCallback()
IntegrityError: trans_data_pkgs.tid may not be NULL

Comment 1 Ugur Celik 2011-05-29 21:10:56 UTC
Created attachment 501660 [details]
Attached traceback automatically from anaconda.

Comment 2 legadema07 2011-06-10 13:37:56 UTC
Created attachment 504120 [details]
Attached traceback automatically from anaconda.

Comment 3 Ilkay 2011-06-21 10:19:41 UTC
Created attachment 505792 [details]
Attached traceback automatically from anaconda.

Comment 4 Ilkay 2011-06-21 10:24:22 UTC
Created attachment 505794 [details]
Attached traceback automatically from anaconda.

Comment 5 James Antill 2011-06-21 14:56:49 UTC
Is this reproducible?

From what I can tell for this traceback to happen it means the following lines failed:

        res = executeSQL(cur,
                         """INSERT INTO trans_beg
                            (timestamp, rpmdb_version, loginuid)
                            VALUES (?, ?, ?)""", (int(time.time()),
                                                    str(rpmdb_version),
                                                    yum.misc.getloginuid()))
        self._tid = cur.lastrowid

...which is really bad. I'm not sure how that can happen. We could detect that, and then just ignore logging the transaction ... I guess, kind of horrible though.

Comment 6 korayharman 2011-07-30 20:40:58 UTC
Created attachment 515989 [details]
Attached traceback automatically from anaconda.

Comment 7 Fedora Admin XMLRPC Client 2012-04-27 15:39:12 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 8 Fedora End Of Life 2012-08-06 19:59:31 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Fedora End Of Life 2012-08-06 20:00:26 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 meric 2013-01-08 15:51:12 UTC
Created attachment 674918 [details]
Attached traceback automatically from anaconda.