Hi,

I have nearly the same problem with my Tumbleweed.

Starting the Yast2-network-configuration-modul stops at "Reading Device-Configuration" (i don't know the exact english error-description, as i'm German) with the error


 Internal error. Please report a bug report with logs.
Run save_y2logs to get complete logs.

Caller: /usr/share/YaST2/lib/y2network/udev_rule.rb:232:in `block in part_by_key'

Details: undefined method `key' for nil:NilClass




A Reinstallation of the Yast-modules and finally a "zypper -dup" didn't help.

I've no idea, where to search.

Bye
Michael

(In reply to Mauro Gaspari from comment #0)
> Created attachment 823085 [details]
> yast2 logs
> 
> Trying to use Yast2 and check network configuration, an error is returned
> after the "Initializing Network Configuration" phase. 
> 
> Internal error. Please report a bug report with logs.
> Run save_y2logs to get complete logs.
> 
> Caller:
> /usr/share/YaST2/lib/y2network/widgets/interfaces_table.rb:109:in
> `interface_protocol'
> 
> Details: undefined method `name' for nil:NilClass

It seems to be caused by the ppp0 configuration. So, we should handle it better. At least not crash when no supported interfaces are read or in this case when the BOOTPROTO is not supported (dialup)

(In reply to Michael Izban from comment #1)
> Hi,
> 
> I have nearly the same problem with my Tumbleweed.
> 
> Starting the Yast2-network-configuration-modul stops at "Reading
> Device-Configuration" (i don't know the exact english error-description, as
> i'm German) with the error

We have refactored yast2-network recently and seems some configuration is not handled correctly at all. 

Although the title of the bug fits with our problem, the reason is different, in this case some problem reading the current udev rules in the system, I will check it but maybe we should move it to a separate bug. 

> 
> 
>  Internal error. Please report a bug report with logs.
> Run save_y2logs to get complete logs.
> 
> Caller: /usr/share/YaST2/lib/y2network/udev_rule.rb:232:in `block in
> part_by_key'
> 
> Details: undefined method `key' for nil:NilClass
> 
> 
> 
> 
> A Reinstallation of the Yast-modules and finally a "zypper -dup" didn't help.
> 
> I've no idea, where to search.

Still have to check logs for knowing exactly what is wrong but at least from what you have pasted it seems related to udev rules as already commented previously

> 
> Bye
> Michael

(In reply to Knut Alejandro Anderssen González from comment #3)
> (In reply to Michael Izban from comment #1)
> > Hi,
> > 
> > I have nearly the same problem with my Tumbleweed.
> > 
> > Starting the Yast2-network-configuration-modul stops at "Reading
> > Device-Configuration" (i don't know the exact english error-description, as
> > i'm German) with the error
> 
> We have refactored yast2-network recently and seems some configuration is
> not handled correctly at all. 
> 
> Although the title of the bug fits with our problem, the reason is
> different, in this case some problem reading the current udev rules in the
> system, I will check it but maybe we should move it to a separate bug. 
> 
> > 
> > 
> >  Internal error. Please report a bug report with logs.
> > Run save_y2logs to get complete logs.
> > 
> > Caller: /usr/share/YaST2/lib/y2network/udev_rule.rb:232:in `block in
> > part_by_key'
> > 
> > Details: undefined method `key' for nil:NilClass
> > 
> > 
> > 
> > 
> > A Reinstallation of the Yast-modules and finally a "zypper -dup" didn't help.
> > 
> > I've no idea, where to search.
> 
> Still have to check logs for knowing exactly what is wrong but at least from
> what you have pasted it seems related to udev rules as already commented
> previously

And for that need logs :) so, please attach as described in:

https://en.opensuse.org/openSUSE:Report_a_YaST_bug

Even better if already reported as a separate bug.

> 
> > 
> > Bye
> > Michael

Created attachment 823279 [details]
Yast2Logs from save_y2logs

Logs vom running save_y2logs as recommendet in th error-report.

(In reply to Michael Izban from comment #5)
> Created attachment 823279 [details]
> Yast2Logs from save_y2logs
> 
> Logs vom running save_y2logs as recommendet in th error-report.

Could you also attach the content of the udev_rules?

/etc/udev/rules.d/70-persistent-net.rules

The content of /etc/udev/rules.d/70-persistent-net.rules:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{type}=="1", ATTR{dev_id}=="0x0", ATTR{address}=="00:1d:92:27:a6:b9", NAME="eth0_tumblw4k"


Bye
Michael

(In reply to Knut Alejandro Anderssen González from comment #2)
> (In reply to Mauro Gaspari from comment #0)
> > Created attachment 823085 [details]
> > yast2 logs
> > 
> > Trying to use Yast2 and check network configuration, an error is returned
> > after the "Initializing Network Configuration" phase. 
> > 
> > Internal error. Please report a bug report with logs.
> > Run save_y2logs to get complete logs.
> > 
> > Caller:
> > /usr/share/YaST2/lib/y2network/widgets/interfaces_table.rb:109:in
> > `interface_protocol'
> > 
> > Details: undefined method `name' for nil:NilClass
> 
> It seems to be caused by the ppp0 configuration. So, we should handle it
> better. At least not crash when no supported interfaces are read or in this
> case when the BOOTPROTO is not supported (dialup)

I am using openSUSE Tumbleweed in a dedicated appliance to act as router/gateway/firewall for my network. PPPoE is used to connect to the WAN.
And yes, I had zero issues with YAST network configuration before I configured PPPoE wan. 
If more logs or details are needed, please send me a list and I will do my best to help. 

Also, if proposed changes are staged in experimental repositories, I am happy to help with testing. Can always snapper rollback if things break :)

(In reply to Michael Izban from comment #7)
> The content of /etc/udev/rules.d/70-persistent-net.rules:
> 
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{type}=="1",
> ATTR{dev_id}=="0x0", ATTR{address}=="00:1d:92:27:a6:b9", NAME="eth0_tumblw4k"
> 
> 

That looks OK, and it works for me, isn't there any other entry?

Definitely there are two different bugs. One is about a PPPoE configuration that was skipped in Leap42.X but since Leap15.X we started to list it although the module for configuring dialup configurations was dropped in Leap15.

And the other one is about some problem with udev rules. Could you fill also a new one with the details ?

> Bye
> Michael

Hi,

yes, i will do so.

Bye.

Unable to confirm this in Tumbleweed 20200408.

(In reply to Mauro Gaspari from comment #0)
> Trying to use Yast2 and check network configuration, an error is returned
> after the "Initializing Network Configuration" phase. 
> 

I am not experiencing this issue in latest Tumbleweed 20210718 - everything seems to be okay. Can this bug be closed?

After an update, the error no longer occurred.

Thanks for help.

We can consider this bug as fixed according to comments and was fixed by:

https://github.com/yast/yast-network/pull/1206