Bug ID 1206611
Summary Tumbleweed Net installer fails dhcp bc choosing wrong network interface?
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS openSUSE Tumbleweed
Status NEW
Severity Critical
Priority P5 - None
Component Network
Assignee screening-team-bugs@suse.de
Reporter jlopez777+opensuse@gmail.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Created attachment 863626 [details]
shot of network device not running

Expected behavior 

DHCP in net install connects to repo


Actual behavior - fails


============

Details: 

Seems as though I can't turn on my network device. It reads "not running" (see
attached). 

When I go to shell, no text editor installed, so can't change any configs. 

THEORY: 

Because it is not running (maybe driver not loaded?) it can't do DHCP and gives
failure. 


If you see in attachment, lo is up....

How can I tell the network installer to use lo ? 

Maybe not a bug, but potential enhancement opportunity to 

1. Use a solution that auto-scans wifi instead of manually putting in info. 

2. include text editor if not already there and I'm missing it

3. Provide user option which network interface to use, so if wlp1s0 doesn't
work, they can go and try another available interface. 


Wasn't sure of major or critical - bc if users can't connect to repo to
install, network installer is "broken"..if this is actually the issue, it
essentially keeps user from goal of net install, hence landing on critical.


You are receiving this mail because: