Comment # 5 on bug 938896 from Marius Tomaschewski

No, this is not about any events -- they're emitted after the call
to netconfig as info for potential listeners.

We have a policy to use netconfig, configurable in yast2. netconfig
considers changes to the file as intended by the admin/user and does
not overwrite the file without to disable the netconfig module.

A NETCONFIG_FORCE_REPLACE=yes in /etc/sysconfig/network/config forces
to overwrite the files.

Obviously, something is not following the policy and breaks the file.
Interesting is the content of the file when it gets broken as it often
gives a hint which program is not following the rules.

Closing this bug as 13.2 is EOL, follow-up in
https://bugzilla.suse.com/show_bug.cgi?id=1083848