Bug 485891

Summary: Registering and online update configuration fails
Product: [openSUSE] openSUSE 11.1 Reporter: Hendrik Müller <poolbarde>
Component: YaST2Assignee: J. Daniel Schmidt <jdsn>
Status: RESOLVED WONTFIX QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P4 - Low CC: jdsn, mantel, poolbarde
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: yast2 log

Description Hendrik Müller 2009-03-17 08:03:35 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1.6 Firefox/3.0.7

On a fresh and up to date openSUSE 11.1 I have deleted all repositories. Then I added the oipenSUSE 11.1 installation DVD and commertiona software add-on CD. Now, I tried 'Setting up online update'. When starting registration I have selected 'Configure now', 'Hardware Profile' and 'optinal information'. Now I click on 'next'.
Now, message box appears:
   Yast2: Fehler
   Beim Verbindungsaufbau mit dem Server ist ein Fehler aufgetreten

Free translation of german error description:
   Yast2: Error
   An error occured  during setup of connection to server.

After that error, no repositories are added and no more updates are possible.

Note: The PC uses a proxy with authentication for accessign internet. Proxy settings are configured and working.

Reproducible: Always

Steps to Reproduce:
1.Delete all software repsoitories.
2.Install PC behind proxy that uses authentication.
3.Try to setup online-update
Actual Results:  
Connection to server not possible

Expected Results:  
Default repositories are added for update openSUSE 11.1 installation.
Comment 1 Hendrik Müller 2009-03-18 10:13:02 UTC
Created attachment 280247 [details]
yast2 log

I have created a yast2 log on a fresh installed opensuse 11.1 after applying all available updates. This time i did not touch the default repositories that are configured. I just clicked on 'Online Update Configuration'  and then select 'Advance -> Register for support and get update repository'. After clicking on 'next' on registration page (the one where you can select 'Configure Now' the following error is shown:
  Error
  An error occured while connection to the server
 Details page show:
  Cannot contact the registration server. Request failed.

Note: PC uses proxy with authentication for accessing internet.
Comment 2 Hendrik Müller 2009-03-19 06:56:41 UTC
Additional note: If that issue is realted to proxy, please take into account, that the authentication name is of format 'domain/user'. Due to policy i needed to exchange original user by some fake and i forgot to mention the /.
Comment 3 Hendrik Müller 2009-03-19 06:57:16 UTC
Sorry: Due to policy i needed to exchange original user in the yast2 logs by some fake and i forgot to mention the /.
Comment 4 Hubert Mantel 2009-03-23 14:48:58 UTC
Seems proxy authentication has a bug. So I will flag this one as duplicate. Hendrik, if you can confirm that the problem does not exist without proxy, please re-open.

*** This bug has been marked as a duplicate of bug 486998 ***
Comment 5 J. Daniel Schmidt 2009-03-23 14:58:18 UTC
Hubert, this rather looks like a duplicate of bug #410750.
Comment 6 Hubert Mantel 2009-03-23 15:30:58 UTC
I see. Thanks. Might this even be the case for #486998 then?
Comment 7 J. Daniel Schmidt 2009-03-23 16:08:33 UTC
(In reply to comment #6)
> Might this even be the case for #486998 then?

I doubt it. This looks like something different.
Comment 8 Hendrik Müller 2009-03-28 00:42:13 UTC
I can confirm:
Problem still exists behind proxy. Second PC without proxy does NOT have the problem.
Comment 9 Hendrik Müller 2009-03-30 05:45:35 UTC
After updating the repositories still following error occured on my PC behind the Proxy:
    Cannot contact the registration erver. Request fails.
Comment 10 Hendrik Müller 2009-03-30 05:46:43 UTC
Sorry, last status change was mistake.
Comment 13 J. Daniel Schmidt 2009-04-06 15:57:50 UTC
The proxy handling of the registration in openSUSE 11.1 seems to contain a bug that was fixed later for SLE11 [1] and also trunk [2] but after the release of openSUSE 11.1. The proxy settings are read but passed to suseRegister (the tool that communicates with the registration server) too late.

[1] http://lists.opensuse.org/yast-commit/2009-01/msg00755.html
[2] http://lists.opensuse.org/yast-commit/2009-01/msg00877.html

It is paradox to offer an online update for this, as the aim of the registration module on openSUSE only is, to setup an update source in case you don't have one, because you deleted it. But if you don't have an update source then how should an online update be deployed?

So, unfortunately I must say that it is hard fix this :-/
If it is just for one machine I'd recommend to use "Software Repositories"->"Add"->"Community Repos" and select the update repo or to add the default update repo [3] manually.

[3]: http://en.opensuse.org/Package_Repositories#Update

If you need the functionality to register lots of machines that way then I can provide a fixed yast2-registration via a build service project. You could add this package as an Add-On product or include is as a driverupdate during installation.

I will close this bug as WONTFIX for now as I can not see any sense in fixing that kind of bug via an online update. But please feel free to reopen the bug to request an updated package for 11.1 via the build service.
Comment 14 Hendrik Müller 2009-04-07 16:35:34 UTC
Will this change also be included into the opensue 11.1 repository (the one which is used by the downloadable opensuse 11.1 DVD vereison)?
Comment 15 J. Daniel Schmidt 2009-04-07 18:25:34 UTC
openSUSE 11.1 is released and thus theses repos will not change. We provide updates only via the online update repository.

But the package that the build service can create will be built for openSUSE 11.1, if you meant that. But anyhow you have to add that specific repository manually to your machine.
And thats the paradox - if you manually add a repo then you could add the default update repo in the first place.
Comment 16 Hendrik Müller 2009-04-09 07:23:48 UTC
Yes, I meant the update repository. Currently I have added  the sle11 repository mentioned above to get this update. My questions is, if that patch will be added to the standardss opensuse 11.1 update repository too?
Comment 17 J. Daniel Schmidt 2009-04-09 16:38:07 UTC
(In reply to comment #16)
> Currently I have added  the sle11 repository mentioned above to 
> get this update.

Yes, that is another option and should just work fine :)

> My questions is, if that patch
> will be added to the standardss opensuse 11.1 update repository too?

Thats what I tried to explain above. Ok, so again:
It makes no sense to release an online update for this. The only aim of the registration module in openSUSE is to get an update repository.
_But_:
1. The update repository is already added during installation.
2. You can add it via "Software Repositories" via "Community Repos".
3. You can add it manually by entering the URL you can find on the page linked in comment #3
4. The only aim of the YaST registration module in openSUSE is, to get and set up an update repository. BUT, to get this update you need to have an update repository. Thus it makes the update itself useless. So, no I will not release an online update for this as it is useless.

What I offered was a package in a build service project (for you and everybody who might be interested).
Comment 18 Hendrik Müller 2009-04-10 05:08:47 UTC
Yes, I understood you argumentation. But think of this situation:
1. I got all updates.
2. Later I tried to reconfigure online updates, but I fail, and my updates are gone.
3. Now i have to enter everything by hand. And hopefully I'm still aware which repositories I need (there are several installed by default).

If I already got the update, this will be easy, without it it's much more work.
Anyhow, I do not want to understand why you're not adding it, I'm just wondering...
Comment 19 J. Daniel Schmidt 2009-04-14 11:43:16 UTC
See comment #17 point 2