[Spacewalk-list] Syncing with SLES for SAP repos

[Sadri, Wafa (BITBW)]

Dear Paul-Andre,

coincidentally I'm having a very similar issue. We fixed this issue in 2.7 and it's now back because SW has fundamentally changed the way it syncs repos (either from 2.7 to 2.8 or 2.8 to 2.9 - not sure yet). Either way, the problem - afaik - seems to be that the download.py file (in which we implemented the fix) doesn't get called until later in the sync/download process. The error though occurs before this python script is called, resulting in the problem you and I are having. So far I haven't yet figured out a way to fix this. At the moment I'm looking into the reposync.py file as I'm suspecting the error to be caused here. 

best regards,
Wafa

-----Ursprüngliche Nachricht-----
Von: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] Im Auftrag von Paul-Andre Panon
Gesendet: Dienstag, 9. April 2019 21:49
An: spacewalk-list at redhat.com
Betreff: [Spacewalk-list] Syncing with SLES for SAP repos

Hi,

We're running Spacewalk 2.9 with Ubuntu and CentOS clients. I have been asked to also set up some of our SUSE servers to patch through Spacewalk.
I saw the older thread about "SUSE tokens broken since Spacewalk 2.7", and thus used the trick of prefixing the user/password used by the SUSE clients before the server name in the URL. That works fine for the SLES and SLES HAE repos, but it's not working for the SLES for SAP repos - I get a 403 error instead. Is the token approach fixed in Spacewalk 2.9 and should I go back to that technique? Or am I stuck when it comes to the SLES for SAP repositories?

Thanks,

Paul-Andre Panon

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list