[Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages

[Lenhardt, Matthias]

Hi Spacewalkers,

anybody syncing SLES 12 SP3 Repos?

I am successfully syncing SLES 12 Repos since SLES 12 was released with the method recently fabulous described by Bernd Helber (Hi Bernd!), but now I have a weird Problem with SP3.

E.g. syncing of 2916 packages out of 3725 of the "OS Pool" repo works, but with 809 packages download fails with error "ERROR: Download failed: https://updates.suse.com/... - [Errno 14] HTTPS Error 403 - Forbidden."

Looking with a browser into the repo is indeed showing all 2916 Packages, but not the missing 809 ones.

By the way we have a valid support contract and connecting a client directly to the SUSE repos over the internet is working perfectly. And my Spacewalk release is 2.7 on CentOS 7.

Thanks in advance!

Mit freundlichen Grüßen

Matthias Lenhardt
System Administrator

BITMARCK Beratung GmbH
Firmensitz: Putzbrunner Straße 93, 81739 München
Geschäftsführer: Christian Niklaus
Registergericht: Amtsgericht München HRB 130163

*****************************************************************

Die Information in dieser E-Mail ist vertraulich und ausschließlich für
den/die benannten Adressaten bestimmt. Ein Zugriff auf diese E-Mail
durch andere Personen als den/die benannten Adressaten ist nicht
gestattet. Sollten Sie nicht der benannte Adressat sein, löschen Sie bitte
diese E-Mail.

[http://postmaster.bitmarck.de/images/weihnachten_2017_e-mail_abbinder.jpg]

[Flores, Javier (D4\\INF\\IT ID)]

Hi Matthias,

I am syncing SLES 12 repos on a daily basis. No problems so far, I get all the 3725 packages.

What I did was to first set up a SLES 12 SP3 VM and register it directly to Suse. I then used "zypper lr --uri" to get the URI which contains the token and copied that to the "Repository URL" field in Spacewalk.
Regards,
Javier


Von: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] Im Auftrag von Lenhardt, Matthias
Gesendet: Donnerstag, 14. Dezember 2017 15:59
An: spacewalk-***@redhat.com
Betreff: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages

Hi Spacewalkers,

anybody syncing SLES 12 SP3 Repos?

I am successfully syncing SLES 12 Repos since SLES 12 was released with the method recently fabulous described by Bernd Helber (Hi Bernd!), but now I have a weird Problem with SP3.

E.g. syncing of 2916 packages out of 3725 of the "OS Pool" repo works, but with 809 packages download fails with error "ERROR: Download failed: https://updates.suse.com/... - [Errno 14] HTTPS Error 403 - Forbidden."

Looking with a browser into the repo is indeed showing all 2916 Packages, but not the missing 809 ones.

By the way we have a valid support contract and connecting a client directly to the SUSE repos over the internet is working perfectly. And my Spacewalk release is 2.7 on CentOS 7.

Thanks in advance!

Mit freundlichen Grüßen

Matthias Lenhardt
System Administrator

BITMARCK Beratung GmbH
Firmensitz: Putzbrunner Straße 93, 81739 München
Geschäftsführer: Christian Niklaus
Registergericht: Amtsgericht München HRB 130163

*****************************************************************

Die Information in dieser E-Mail ist vertraulich und ausschließlich für
den/die benannten Adressaten bestimmt. Ein Zugriff auf diese E-Mail
durch andere Personen als den/die benannten Adressaten ist nicht
gestattet. Sollten Sie nicht der benannte Adressat sein, löschen Sie bitte
diese E-Mail.

[http://postmaster.bitmarck.de/images/weihnachten_2017_e-mail_abbinder.jpg]

[Lenhardt, Matthias]

Hi Javier,

this is what I did, too. Strange ...

Mit freundlichen Grüßen

Matthias Lenhardt
System Administrator

Von: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] Im Auftrag von Flores, Javier (D4\INF\IT ID)
Gesendet: Donnerstag, 14. Dezember 2017 17:18
An: 'spacewalk-***@redhat.com' <spacewalk-***@redhat.com>
Betreff: Re: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages

Hi Matthias,

I am syncing SLES 12 repos on a daily basis. No problems so far, I get all the 3725 packages.

What I did was to first set up a SLES 12 SP3 VM and register it directly to Suse. I then used "zypper lr --uri" to get the URI which contains the token and copied that to the "Repository URL" field in Spacewalk.

Regards,
Javier


Von: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] Im Auftrag von Lenhardt, Matthias
Gesendet: Donnerstag, 14. Dezember 2017 15:59
An: spacewalk-***@redhat.com
Betreff: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages

Hi Spacewalkers,

anybody syncing SLES 12 SP3 Repos?

