Bug 132463

Summary:	yast packagemanager checks for nfs shares whereas all nfs sources have been removed
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Gilles Sabourin <sabourin.gilles>
Component:	YaST2	Assignee:	Michael Andres <ma>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	32bit
OS:	Linux
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2log log with (1) nfs server down and (2) nfs server up

Description Gilles Sabourin 2005-11-05 10:44:04 UTC

I have set up a nfs server on my files server for a specific need, as I couldn't use a SMB source as installation source (See also #132461).

This time, I could add a new nfs installation source and update my packages. Next, I removed the nfs installation source from the list, and I stopped my NFS server.

Whenever I relaunched yast2 packagemanager, I got a blank list with a watch mouse cursor. I have to start nfs server again to be unlocked.

See the yast2 log in the following attachment.

Comment 1 Gilles Sabourin 2005-11-05 10:57:54 UTC

Created attachment 56547 [details]
y2log log with (1) nfs server down and (2) nfs server up

test 1 : nfs server down. yast packamanger is locked during cache access (see around line 491)

test 2 : nfs server up. yast packamanger cannot remove 15 packages from cache since it performs an access through read only nfs mount point.

Comment 2 Gilles Sabourin 2005-11-05 10:59:40 UTC

Comment on attachment 56547 [details]
y2log log with (1) nfs server down and (2) nfs server up

for test2, see around line 954

Comment 3 Gilles Sabourin 2005-11-05 11:09:04 UTC

I have a look myself in yast logs. I have to remount nfs share with read/write access option to get rid of this problem.

This can be a workaround only if you can access yourself to the server or ask to the server admin. For security reasons, your server admin may refuse write access to the nfs shares. Then, you can't have access anymore to packagemanager.

Comment 5 Michael Andres 2005-11-15 14:21:59 UTC

Looks like there are two broken cache directories:

 /var/adm/YaST/InstSrcManager/IS_CACHE_0x00000002
 /var/adm/YaST/InstSrcManager/IS_CACHE_0x0000000c

Both do not conatin a DESCRIPTION/description file, thus they are not usable. But YaST fails to get rid of them.

-

YaST didn't mount the nfs share below /IS_CACHE_0x00000002/MEDIA. In fact it can't, bause the description file, which contains the URL is not present. 

It looks like some previous run failed to unmount IS_CACHE_0x00000002/MEDIA. And now YaST is not aware at all, that something is mounted there. It just tries to cleanup. Quite dangerous situation ;(


[Gilles]
If this persisits, please stop YaST and manually unmount var/adm/YaST/InstSrcManager/IS_CACHE_0x00000002/MEDIA. Then remove the IS_CACHE_0x00000002 directory.

Comment 6 Michael Andres 2007-01-22 14:52:12 UTC

Should not happen with libyzpp / 10.1.