Bug 227059

Summary:	Autoregistration of update source
Product:	[openSUSE] openSUSE 10.3	Reporter:	Dominique Leuenberger <dimstar>
Component:	Installation	Assignee:	Ladislav Slezák <lslezak>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	jdsn, mc
Version:	Beta 2
Target Milestone:	unspecified
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	the whole /var/log/YaST2 directory

Description Dominique Leuenberger 2006-12-08 10:46:48 UTC

I've installed openSUSE 10.2 behind a quiet restrictive firewall, FTP is denied.

During the setup, yast was advised to use a http proxy and the internet test succeeded.

While adding an FTP Update source, this failed, but no visible feedback was reported and no backfalling to http was done.

Thus, without a visual note about this and no other retries, I have no update source registered in the system.

Suggestion: (probably onle for 10.3?): Fall back to a http source (especially, as the internet connection test verifies http), and if this fails too, give visual feedback, so the user KNOWS that something did not happen correctly.

Yast Logs will be appended afterwards.

Comment 1 Dominique Leuenberger 2006-12-08 10:49:24 UTC

Created attachment 108822 [details]
the whole /var/log/YaST2 directory

Comment 2 Michal Zugec 2007-01-30 10:24:23 UTC

Jirko, I think it's not bad idea to backfall to http when ftp failed

Comment 3 Jiří Suchomel 2007-01-30 10:35:40 UTC

Using http instead of ftp is strange and I don't think we should do this when user was adding FTP source.

The information about no online update source available should be shown, this is already described in some feature (I don't remember the id right now).

Comment 4 Dominique Leuenberger 2007-01-30 10:39:04 UTC

I don't agree with 'invalid' here.

Nobody choose FTP or another protocol during the installation and auto registration of an update source. In fact: no question is asked, no dialog is prompted... 

so why should a fallback in this case be invalid?

Comment 5 Jiří Suchomel 2007-01-30 10:40:35 UTC

If you mean the case of automatically added online-update source, this is a task for yast2-registration or the tools under it.

Comment 6 Dominique Leuenberger 2007-01-30 10:42:07 UTC

Indeed, that is the point I was talking about... I seem to have forgotten to mention this in the initial report.

Comment 7 Dominique Leuenberger 2007-08-31 08:36:13 UTC

I'm wondering if there happened something about this in the last 7 month; should I test it again and hope that it got accidentially fixed for 10.3?

Comment 8 J. Daniel Schmidt 2007-08-31 16:17:45 UTC

If no repository was added the registration module will show a message.
This has been implemented into 10.3 already.

The automatic fallback from ftp to http is nothing the registration may handle (it is only a workflow). This is a job for the Source Manager.

(moving bug from 10.2 to 10.3)

Comment 9 Ladislav Slezák 2007-09-03 08:57:04 UTC

HTTP fallback for FTP has been added in yast2-packager-2.15.72