Bug 1473849 - [abrt] blivet-gui: blivetgui.py:227:_reraise_exception:ValueError: etherd/e1.1 is not a valid name for this device
[abrt] blivet-gui: blivetgui.py:227:_reraise_exception:ValueError: etherd/e1....
Status: NEW
Product: Fedora
Classification: Fedora
Component: blivet-gui (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Vojtech Trefny
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-07-21 16:40 EDT by Davide Repetto
Modified: 2017-11-16 09:08 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (8.01 KB, text/plain)
2017-07-21 16:40 EDT, Davide Repetto
no flags Details
File: blivet.log (163.38 KB, text/plain)
2017-07-21 16:40 EDT, Davide Repetto
no flags Details
File: program.log (18.04 KB, text/plain)
2017-07-21 16:41 EDT, Davide Repetto
no flags Details
File: environ (2.82 KB, application/octet-stream)
2017-07-21 16:41 EDT, Davide Repetto
no flags Details

  None (edit)
Description Davide Repetto 2017-07-21 16:40:46 EDT
Version-Release number of selected component:

Additional info:
reporter:       libreport-2.8.0
cmdline:        /usr/bin/python3 /usr/bin/blivet-gui
executable:     /usr/bin/blivet-gui
kernel:         4.11.10-200.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
#1 __init__ in /usr/lib/python3.5/site-packages/blivet/devices/device.py:85
#2 run_with_lock in /usr/lib/python3.5/site-packages/blivet/threads.py:45
#3 __init__ in /usr/lib/python3.5/site-packages/blivet/devices/storage.py:136
#4 run_with_lock in /usr/lib/python3.5/site-packages/blivet/threads.py:45
#5 __init__ in /usr/lib/python3.5/site-packages/blivet/devices/disk.py:97
#6 run_with_lock in /usr/lib/python3.5/site-packages/blivet/threads.py:45
#7 run in /usr/lib/python3.5/site-packages/blivet/populator/helpers/disk.py:74
#8 handle_device in /usr/lib/python3.5/site-packages/blivet/populator/populator.py:306
#9 run_with_lock in /usr/lib/python3.5/site-packages/blivet/threads.py:45
#10 _populate in /usr/lib/python3.5/site-packages/blivet/populator/populator.py:518
Comment 1 Davide Repetto 2017-07-21 16:40:52 EDT
Created attachment 1302553 [details]
File: backtrace
Comment 2 Davide Repetto 2017-07-21 16:40:58 EDT
Created attachment 1302554 [details]
File: blivet.log
Comment 3 Davide Repetto 2017-07-21 16:41:00 EDT
Created attachment 1302555 [details]
File: program.log
Comment 4 Davide Repetto 2017-07-21 16:41:02 EDT
Created attachment 1302556 [details]
File: environ
Comment 5 Fedora End Of Life 2017-11-16 09:08:35 EST
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

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