Bug 388039

Summary:	Dowload error message during setup that could be suppressed when no network is available.
Product:	[openSUSE] openSUSE 11.0	Reporter:	Forgotten User CxVz4LpaB5 <forgotten_CxVz4LpaB5>
Component:	Installation	Assignee:	Lukas Ocilka <locilka>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	casualprogrammer, gandolfo17
Version:	Beta 2
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User CxVz4LpaB5 2008-05-08 00:51:48 UTC

During the setup, the user have the choice to manage its network configuration using network manager or ifup. For the fun, I have selected ifup, but that does not work. That's not a real issue since I can use network manager.

The problem is that later in the setup. at then end (maybe online update) an error message is displayed:
' Cannot access installation media (media 1)
Check whatever the service is accessible
url : http://download.opensuse.org/update/11.0
download (curl) error for http://download.opensuse.org/update/11.0
error code
error message : couldn't resolve download,opensuse.org'

It seems that there is no check done to be sure that the setup is able to go on the internet or not so come this error message.

- Could the error message be changed to something less 'system' like : 'Setup cannot contact the url for downloading the update, check your network configuration or try again when the setup is completed' (with a more info button'
- Could this error message have a timer (see #384402)
- Maybe a message box to make the user goes back to the network configuration? That could be nice!

Thanks

Comment 1 Stephan Kulow 2008-05-08 06:20:08 UTC

I don't think it's possible to reliable detect network setup failed. So unless there is some way I did not think of, this is WONTFIX.

Comment 2 Jiří Suchomel 2008-05-12 12:09:29 UTC

AFAIK the message comes from the package callbacks.

Comment 3 Ladislav Slezák 2008-05-12 13:52:20 UTC

Lukas, the update source probably should not be added when there is no network.

Comment 4 Lukas Ocilka 2008-05-12 13:54:20 UTC

Well, we could add it disabled (as the other repositories) if there is no network running...

Comment 5 Ladislav Slezák 2008-06-02 10:28:54 UTC

*** Bug 395740 has been marked as a duplicate of this bug. ***

Comment 6 Michal Zugec 2008-06-03 11:00:10 UTC

*** Bug 396123 has been marked as a duplicate of this bug. ***

Comment 7 Ladislav Slezák 2008-06-03 11:05:57 UTC

In running system you can avoid the error messages by disabling the remote repositories manually.

Comment 8 Casual J. Programmer 2008-06-03 11:17:07 UTC

Not sure why Bug 396123 should be a duplicate of this bug, Bug 396123 is about yast2 lan accessing repositories, although there is _no_ reason for it. Please review.

Comment 9 Lukas Ocilka 2008-07-24 10:53:51 UTC

- Making possible to upgrade running system using YaST Update even
  if it changes a release (the original/current installation
  repository must be present).
- yast2-update-2.17.0

Supported scenario:

  * Do not remove your installation repository (the one you've used
    to install the current product.
  * Add a new repository (FACTORY, for instance)
  * Run `yast2 update`
  * You will probably have to solve conflicts...

Anyway, works now ...

Comment 10 Lukas Ocilka 2008-07-24 11:03:23 UTC

- Making possible to upgrade running system using YaST Update even
  if it changes a release (the original/current installation
  repository must be present).
- yast2-update-2.17.0

Supported scenario:

  * Do not remove your installation repository (the one you've used
    to install the current product.
  * Add a new repository (FACTORY, for instance)
  * Run `yast2 update`
  * You will probably have to solve conflicts...

Anyway, works now ...