I am successfully syncing SLES 12 Repos since SLES 12 was released with the method recently fabulous described by Bernd Helber (Hi Bernd!), but now I have a weird Problem with SP3.

E.g. syncing of 2916 packages out of 3725 of the "OS Pool" repo works, but with 809 packages download fails with error "ERROR: Download failed: https://updates.suse.com/... - [Errno 14] HTTPS Error 403 - Forbidden."

Looking with a browser into the repo is indeed showing all 2916 Packages, but not the missing 809 ones.

By the way we have a valid support contract and connecting a client directly to the SUSE repos over the internet is working perfectly. And my Spacewalk release is 2.7 on CentOS 7.

Thanks in advance!

Mit freundlichen Grüßen

Matthias Lenhardt
System Administrator

BITMARCK Beratung GmbH
Firmensitz: Putzbrunner Straße 93, 81739 München
Geschäftsführer: Christian Niklaus
Registergericht: Amtsgericht München HRB 130163

*****************************************************************

Die Information in dieser E-Mail ist vertraulich und ausschließlich für
den/die benannten Adressaten bestimmt. Ein Zugriff auf diese E-Mail
durch andere Personen als den/die benannten Adressaten ist nicht
gestattet. Sollten Sie nicht der benannte Adressat sein, löschen Sie bitte
diese E-Mail.

[Das Bild wurde vom Absender entfernt.]
[http://postmaster.bitmarck.de/images/weihnachten_2017_e-mail_abbinder.jpg]

[Daryl Rose]

Javier,


I'm also trying to setup a SLES 12 SP3 repo sync.


I also have a registered SLES 12 SP3 and I copied/pasted the "zypper lr --uri" into the repository URL field as you suggest.


I get an error that the sync can't retrieve repository metadata.


ERROR: Cannot retrieve repository metadata (repomd.xml)

I can put that URL in my browser and see the repository, but I can't get the sync to work in SW.

Am I missing something?

Thanks

Daryl

________________________________
From: spacewalk-list-***@redhat.com <spacewalk-list-***@redhat.com> on behalf of Flores, Javier (D4\INF\IT ID) <***@gmz.migros.ch>
Sent: Thursday, December 14, 2017 10:18 AM
To: 'spacewalk-***@redhat.com'
Subject: Re: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages


Hi Matthias,



I am syncing SLES 12 repos on a daily basis. No problems so far, I get all the 3725 packages.



What I did was to first set up a SLES 12 SP3 VM and register it directly to Suse. I then used “zypper lr --uri” to get the URI which contains the token and copied that to the “Repository URL” field in Spacewalk.

Regards,

Javier





Von: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] Im Auftrag von Lenhardt, Matthias
Gesendet: Donnerstag, 14. Dezember 2017 15:59
An: spacewalk-***@redhat.com
Betreff: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages



Hi Spacewalkers,



anybody syncing SLES 12 SP3 Repos?



I am successfully syncing SLES 12 Repos since SLES 12 was released with the method recently fabulous described by Bernd Helber (Hi Bernd!), but now I have a weird Problem with SP3.



E.g. syncing of 2916 packages out of 3725 of the „OS Pool“ repo works, but with 809 packages download fails with error „ERROR: Download failed: https://updates.suse.com/… - [Errno 14] HTTPS Error 403 - Forbidden.“



Looking with a browser into the repo is indeed showing all 2916 Packages, but not the missing 809 ones.



By the way we have a valid support contract and connecting a client directly to the SUSE repos over the internet is working perfectly. And my Spacewalk release is 2.7 on CentOS 7.



Thanks in advance!



Mit freundlichen Grüßen



Matthias Lenhardt
System Administrator



BITMARCK Beratung GmbH
Firmensitz: Putzbrunner Straße 93, 81739 München
Geschäftsführer: Christian Niklaus
Registergericht: Amtsgericht München HRB 130163



*****************************************************************



Die Information in dieser E-Mail ist vertraulich und ausschließlich für
den/die benannten Adressaten bestimmt. Ein Zugriff auf diese E-Mail
durch andere Personen als den/die benannten Adressaten ist nicht
gestattet. Sollten Sie nicht der benannte Adressat sein, löschen Sie bitte
diese E-Mail.



[http://postmaster.bitmarck.de/images/weihnachten_2017_e-mail_abbinder.jpg]

[Flores, Javier (D4\\INF\\IT ID)]

Hi,

Right, I forgot to mention that I had to manually apply this patch:

https://lists.opensuse.org/opensuse-commit/2014-09/msg01140.html

and also this one

https://github.com/spacewalkproject/spacewalk/pull/531

on the Spacewalk server to get everything working for SLES.

I am using Spacewalk 2.6 on CentOS 7.

Regards,
Javier

Von: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] Im Auftrag von Daryl Rose
Gesendet: Donnerstag, 14. Dezember 2017 20:40
An: spacewalk-***@redhat.com
Betreff: Re: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages


