Bug 1047383

Summary: [abrt] synce-connector: synceconnector.py:349:signal_dccm:NameError: global name 'our_udi' is not defined
Product: [Fedora] Fedora Reporter: weidemann.m
Component: synce-connectorAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: andreas.bierfert, weidemann.m
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2e340851cb5cf1c23453dee4324b1c883fec658c
Whiteboard: abrt_hash:6c23c466def70f31dc8d0671a951a267a8c46c60
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:48:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description weidemann.m 2013-12-30 20:25:08 UTC
Version-Release number of selected component:
synce-connector-0.15.2-5.fc17

Additional info:
reporter:       libreport-2.1.10
cmdline:        python /usr/share/synce-connector/udev-synce-rndis
executable:     /usr/share/synce-connector/udev-synce-rndis
kernel:         3.12.5-200.fc19.i686
runlevel:       N 5
type:           Python
uid:            0

Truncated backtrace:
synceconnector.py:349:signal_dccm:NameError: global name 'our_udi' is not defined

Traceback (most recent call last):
  File "/usr/share/synce-connector/udev-synce-rndis", line 61, in <module>
    if signal_dccm(device_path,device_ip,local_ip,True) == False:
  File "/usr/share/synce-connector/synceconnector.py", line 349, in signal_dccm
    logger.critical("failed to signal device connect to dccm device manager %s: %s" % (our_udi, e))
NameError: global name 'our_udi' is not defined

Local variables in innermost frame:
dccm_manager: <Interface <ProxyObject wrapping <dbus._dbus.SystemBus (system) at 0xb73eb4dc> :1.21 /org/synce/dccm/DeviceManagerControl at 0xb73eec0c> implementing 'org.synce.dccm.DeviceManager.Control' at 0xb73eeb4c>
local_ip: '169.254.2.2'
device_ip: '169.254.2.1'
dccm_log_level: '6'
rndis: True
device_path: '/devices/pci0000:00/0000:00:02.1/usb3/3-2/3-2:1.0/net/enp0s2f1u2'
rndis_text: 'True'

Potential duplicate: bug 760991

Comment 1 weidemann.m 2013-12-30 20:25:13 UTC
Created attachment 843508 [details]
File: backtrace

Comment 2 weidemann.m 2013-12-30 20:25:15 UTC
Created attachment 843509 [details]
File: environ

Comment 3 Fedora End Of Life 2015-01-09 20:58:47 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 4 Fedora End Of Life 2015-02-17 19:48:43 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.