http://bugzilla.suse.com/show_bug.cgi?id=1166680 http://bugzilla.suse.com/show_bug.cgi?id=1166680#c6 Thorsten Kukuk <kukuk@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #6 from Thorsten Kukuk <kukuk@suse.com> --- (In reply to William Brown from comment #2)
It seems like that's a potential hiccup that can happen though, many people will have a /etc/nsswitch they'll push from a config management system, and will blow away whatever settings are there to adjust for this /etc/services business. Maybe a better or more transparent solution can be found?
We have a transparent, working solution. But if you overwrite the file afterwards with an outdated version, there is nothing we can do. This is Ok on openSUSE Leap or SLE, were we try to maintain compatibility and try to avoid such breakage during one release (but not with SP or major version updates), but with an rolling release distribution like Tumbleweed you need to expect such a breakage with every release and you need to adjust your configuration. Or fix your ansible setup to not overwrite nsswitch.conf with an outdated version, but only to modify the entries you want to change. -- You are receiving this mail because: You are on the CC list for the bug.