Javier,



I'm also trying to setup a SLES 12 SP3 repo sync.


I also have a registered SLES 12 SP3 and I copied/pasted the "zypper lr --uri" into the repository URL field as you suggest.



I get an error that the sync can't retrieve repository metadata.



ERROR: Cannot retrieve repository metadata (repomd.xml)

I can put that URL in my browser and see the repository, but I can't get the sync to work in SW.

Am I missing something?

Thanks

Daryl

________________________________
From: spacewalk-list-***@redhat.com<mailto:spacewalk-list-***@redhat.com> <spacewalk-list-***@redhat.com<mailto:spacewalk-list-***@redhat.com>> on behalf of Flores, Javier (D4\INF\IT ID) <***@gmz.migros.ch<mailto:***@gmz.migros.ch>>
Sent: Thursday, December 14, 2017 10:18 AM
To: 'spacewalk-***@redhat.com'
Subject: Re: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages


Hi Matthias,



I am syncing SLES 12 repos on a daily basis. No problems so far, I get all the 3725 packages.



What I did was to first set up a SLES 12 SP3 VM and register it directly to Suse. I then used "zypper lr --uri" to get the URI which contains the token and copied that to the "Repository URL" field in Spacewalk.

Regards,

Javier





Von: spacewalk-list-***@redhat.com<mailto:spacewalk-list-***@redhat.com> [mailto:spacewalk-list-***@redhat.com] Im Auftrag von Lenhardt, Matthias
Gesendet: Donnerstag, 14. Dezember 2017 15:59
An: spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>
Betreff: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages



Hi Spacewalkers,



anybody syncing SLES 12 SP3 Repos?



I am successfully syncing SLES 12 Repos since SLES 12 was released with the method recently fabulous described by Bernd Helber (Hi Bernd!), but now I have a weird Problem with SP3.



E.g. syncing of 2916 packages out of 3725 of the "OS Pool" repo works, but with 809 packages download fails with error "ERROR: Download failed: https://updates.suse.com/... - [Errno 14] HTTPS Error 403 - Forbidden."



Looking with a browser into the repo is indeed showing all 2916 Packages, but not the missing 809 ones.



By the way we have a valid support contract and connecting a client directly to the SUSE repos over the internet is working perfectly. And my Spacewalk release is 2.7 on CentOS 7.



Thanks in advance!



Mit freundlichen Grüßen



Matthias Lenhardt
System Administrator



BITMARCK Beratung GmbH
Firmensitz: Putzbrunner Straße 93, 81739 München
Geschäftsführer: Christian Niklaus
Registergericht: Amtsgericht München HRB 130163



*****************************************************************



Die Information in dieser E-Mail ist vertraulich und ausschließlich für
den/die benannten Adressaten bestimmt. Ein Zugriff auf diese E-Mail
durch andere Personen als den/die benannten Adressaten ist nicht
gestattet. Sollten Sie nicht der benannte Adressat sein, löschen Sie bitte
diese E-Mail.



