[New: openFATE 321608] Detect and repair network config messed up by ifaces name change
Feature added by: Ancor Gonzalez Sosa (ancorgs) Feature #321608, revision 1 Title: Detect and repair network config messed up by ifaces name change openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Ancor Gonzalez Sosa (ancorgs) Partner organization: openSUSE.org Description: Leap 42.1 introduced a change in how the network interfaces are renamed in comparison to 13.X. This is documented in the release notes (https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.1/#idm1402896...) Tumbleweed uses the same approach that 13.X. So in general, it's not unusual for an openSUSE system to end up in a situation in which the network configuration is broken due to the mix of both naming schemes. As Ludwig Nussel suggested in bug#1000732 (https://bugzilla.suse.com/show_bug.cgi?id=1000732#c6), it would be nice if YaST could detect the situation and offer a convenient and user-friendly way to fix the mess. -- openSUSE Feature: https://features.opensuse.org/321608
Feature changed by: Ancor Gonzalez Sosa (ancorgs) Feature #321608, revision 2 Title: Detect and repair network config messed up by ifaces name change openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Ancor Gonzalez Sosa (ancorgs) Partner organization: openSUSE.org Description: Leap 42.1 introduced a change in how the network interfaces are renamed in comparison to 13.X. This is documented in the release notes (https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.1/#idm1402896...) - Tumbleweed uses the same approach that 13.X. So in general, it's not - unusual for an openSUSE system to end up in a situation in which the - network configuration is broken due to the mix of both naming schemes. + Tumbleweed uses the same approach that 13.X. + So it's not unusual for an openSUSE system to end up in a situation in + which the network configuration is broken due to the mix of both naming + schemes. As Ludwig Nussel suggested in bug#1000732 (https://bugzilla.suse.com/show_bug.cgi?id=1000732#c6), it would be nice if YaST could detect the situation and offer a convenient and user- friendly way to fix the mess. -- openSUSE Feature: https://features.opensuse.org/321608
Feature changed by: Karl Cheng (qantas94heavy) Feature #321608, revision 3 Title: Detect and repair network config messed up by ifaces name change - openSUSE Distribution: Unconfirmed + openSUSE Distribution: Evaluation by engineering manager Priority Requester: Neutral Requested by: Ancor Gonzalez Sosa (ancorgs) Partner organization: openSUSE.org Description: Leap 42.1 introduced a change in how the network interfaces are renamed in comparison to 13.X. This is documented in the release notes (https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.1/#idm1402896...) Tumbleweed uses the same approach that 13.X. So it's not unusual for an openSUSE system to end up in a situation in which the network configuration is broken due to the mix of both naming schemes. As Ludwig Nussel suggested in bug#1000732 (https://bugzilla.suse.com/show_bug.cgi?id=1000732#c6), it would be nice if YaST could detect the situation and offer a convenient and user- friendly way to fix the mess. -- openSUSE Feature: https://features.opensuse.org/321608
participants (1)
-
fate_noreply@suse.de