Bug 1085139

Summary:	systemd-networkd is out of YaST2 network managers list
Product:	[openSUSE] openSUSE Distribution	Reporter:	Mikhail Kasimov <mikhail.kasimov>
Component:	YaST2	Assignee:	E-mail List <yast2-maintainers>
Status:	RESOLVED FEATURE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	jreidinger, mikhail.kasimov
Version:	Leap 42.3
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 42.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Mikhail Kasimov 2018-03-13 18:21:56 UTC

Hello!

Subj.

Steps-to-reproduce algo: https://youtu.be/6o8kWuotHh8 (too long to describe in text, video is much shorter. :) )

Comment 1 Stefan Hundhammer 2018-03-22 10:41:26 UTC

Please read the FAQ.

https://en.opensuse.org/openSUSE:Bug_reporting_FAQ#People_were_very_unhappy_because_I_only_wrote_.22see_subject.22_in_the_Bugzilla_bug_description_-_but_my_subject_really_explains_it_all.21_Isn.27t_it_pure_nitpicking_to_insist_on_bug_reporters_repeating_that_in_the_description_field.3F

And having a video might be a nice add-on, but it is no substitute for a bug description. How many times do you think people are looking through bugs; do you seriously expect them to watch that video every time?

So, please add a problem description, and if you think it's a YaST bug, y2logs.

https://en.opensuse.org/openSUSE:Report_a_YaST_bug#Attachments_-_y2logs.2C_hwinfo_etc.

Comment 2 Stefan Hundhammer 2018-03-22 10:42:52 UTC

And frankly, having that part in Russian does not exactly help us to figure out what this is all about.

Comment 3 Mikhail Kasimov 2018-03-22 11:17:50 UTC

OK, let's describe this in something else, comparing to Pushkin's poetical language. :)

There're three network management frameworks in openSUSE 42.3 for now:

a) Wicked, which is used by default.
b) Network Manager, which is OFF by default.
c) systemd-networkd, which is OFF by default.

YaST2 handles two of them to make user able to configure them via YaST's interface: Wicked and Network Manager. Simultaneously to this, systemd-networkd is out of this YaST2's list. And this seems to be a bug (lack of YaST's functionality).

Steps-to-reproduce algo:
===========================
1) Start YaST --> Network.
2) Check network management frameworks downdrop list. You can see Wicked and Network Manager.
3) In terminal do 'systemctal status systemd-networkd.service' and make sure, that service in OFF, but present. This means, that systemd's network management system is present.
4) Back to 2. to convince, that systemd-networkd is out of list and cannot be managed via YaST2.
===========================

Hope, such text-description will help. ;) Thanks!

Comment 4 Josef Reidinger 2018-03-28 12:15:49 UTC

Yes, we support just two frameworks now. One is suitable for notebooks that travel ( NM ) and second for stationary PCs and servers ( wicked ). If you want to play with another one, we are not against. But we do not see value in it.

So this is feature request that need to be properly discussed and also it should convince product managers or developer that it make sense to invest time and work to support another backend.