From Dick.Waite at softwareag.com Wed Apr 1 01:12:14 2015 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Wed, 1 Apr 2015 07:12:14 +0000 Subject: [sles-beta] Registration Issues Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DBD68AEB6@hqmbx6.eur.ad.sag> Grand New April, It looks from the png attached I should be able to get access to the updates, but I get nags to go register. Could be the Beta, I?m on Beta-3 has another way of checking updates. Maybe we should not be checking for updates, but then how does one check the checking for updates is doing it?s thing? No this is not an April 1st joke, inquiring minds would like to know, not mine the chap who pays me. Have you all a very good day. __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: snapshot6.png Type: image/png Size: 971364 bytes Desc: snapshot6.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: snapshot8.png Type: image/png Size: 42970 bytes Desc: snapshot8.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: snapshot9.png Type: image/png Size: 42861 bytes Desc: snapshot9.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: snapshot10.png Type: image/png Size: 189063 bytes Desc: snapshot10.png URL: From fcrozat at suse.com Thu Apr 2 07:38:16 2015 From: fcrozat at suse.com (Frederic Crozat) Date: Thu, 02 Apr 2015 15:38:16 +0200 Subject: [sles-beta] Registration Issues In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DBD68AEB6@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DBD68AEB6@hqmbx6.eur.ad.sag> Message-ID: <1427981896.3578.27.camel@par-r81vxc7.par.novell.com> Le mercredi 01 avril 2015 ? 07:12 +0000, Waite, Dick a ?crit : > Grand New April, > > > > It looks from the png attached I should be able to get access to the > updates, but I get nags to go register. Could be the Beta, I?m on > Beta-3 has another way of checking updates. Maybe we should not be > checking for updates, but then how does one check the checking for > updates is doing it?s thing? Right now, there is no update available at all on SP4 Update channel, that might be why you are getting this error. I've tested and I don't get any issue, so it could also be a temporary hickup on NCC side. Do you still have the issue ? -- Frederic Crozat Project Manager Enterprise Desktop SUSE From lukas.ocilka at suse.com Fri Apr 3 01:22:36 2015 From: lukas.ocilka at suse.com (Lukas Ocilka) Date: Fri, 03 Apr 2015 09:22:36 +0200 Subject: [sles-beta] Registration Issues In-Reply-To: <1427981896.3578.27.camel@par-r81vxc7.par.novell.com> References: <46AC8C81C10B8C48820201DF2AE1D76DBD68AEB6@hqmbx6.eur.ad.sag> <1427981896.3578.27.camel@par-r81vxc7.par.novell.com> Message-ID: <551E3FBC.9050508@suse.com> On 2.4.2015 15:38, Frederic Crozat wrote: > Le mercredi 01 avril 2015 ? 07:12 +0000, Waite, Dick a ?crit : >> Grand New April, >> >> >> >> It looks from the png attached I should be able to get access to the >> updates, but I get nags to go register. Could be the Beta, I?m on >> Beta-3 has another way of checking updates. Maybe we should not be >> checking for updates, but then how does one check the checking for >> updates is doing it?s thing? > > Right now, there is no update available at all on SP4 Update channel, > that might be why you are getting this error. > > I've tested and I don't get any issue, so it could also be a temporary > hickup on NCC side. > > Do you still have the issue ? Frederic, I've seen those attached screenshots and they clearly say: Permission to access https://nu..../(patterns|repomd).xml denied That would actually mean that error 404 (not found) could be evaluated as 401 unauthorized. Either in Yast or maybe even in NCC. My explanation would be similar to Frederic's: Empty update repository as there is nothing to show yet. But from my SUSE POV, we should always make sure that the repository contains at least all the mandatory files. So, Dick, if you still have these issues, please report them and attach Yast logs if possible. See https://en.opensuse.org/openSUSE:Report_a_YaST_bug for more info. Thank you. Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux