Bug 809271

Summary:	ypserv maps get removed by upgrade
Product:	[openSUSE] openSUSE 12.3	Reporter:	Robert Schweikert <rjschwei>
Component:	Basesystem	Assignee:	E-mail List <bnc-team-screening>
Status:	VERIFIED NORESPONSE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Robert Schweikert 2013-03-13 22:56:40 UTC

I upgraded my NIS server from openSUSE 12.2 to openSUSE 12.3 using zypper dup. After the upgrade ypserv was running, but he maps had been lost. I had to run "make" in /var/yp/. Users should not have to repopulate the due to an upgrade.

Expected behavior:
ypserv functions as before the upgrade

Problem:
user has to rebuild the maps running make in /var/yp/

Comment 1 Thorsten Kukuk 2013-04-19 09:50:21 UTC

There is absolute no code in ypserv.spec file which would remove ypserv maps. And that wouldn't even be possible at all, as there is no way to find out where maps are stored.

Are you absolute sure that this happened during 12.2 -> 12.3 migration? What's in the log files?

Comment 2 Robert Schweikert 2013-04-19 12:36:27 UTC

Yes, I am absolutely certain this happened during migration. NIS was working before I ran zypper dup and was broken right after. It took me a while to figure out that I had to rebuild the maps.

I didn't see anything interesting in the log file (messages) other than my feeble attempts of restarting the service.

Maybe there is something that the new systemd logging service would reveal, but I am not yet sufficiently familiar with this to extract useful information.

Comment 3 Thorsten Kukuk 2013-04-30 06:33:02 UTC

I'm not able to reproduce and it is not the ypserv package who deletes the files.

Comment 4 Fei Xiang Zhang 2013-07-25 07:45:38 UTC

Hi Robert,
could you provide /var/log/zypper.log ?

Comment 5 Fei Xiang Zhang 2013-08-14 09:50:41 UTC

please feel free to reopen the bug if you can provide the needed information,thanks.