
El 1/6/20 a las 15:43, Pau Garcia Quiles escribió:
With 2020.05 we receive the following error message:
Sync of channel started. Get metadata from repository 'oes2018-sp2-sles12-sp5-pool-x86_64' ................................. ................................................. [ Error] Repository 'oes2018-sp2-sles12-sp5-pool-x86_64' is invalid. [oes2018-sp2-sles12-sp5-pool-x86_64 | https: // <mirrorcredential username> @ nu.novell.com / repo / $ RCE / OES2018-SP2-SLES12-SP5- Pool / sle-12-x86_64 /] No valid metadata found at the specified URL Course: - [|] Error while trying to read from 'https: // <mirrorcredential username> @nu.novell.com/repo/$RCE/OES2018-SP2-SLES12-SP5-Pool/sle- 12-x86_64/' - Access to 'https: // <mirrorcredential username> @nu.novell.com/repo/$RCE/OES2018-SP2-SLES12-SP5-Pool/sle-12- x86_64/content' denied. Visit the Novell Customer Center to check that your registration is valid and has not expired.
I mean when you access the repository with
https: // <mirrorcredential username> @ nu.novell.com / repo / $ RCE / OES2018-SP2-SLES12-SP5-Pool / sle-12-x86_64 /
would have to include the URL
https: // <mirrorcredential username>: <mirrorcredential password> @ nu.novell.com / repo / $ RCE / OES2018-SP2-SLES12-SP5-Pool / sle-12- x86_64 /
to be translated?
<mirrorcredential username>: <mirrorcredential password> are of course stored in the Uyuni setup with the correct access data.
where's our mistake Pablo, could you please take a look. Maybe this broke when we added the additional custom headers for reposync?
Hey Pau and Thomas, the additional custom headers should not interfere here if there is no custom header defined at "/etc/rhn/spacewalk-repo-sync/extra_headers.conf". Thomas, what happens if you manually call reposync and passes the mirror credentials from the CLI? Something like: # spacewalk-repo-sync -c oes2018-sp2-sles12-sp5-pool-x86_64 -u https://MIRROR_USERNAME:MIRROR_PASS@nu.novell.com/repo/\$RCE/OES2018-SP2-SLES12-SP5-Pool/sle-12-x86_64/ Additionally, taking a look at "/var/log/zypper.log" might bring some more light to the issue. Hth! -- Pablo Suárez Hernández - <psuarezhernandez@suse.de> SUSE Manager Development Team SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg - https://www.suse.com/ GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org