Bug 223893

Summary:	Possible deadlock in installation source module
Product:	[openSUSE] openSUSE 10.2	Reporter:	Marcel Hilzinger <marcel>
Component:	YaST2	Assignee:	Ladislav Slezák <lslezak>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None
Version:	RC 1
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Marcel Hilzinger 2006-11-27 15:14:32 UTC

In 10.2 the inistallation source module checks for all sources before it starts. This is

a) slow
b) unneccessary
c) dangerous

I just wanted to remove ftp.suse.com as online update source. As the server was not responding (high load as always), the module did not start. This is contraproductive:

If you want to change a source, because it's not reachable, you cannot do it within YaST, because YaST cannot reach it nighter.

Comment 1 Matej Horvath 2006-11-27 19:10:13 UTC

Please attach your yast logs. They might be useful for the maintainer.
http://en.opensuse.org/Bugs/YaST

Thank you.

Comment 2 Marcel Hilzinger 2006-11-27 19:37:24 UTC

Good joke man. If you need logs, you did not understand the problem:

If you start the installation source module, YaST tries to fetch informations for all existing installation sources.
If one of the servers is not reachable (for what reason ever), YaST waits and waits and waits forever.
So how to change the installation sources within YaST?

That's the problem.

Comment 3 Stefan Hundhammer 2006-11-28 10:26:26 UTC

That's not critical.

IIRC it times out after some (very long, agreed) time.
And I think (not sure, though) it behaves like that only if you selected "autorefresh" for those sources. In that case, it does just what it was asked to do: Refresh the sources. I am not sure if the point in time to do that (upon startup of the inst source module) is so great, though.

Comment 4 Marcel Hilzinger 2006-11-28 11:04:36 UTC

I waited for at least 15 minutes, then I killed YaST. So timeout is far too long).

Why I think it's at least major: On 3 of my test machines, YaST set up ftp.suse.com as repository for online updates. As we all know, after a new release, ftp.suse.com cannot handle so many users. So YaST will just block every work on installation sources.

If for 10.2 ftp.suse.com could be excluded from the update source list, it would be just a normal bug.

Comment 5 Ladislav Slezák 2006-11-29 13:15:57 UTC


*** This bug has been marked as a duplicate of bug 223600 ***