Bug 1046973

Summary:	Changing YaST2 Wicket service to Network Manager changes the IP-address
Product:	[openSUSE] openSUSE Distribution	Reporter:	Terje J. Hanssen <terjejhanssen>
Component:	Network	Assignee:	wicked maintainers <wicked-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	songchuan.kang
Version:	Leap 42.3
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Terje J. Hanssen 2017-07-02 20:08:41 UTC

I have experienced this confusing behavior also on previous openSUSE releases.

I did recently a new 42.3 installation from DVD media, and let the initial network configuration be set up automatically, expectately with DHCP.

After the installation I enterde the YaST2 > System > Network setting tool, edited the network and configured it to the wanted Statical IP address, host name etc. and saved it.

Rebooted and the wanted IP address was confirmed with ip and ifconfig.

Next started the YaST2 > System > Network setting tool shsom and just changed the General > Wicket service to Network Manager service and nothing else before OK.

The confusing here is that this step also changes the IP address from the statical assigned Ip address, possibly back to the initial automatic DHCP address, which is confirmed both with ip, ifconfig and with Network Manager itself.

Therefore I have had to keep Wicked service to be able keep the wanted statical ip-address.

Is this a bug somewhere?

Comment 1 Tomáš Chvátal 2019-07-11 11:13:17 UTC

This is automated batch bugzilla cleanup.

The openSUSE 42.3 changed to end-of-life (EOL [1]) status. As such
it is no longer maintained, which means that it will not receive any
further security or bug fix updates.
As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
openSUSE (At this moment openSUSE Leap 15.1, 15.0 and Tumbleweed) please
feel free to reopen this bug against that version (!you must update the
"Version" component in the bug fields, do not just reopen please), or
alternatively create a new ticket.

Thank you for reporting this bug and we are sorry it could not be fixed
during the lifetime of the release.

[1] https://en.opensuse.org/Lifetime