[http://postmaster.bitmarck.de/images/weihnachten_2017_e-mail_abbinder.jpg]

[Daryl Rose]

Thank you Javier. I'll review those patches.


Daryl


________________________________
From: spacewalk-list-***@redhat.com <spacewalk-list-***@redhat.com> on behalf of Flores, Javier (D4\INF\IT ID) <***@gmz.migros.ch>
Sent: Friday, December 15, 2017 1:30 AM
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages


Hi,



Right, I forgot to mention that I had to manually apply this patch:



https://lists.opensuse.org/opensuse-commit/2014-09/msg01140.html

commit python-urlgrabber for openSUSE:Factory<https://lists.opensuse.org/opensuse-commit/2014-09/msg01140.html>
lists.opensuse.org
Hello community, here is the log from the commit of package python-urlgrabber for openSUSE:Factory checked in at 2014-09-20 15:49:54 ...




and also this one



https://github.com/spacewalkproject/spacewalk/pull/531

[https://avatars1.githubusercontent.com/u/1038917?s=400&v=4]<https://github.com/spacewalkproject/spacewalk/pull/531>

do not fail with a traceback when media.1 is requested by mcalmer · Pull Request #531 · spacewalkproject/spacewalk<https://github.com/spacewalkproject/spacewalk/pull/531>
github.com
New libzypp request media.1 directory which result in a traceback. Just returning 404 Not Found is ok.




on the Spacewalk server to get everything working for SLES.



I am using Spacewalk 2.6 on CentOS 7.



Regards,

Javier



Von: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] Im Auftrag von Daryl Rose
Gesendet: Donnerstag, 14. Dezember 2017 20:40
An: spacewalk-***@redhat.com
Betreff: Re: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages



Javier,



I'm also trying to setup a SLES 12 SP3 repo sync.



I also have a registered SLES 12 SP3 and I copied/pasted the "zypper lr --uri" into the repository URL field as you suggest.



I get an error that the sync can't retrieve repository metadata.



ERROR: Cannot retrieve repository metadata (repomd.xml)



I can put that URL in my browser and see the repository, but I can't get the sync to work in SW.



Am I missing something?



Thanks



Daryl



________________________________

From: spacewalk-list-***@redhat.com<mailto:spacewalk-list-***@redhat.com> <spacewalk-list-***@redhat.com<mailto:spacewalk-list-***@redhat.com>> on behalf of Flores, Javier (D4\INF\IT ID) <***@gmz.migros.ch<mailto:***@gmz.migros.ch>>
Sent: Thursday, December 14, 2017 10:18 AM
To: 'spacewalk-***@redhat.com'
Subject: Re: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages



Hi Matthias,



I am syncing SLES 12 repos on a daily basis. No problems so far, I get all the 3725 packages.



What I did was to first set up a SLES 12 SP3 VM and register it directly to Suse. I then used “zypper lr --uri” to get the URI which contains the token and copied that to the “Repository URL” field in Spacewalk.

Regards,

Javier





Von: spacewalk-list-***@redhat.com<mailto:spacewalk-list-***@redhat.com> [mailto:spacewalk-list-***@redhat.com] Im Auftrag von Lenhardt, Matthias
Gesendet: Donnerstag, 14. Dezember 2017 15:59
An: spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>
Betreff: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages



Hi Spacewalkers,



anybody syncing SLES 12 SP3 Repos?



I am successfully syncing SLES 12 Repos since SLES 12 was released with the method recently fabulous described by Bernd Helber (Hi Bernd!), but now I have a weird Problem with SP3.



E.g. syncing of 2916 packages out of 3725 of the „OS Pool“ repo works, but with 809 packages download fails with error „ERROR: Download failed: https://updates.suse.com/… - [Errno 14] HTTPS Error 403 - Forbidden.“



Looking with a browser into the repo is indeed showing all 2916 Packages, but not the missing 809 ones.



By the way we have a valid support contract and connecting a client directly to the SUSE repos over the internet is working perfectly. And my Spacewalk release is 2.7 on CentOS 7.



Thanks in advance!



Mit freundlichen Grüßen



Matthias Lenhardt
System Administrator



BITMARCK Beratung GmbH
Firmensitz: Putzbrunner Straße 93, 81739 München
Geschäftsführer: Christian Niklaus
Registergericht: Amtsgericht München HRB 130163



*****************************************************************



Die Information in dieser E-Mail ist vertraulich und ausschließlich für
den/die benannten Adressaten bestimmt. Ein Zugriff auf diese E-Mail
durch andere Personen als den/die benannten Adressaten ist nicht
gestattet. Sollten Sie nicht der benannte Adressat sein, löschen Sie bitte
diese E-Mail.



[http://postmaster.bitmarck.de/images/weihnachten_2017_e-mail_abbinder.jpg]

[Lenhardt, Matthias]

Important hint:

Looking deaper into the error message. I found a possible error within the path part of the download URL (Sorry, for not doing that earlier):

ERROR: Download failed: https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/x86_64/grep-2.16-3.1.x86_64.rpm - [Errno 14] HTTPS Error 403 - Forbidden.

There are two directories "x86_64/" in series. It seems, it should be "x86_64/product/x86_64". Using this corrected URL I'm finding the missing packages using a browser.

Spacewalk Repo URL for SLES 12 SP3 OS pool is https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product?<suse_token>

Regards

Matthias Lenhardt
System Administrator
[http://postmaster.bitmarck.de/images/weihnachten_2017_e-mail_abbinder.jpg]

[Lenhardt, Matthias]

Important hint, part 2:

Solved the issue with the path myself by adding a slash between the repo URL and the SuSE token:

https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product/?<suse-token<https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product/?%3csuse-token>> (Note the / after ...product and before ?<suse-token>)

But unfortunatelly this didn't solve the problem. Now the URLs in the spacewalk-repo-sync logfile are correct, but access is still forbidden:

"... ERROR: Download failed: https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product/x86_64/grep-2.16-3.1.x86_64.rpm - [Errno 14] HTTPS Error 403 - Forbidden."

Again, downloading the "grep" RPM with a browser is working.

Could it be, that for some RPMs the suse-token is not added to the download url?

Regards
Matthias
[http://postmaster.bitmarck.de/images/weihnachten_2017_e-mail_abbinder.jpg]