https://bugzilla.suse.com/show_bug.cgi?id=1201010 https://bugzilla.suse.com/show_bug.cgi?id=1201010#c5 --- Comment #5 from Thorsten Kukuk <kukuk@suse.com> --- (In reply to Robert Schweikert from comment #4)

Hold on that doesn't make any sense to me what so ever. NM does not handle the underlying connections, i.e. NM does not make DHCP requests etc.

It does.

That happens via wicked or via dhcpclient.

You don't need wicked and you don't need dhcpclient. Neither of both is installed on my MicroOS systems.

If we are dropping wicked are we going back to dhcpclient?

No, we are dropping wicked since we switched already to NetworkManager as default for openSUSE Tumbleweed and openSUSE MicroOS. SLE Micro will switch with 5.3 to NetworkManager, as often enough mentioned by Daniel and Jiri in the sync calls since half a year. Wicked does not provide the functionality our customers especially from the Edge require.

What happens to our sysconfig layout and the values we set in sysconfig?

I would like to drop them sooner than later, because NetworkManager provides a much better interface. I don't understand why we limit ourself with netconfig to 14 year old technology? But currently it looks like it stays, and since sysconfig and sysconfig-netconfig are compatible with NetworkManager...

This is a much bigger topic than a "Require" statement in the spec file.

For the majority of packages my team touched it was not much more than fixing the requires.

As a side note wicked is required by a lot of packages in the Public Cloud area, we need a running network.

Then you should start working on it... -- You are receiving this mail because: You are on the CC list for the bug.