On dl, 2020-06-01 at 11:30 +0200, Thomas Weis wrote:
Hello everybody
we installed Uyuni 2020.05 from scratch, an update from 4.01 did not work for us.
What problem did you have when updating from 4.0.1? Did you follow the migration steps in the 4.0.2 release notes? https://www.uyuni-project.org/doc/2020.05/release-notes-uyuni-server.ht ml#_migrating_the_server_from_4_0_1_to_4_0_2
After the first product initialization, the OES2018 Repos cannot be synchronized via the GUI. Since the GPG keys are probably not imported during the first synchronization via the GUI, we synchronize the repos manually, e.g .:
spacewalk-repo-sync -v -c oes2018-sp2-sles12-sp5-pool-x86_64
Under Release 4.01, this worked with OES2018-SP1 *, the keys could then be imported manually.
This is expected. We are working on a solution for this for every non- SUSE vendor.
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?
Thanks and best regards
Thomas-- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Thank you Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager Phone: +1 385-666-5608 SUSE Software Solutions Spain