Bug 1323552

Summary: [abrt] dnf: rpmtrans.py:558:_scriptError:AttributeError: 'NoneType' object has no attribute 'name'
Product: [Fedora] Fedora Reporter: Silvio Palmieri <silvio.a.palmieri>
Component: dnfAssignee: rpm-software-management
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: jmracek, joeffel.faelnar, jsilhan, mluscon, mmraka, packaging-team-maint, pnemade, silvio.a.palmieri, vmukhame
Target Milestone: ---Keywords: Triaged
Target Release: ---Flags: jmracek: needinfo? (silvio.a.palmieri)
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9b6f6c8269bdb7e66d90418394d86b574d13f807
Whiteboard: abrt_hash:cbd9e3cb0272dd8356fc3a35c2f593ea0cb84e41;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-28 14:42:16 UTC 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
File: _var_log_dnf.log
none
File: backtrace
none
File: dnf-makecache.log
none
File: environ none

Description Silvio Palmieri 2016-04-04 04:29:47 UTC
Version-Release number of selected component:
dnf-1.1.7-2.fc23

Additional info:
reporter:       libreport-2.6.4
cmdline:        /usr/bin/python3 -OO /bin/dnf update
executable:     /bin/dnf
kernel:         4.2.3-300.fc23.x86_64
runlevel:       N 5
type:           Python3
uid:            0

Truncated backtrace:
rpmtrans.py:558:_scriptError:AttributeError: 'NoneType' object has no attribute 'name'

Traceback (most recent call last):
  File "/usr/lib/python3.4/site-packages/dnf/yum/rpmtrans.py", line 427, in callback
    self._scriptError(bytes, total, h)
  File "/usr/lib/python3.4/site-packages/dnf/yum/rpmtrans.py", line 558, in _scriptError
    name = pkg.name
AttributeError: 'NoneType' object has no attribute 'name'

Local variables in innermost frame:
_: None
bytes: 262144
pkg: None
self: <dnf.yum.rpmtrans.RPMTransaction object at 0x7fc13ab83da0>
scriptlet_name: '<unknown>'
total: 0
h: None

Comment 1 Silvio Palmieri 2016-04-04 04:33:23 UTC
Created attachment 1143149 [details]
File: _var_log_dnf.log

Comment 2 Silvio Palmieri 2016-04-04 04:33:27 UTC
Created attachment 1143150 [details]
File: backtrace

Comment 3 Silvio Palmieri 2016-04-04 04:33:29 UTC
Created attachment 1143151 [details]
File: dnf-makecache.log

Comment 4 Silvio Palmieri 2016-04-04 04:33:30 UTC
Created attachment 1143152 [details]
File: environ

Comment 5 Honza Silhan 2016-04-04 11:50:09 UTC
We'll take a look.

Comment 6 Fedora Admin XMLRPC Client 2016-07-08 09:40:24 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Jaroslav Mracek 2016-09-17 19:17:31 UTC
I would like to investigate the bug, but somehow I don't know how to reproduce it. It fails when RPMCALLBACK_SCRIPT_ERROR appear, but I don't know which package has triggered this error. Please any information to reproduce it will be very useful. The best would be exact package name and from which version to which version it appears. Probably the information that I am looking for is in dnf.rpm.log but it is long time ago gone.

Comment 8 Fedora End Of Life 2016-11-25 07:14:13 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

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 23 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 9 Michael Mráka 2016-11-28 14:42:16 UTC

*** This bug has been marked as a duplicate of bug 1397047 ***