Bug ID 1090915
Summary Installer ports yp.conf, which overrides subsequent YaST NIS changes
Classification openSUSE
Product openSUSE Distribution
Version Leap 15.0
Hardware x86-64
OS SUSE Other
Status NEW
Severity Minor
Priority P5 - None
Component Network
Assignee bnc-team-screening@forge.provo.novell.com
Reporter jcholewa@northwell.edu
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/64.0.3282.189 Safari/537.36 Vivaldi/1.95.1077.60
Build Identifier: 

The Leap 15 Beta installer seems to copy /etc/yp.conf from prior installs, but
the YaST NIS Client module in my 15.0 build -- kernel 4.12.14-lp150.8-default
#1 SMP Sat Apr 7 05:12:52 UTC 2018 (8719fc4) -- sets the NIS server elsewhere
(looks like in /etc/sysconfig/network/config).  ypbind seems to check
/etc/yp.conf first, so the NIS server is not the one specified by YaST. 
Command like ypwhich report "Error for domain 'mydomain' from ypbind on
'localhost': Domain not bound".  This issue persists through reboots.

Curiously, after the initial set up in YaST but before the first subsequent
reboot, ypbind *does* recognize the value set by YaST, but something is
confused as programs like id and chown fail with "no such user" messages.

In the end, the problem only goes away if /etc/yp.conf is manually modified. 
It seems likely that removing the file entirely would likely have fixed the
problem, as well.


Reproducible: Didn't try

Steps to Reproduce:
1. Install Leap 15.0 and import settings from prior version of openSUSE (or
just copy old /etc/yp.conf to new install
2. Enter YaST NIS Client and change NIS server host/IP
3. Reboot
4. Run ypwhich to test which server is used
Actual Results:  
ypwhich reports server specified in /etc/yp.conf

Expected Results:  
ypwhich reports server specified by YaST NIS Client

A) Instead of copying /etc/yp.conf from old install, 15.0 installer perhaps
should have entered the relevant value into /etc/sysconfig,

B) YaST NIS Client should have removed or commented out any obsoleted entries
from /etc/yp.conf and replaced them with the new server host/IP.


You are receiving this mail because: