Re: Registration problems with Ubuntu 20.04 and Uyuni
Actually I do and I don't. There's no auth.conf, ppanon@mydomain@mytestclient:/etc/apt$ ls -al total 20 drwxr-xr-x 7 root root 158 Dec 7 19:42 . drwxr-xr-x 97 root root 8192 Feb 4 06:03 .. drwxr-xr-x 2 root root 296 Jan 28 06:40 apt.conf.d drwxr-xr-x 2 root root 30 Jan 26 23:17 auth.conf.d drwxr-xr-x 2 root root 6 Apr 9 2020 preferences.d -rw-r--r-- 1 root root 2779 Jan 26 23:17 sources.list -rw-r--r-- 1 root root 2743 Jul 31 2020 sources.list.curtin.old drwxr-xr-x 2 root root 39 Jan 26 23:17 sources.list.d drwxr-xr-x 2 root root 123 Jul 31 2020 trusted.gpg.d but there is a file in the auth.conf.d subdirectory ppanon@mydomain@mytestclient:/etc/apt$ ls -al auth.conf.d/ total 8 drwxr-xr-x 2 root root 30 Jan 26 23:17 . drwxr-xr-x 7 root root 158 Dec 7 19:42 .. -rw------- 1 _apt root 5058 Jan 26 23:17 susemanager.conf For each channel there are two entries: ppanon@mydomain@mytestclient:/etc/apt$ sudo more auth.conf.d/susemanager.conf [sudo] password for ppanon@mydomain: # susemanager.conf managed by SUSE Manager # Do not edit this file, changes will be overwritten # machine myserver.mydomain:443/rhn/manager/download/dists/<channel1> login <long encrypted string> machine myserver.mydomain:443/rhn/manager/download/<channel1> login <long encrypted string> machine myserver.mydomain:443/rhn/manager/download/dists/<channel2> login <long encrypted string#2> machine myserver.mydomain:443/rhn/manager/download/<channel2> login <long encrypted string#2> . . . The encrypted strings are the same for the two entries for each channel, but differ from channel to channel. So maybe the problem is that the auth.conf file which should include the files in the subdirectory are missing? I'm not sure what the syntax for that would be and it didn't look like that was necessary in the man page. I've tried to run #sudo apt -oDebug::pkgAcquire::Worker=1 update and I don't see any indication that tokens are being submitted in the URLs listed in the output, but I don't know if that should be visible or not. Err:1 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.04-pool-a...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.04-pool-a...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.04-pool-a... <- https:400%20URI%20Failure%0aFailReason:%20HttpError404%0aMessage:%20404%20%20404%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.04-pool-a... Ign:8 https://myserver.mydomain:443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017:04:03%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... Get:9 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aFailReason:%20HttpError404%0aMessage:%20Undetermined%20Error%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... -> https:600%20URI%20Acquire%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.04-pool-a... Err:9 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... <- https:200%20URI%20Start%0aLast-Modified:%20Tue,%2008%20Dec%202020%2012:19:09%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... Get:10 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aMessage:%20Undetermined%20Error%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... Err:10 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017:06:43%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... Get:11 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease -----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Thursday, February 4, 2021 12:18 PM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni So you really do not have an apt auth.conf file? sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Thu Feb 04 02:24:35 GMT+01:00 2021 An: Robert Paschedag <robert.paschedag@web.de> Cc: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni Hi Robert, Thanks for the info on what that token should be and where. I'll keep in mind the forthcoming change of location. But for now, since we're still running Uyuni 2020.11, it should be in the sources.list file and it just isn't ppanon@mydomain@mytestclient:/etc/apt$ more /etc/apt/sources.list.d/susemanager\:channels.list # Channels managed by SUSE Manager # Do not edit this file, changes will be overwritten # deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-security-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-20.04-pool-amd64-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-uyuni-client main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-updates-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-updates-uyuni main So how do I fix this? Is there a salt command I can use to try to replicate that part of the bootstrap and get more information to find out why it's failing? Is there a salt command I can use to generate and populate those tokens after the fact? Thanks, Paul-Andre -----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Saturday, January 30, 2021 6:38 AM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni Hi Paul-Andre, when zu register via salt, within your sources.list file created by uyuni, you should have a token attached to every channel that client is subscribed to. A latest fix moves those token information into the auth.conf file (a .netrc like file). See also Robert sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Wed Jan 27 01:01:40 GMT+01:00 2021 An: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni Well, it’s a definite improvement. I’ve rolled that into the template customization scripts and I can now see more than 1 system registered. Thank you. I’m now seeing a different problem. W: Failed to fetch https://urldefense.proofpoint.com/v2/url?u=https-3A__myuniserver.mydomain-3A443_rhn_manager_download_dists_ubuntu-2D2004-2Damd64-2Dmain-2Dsecurity-2Duyuni_InRelease&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=uXLXgJZnU7L6qtsKpTFhdwYWbJJ47fyrl1qTBRu4-D8&s=RtMA8z2YPpn1X1WUP4o1G2CizV-ZfgHAHmK0hyKlDb4&e= Undetermined Error [IP: AA.BB.CC.DD 443] If I try to go to that URL from a browser, I get You need a token to access /manager/download/ubuntu-2004-amd64-main-security-uyuni/repodata/InRelease The only reference I’ve found in google for that appears to be in Spanish and CentOS related on a capa9.net forum. -- *For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.* -- *For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.*
Hi, that is - at first - looking good (only looking to the auth.conf file). And you do not get a 401 or 403 indicating that you are not authorized or access is forbidden. Issue for me is, that you get 400 errors. Please check the apache logs (/var/log/httpd) and check, what files are exactly requested. Robert
Gesendet: Freitag, 05. Februar 2021 um 05:39 Uhr Von: "Paul-Andre Panon" <paul-andre.panon@avigilon.com> An: "Pau Garcia" <pau.garcia@suse.com>, users@lists.uyuni-project.org, "Robert Paschedag" <robert.paschedag@web.de> Betreff: Re: Registration problems with Ubuntu 20.04 and Uyuni
Actually I do and I don't. There's no auth.conf,
ppanon@mydomain@mytestclient:/etc/apt$ ls -al total 20 drwxr-xr-x 7 root root 158 Dec 7 19:42 . drwxr-xr-x 97 root root 8192 Feb 4 06:03 .. drwxr-xr-x 2 root root 296 Jan 28 06:40 apt.conf.d drwxr-xr-x 2 root root 30 Jan 26 23:17 auth.conf.d drwxr-xr-x 2 root root 6 Apr 9 2020 preferences.d -rw-r--r-- 1 root root 2779 Jan 26 23:17 sources.list -rw-r--r-- 1 root root 2743 Jul 31 2020 sources.list.curtin.old drwxr-xr-x 2 root root 39 Jan 26 23:17 sources.list.d drwxr-xr-x 2 root root 123 Jul 31 2020 trusted.gpg.d
but there is a file in the auth.conf.d subdirectory
ppanon@mydomain@mytestclient:/etc/apt$ ls -al auth.conf.d/ total 8 drwxr-xr-x 2 root root 30 Jan 26 23:17 . drwxr-xr-x 7 root root 158 Dec 7 19:42 .. -rw------- 1 _apt root 5058 Jan 26 23:17 susemanager.conf
For each channel there are two entries:
ppanon@mydomain@mytestclient:/etc/apt$ sudo more auth.conf.d/susemanager.conf [sudo] password for ppanon@mydomain: # susemanager.conf managed by SUSE Manager # Do not edit this file, changes will be overwritten #
machine myserver.mydomain:443/rhn/manager/download/dists/<channel1> login <long encrypted string> machine myserver.mydomain:443/rhn/manager/download/<channel1> login <long encrypted string>
machine myserver.mydomain:443/rhn/manager/download/dists/<channel2> login <long encrypted string#2> machine myserver.mydomain:443/rhn/manager/download/<channel2> login <long encrypted string#2> . . .
The encrypted strings are the same for the two entries for each channel, but differ from channel to channel.
So maybe the problem is that the auth.conf file which should include the files in the subdirectory are missing? I'm not sure what the syntax for that would be and it didn't look like that was necessary in the man page.
I've tried to run #sudo apt -oDebug::pkgAcquire::Worker=1 update and I don't see any indication that tokens are being submitted in the URLs listed in the output, but I don't know if that should be visible or not.
Err:1 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.04-pool-a...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.04-pool-a...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.04-pool-a... <- https:400%20URI%20Failure%0aFailReason:%20HttpError404%0aMessage:%20404%20%20404%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.04-pool-a... Ign:8 https://myserver.mydomain:443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017:04:03%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... Get:9 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aFailReason:%20HttpError404%0aMessage:%20Undetermined%20Error%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... -> https:600%20URI%20Acquire%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.04-pool-a... Err:9 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... <- https:200%20URI%20Start%0aLast-Modified:%20Tue,%2008%20Dec%202020%2012:19:09%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... Get:10 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aMessage:%20Undetermined%20Error%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... Err:10 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u...) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017:06:43%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-u... Get:11 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease
-----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Thursday, February 4, 2021 12:18 PM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni
So you really do not have an apt auth.conf file?
sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Thu Feb 04 02:24:35 GMT+01:00 2021 An: Robert Paschedag <robert.paschedag@web.de> Cc: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni
Hi Robert,
Thanks for the info on what that token should be and where. I'll keep in mind the forthcoming change of location. But for now, since we're still running Uyuni 2020.11, it should be in the sources.list file and it just isn't
ppanon@mydomain@mytestclient:/etc/apt$ more /etc/apt/sources.list.d/susemanager\:channels.list # Channels managed by SUSE Manager # Do not edit this file, changes will be overwritten #
deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-security-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-20.04-pool-amd64-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-uyuni-client main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-updates-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C_Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-updates-uyuni main
So how do I fix this? Is there a salt command I can use to try to replicate that part of the bootstrap and get more information to find out why it's failing? Is there a salt command I can use to generate and populate those tokens after the fact?
Thanks,
Paul-Andre
-----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Saturday, January 30, 2021 6:38 AM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni
Hi Paul-Andre,
when zu register via salt, within your sources.list file created by uyuni, you should have a token attached to every channel that client is subscribed to.
A latest fix moves those token information into the auth.conf file (a .netrc like file). See also
Robert
sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Wed Jan 27 01:01:40 GMT+01:00 2021 An: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni
Well, it’s a definite improvement. I’ve rolled that into the template customization scripts and I can now see more than 1 system registered. Thank you.
I’m now seeing a different problem.
W: Failed to fetch https://urldefense.proofpoint.com/v2/url?u=https-3A__myuniserver.mydomain-3A443_rhn_manager_download_dists_ubuntu-2D2004-2Damd64-2Dmain-2Dsecurity-2Duyuni_InRelease&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=uXLXgJZnU7L6qtsKpTFhdwYWbJJ47fyrl1qTBRu4-D8&s=RtMA8z2YPpn1X1WUP4o1G2CizV-ZfgHAHmK0hyKlDb4&e= Undetermined Error [IP: AA.BB.CC.DD 443]
If I try to go to that URL from a browser, I get
You need a token to access /manager/download/ubuntu-2004-amd64-main-security-uyuni/repodata/InRelease
The only reference I’ve found in google for that appears to be in Spanish and CentOS related on a capa9.net forum.
--
*For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.*
--
*For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.*
Hi Robert, This is what it's looking for and I think I may have figured out as a result what was going wrong. 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" ::1 - - [06/Feb/2021:00:25:29 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty-deb/Release HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty-deb/Release HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 10.91.16.74 - - [06/Feb/2021:00:25:56 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-security-uyuni/InRelease HTTP/1.1" 200 - ::1 - - [06/Feb/2021:00:25:58 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" ::1 - - [06/Feb/2021:00:25:59 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 10.91.16.74 - - [06/Feb/2021:00:26:12 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease HTTP/1.1" 404 8191 10.91.16.74 - - [06/Feb/2021:00:26:12 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-uyuni-client/InRelease HTTP/1.1" 200 - ::1 - - [06/Feb/2021:00:26:17 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 10.91.16.74 - - [06/Feb/2021:00:26:27 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:26:42 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:26:57 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:27:12 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-updates-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:27:27 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release HTTP/1.1" 304 - 10.91.16.74 - - [06/Feb/2021:00:27:27 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release.gpg HTTP/1.1" 404 8191 I've been using a modified version of philicious's secureApt.sh script on the older Spacewalk install to generate Release, InRelease, and Release.gpg files. I copied over the script, and added it to a regular cron job and noticed that it was creating those files. What I neglected to do was perform the steps for creating a GPG key in the keyring with which to sign the release files, or notice that the .gpg and InRelease files thus being created were empty. Except for the 20.04-pool repo, which didn't have those files at all because I didn't bother with the 0-length Packages file, the other repodata sig files were all being transmitted as is and the client, seeing a 0-length file, must be interpreting it as a network error. I'll try to create the GPG key, rerun the script for the *Release* repodata files, and see if that helps. If you don't hear from me again you can assume it worked. -----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Friday, February 5, 2021 12:10 AM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: Aw: Re: Registration problems with Ubuntu 20.04 and Uyuni Hi, that is - at first - looking good (only looking to the auth.conf file). And you do not get a 401 or 403 indicating that you are not authorized or access is forbidden. Issue for me is, that you get 400 errors. Please check the apache logs (/var/log/httpd) and check, what files are exactly requested. Robert
Gesendet: Freitag, 05. Februar 2021 um 05:39 Uhr Von: "Paul-Andre Panon" <paul-andre.panon@avigilon.com> An: "Pau Garcia" <pau.garcia@suse.com>, users@lists.uyuni-project.org, "Robert Paschedag" <robert.paschedag@web.de> Betreff: Re: Registration problems with Ubuntu 20.04 and Uyuni
Actually I do and I don't. There's no auth.conf,
ppanon@mydomain@mytestclient:/etc/apt$ ls -al total 20 drwxr-xr-x 7 root root 158 Dec 7 19:42 . drwxr-xr-x 97 root root 8192 Feb 4 06:03 .. drwxr-xr-x 2 root root 296 Jan 28 06:40 apt.conf.d drwxr-xr-x 2 root root 30 Jan 26 23:17 auth.conf.d drwxr-xr-x 2 root root 6 Apr 9 2020 preferences.d -rw-r--r-- 1 root root 2779 Jan 26 23:17 sources.list -rw-r--r-- 1 root root 2743 Jul 31 2020 sources.list.curtin.old drwxr-xr-x 2 root root 39 Jan 26 23:17 sources.list.d drwxr-xr-x 2 root root 123 Jul 31 2020 trusted.gpg.d
but there is a file in the auth.conf.d subdirectory
ppanon@mydomain@mytestclient:/etc/apt$ ls -al auth.conf.d/ total 8 drwxr-xr-x 2 root root 30 Jan 26 23:17 . drwxr-xr-x 7 root root 158 Dec 7 19:42 .. -rw------- 1 _apt root 5058 Jan 26 23:17 susemanager.conf
For each channel there are two entries:
ppanon@mydomain@mytestclient:/etc/apt$ sudo more auth.conf.d/susemanager.conf [sudo] password for ppanon@mydomain: # susemanager.conf managed by SUSE Manager # Do not edit this file, changes will be overwritten #
machine myserver.mydomain:443/rhn/manager/download/dists/<channel1> login <long encrypted string> machine myserver.mydomain:443/rhn/manager/download/<channel1> login <long encrypted string>
machine myserver.mydomain:443/rhn/manager/download/dists/<channel2> login <long encrypted string#2> machine myserver.mydomain:443/rhn/manager/download/<channel2> login <long encrypted string#2> . . .
The encrypted strings are the same for the two entries for each channel, but differ from channel to channel.
So maybe the problem is that the auth.conf file which should include the files in the subdirectory are missing? I'm not sure what the syntax for that would be and it didn't look like that was necessary in the man page.
I've tried to run #sudo apt -oDebug::pkgAcquire::Worker=1 update and I don't see any indication that tokens are being submitted in the URLs listed in the output, but I don't know if that should be visible or not.
Err:1 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-main-security-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Co nnecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Co nnected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Wa iting%20for%20headers <- https:400%20URI%20Failure%0aFailReason:%20HttpError404%0aMessage:%2040 4%20%20404%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserver.mydom ain:443/rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/InRel ease Ign:8 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-20.04-pool-amd64-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-uyuni-client/InRelease%0aMessage:%20W aiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017 :04:03%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-uyuni-client/InRelease Get:9 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-uyuni-client InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aFailReason:%20 HttpError404%0aMessage:%20Undetermined%20Error%20[IP:%2010.90.16.11%20 443]%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists /ubuntu-2004-amd64-uyuni-client/InRelease -> https:600%20URI%20Acquire%0aURI:%20https://myserver.mydomain:443/rhn/m anager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release%0aFilename :%20/var/lib/apt/lists/partial/myserver.mydomain:443_rhn_manager_downl oad_dists_ubuntu-20.04-pool-amd64-uyuni_Release%0aTarget-Type:%20index %0aTarget-Release:%20ubuntu-20.04-pool-amd64-uyuni%0aTarget-Base-URI:% 20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.0 4-pool-amd64-uyuni/%0aTarget-Repo-URI:%20https://myserver.mydomain:443 /rhn/manager/download/%0aTarget-Site:%20https://myserver.mydomain:443/ rhn/manager/download%0aIndex-File:%20true%0aMaximum-Size:%2010000000%0 aLast-Modified:%20Tue,%2003%20Nov%202020%2010:18:00%20GMT%0a%0a Err:9 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-uyuni-client InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Connecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Connected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Waiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Tue,%2008%20Dec%202020%2012 :19:09%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease Get:10 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aMessage:%20Und etermined%20Error%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserve r.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-universe-u pdates-uyuni/InRelease Err:10 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Connecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Connected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Waiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017 :06:43%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-universe-uyuni/InRelease Get:11 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-uyuni InRelease
-----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Thursday, February 4, 2021 12:18 PM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni
So you really do not have an apt auth.conf file?
sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Thu Feb 04 02:24:35 GMT+01:00 2021 An: Robert Paschedag <robert.paschedag@web.de> Cc: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni
Hi Robert,
Thanks for the info on what that token should be and where. I'll keep in mind the forthcoming change of location. But for now, since we're still running Uyuni 2020.11, it should be in the sources.list file and it just isn't
ppanon@mydomain@mytestclient:/etc/apt$ more /etc/apt/sources.list.d/susemanager\:channels.list # Channels managed by SUSE Manager # Do not edit this file, changes will be overwritten #
deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-security-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-20.04-pool-amd64-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-uyuni-client main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-updates-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-updates-uyuni main
So how do I fix this? Is there a salt command I can use to try to replicate that part of the bootstrap and get more information to find out why it's failing? Is there a salt command I can use to generate and populate those tokens after the fact?
Thanks,
Paul-Andre
-----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Saturday, January 30, 2021 6:38 AM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni
Hi Paul-Andre,
when zu register via salt, within your sources.list file created by uyuni, you should have a token attached to every channel that client is subscribed to.
A latest fix moves those token information into the auth.conf file (a .netrc like file). See also
Robert
sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Wed Jan 27 01:01:40 GMT+01:00 2021 An: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni
Well, it’s a definite improvement. I’ve rolled that into the template customization scripts and I can now see more than 1 system registered. Thank you.
I’m now seeing a different problem.
W: Failed to fetch https://urldefense.proofpoint.com/v2/url?u=https-3A__myuniserver.mydom ain-3A443_rhn_manager_download_dists_ubuntu-2D2004-2Damd64-2Dmain-2Dse curity-2Duyuni_InRelease&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcn cSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=uXLXgJZnU7L6qtsKpTFhdwYWbJJ47fyrl 1qTBRu4-D8&s=RtMA8z2YPpn1X1WUP4o1G2CizV-ZfgHAHmK0hyKlDb4&e= Undetermined Error [IP: AA.BB.CC.DD 443]
If I try to go to that URL from a browser, I get
You need a token to access /manager/download/ubuntu-2004-amd64-main-security-uyuni/repodata/InRel ease
The only reference I’ve found in google for that appears to be in Spanish and CentOS related on a capa9.net forum.
--
*For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elq TrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacyst atement>.*
--
*For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elq TrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacyst atement>.*
-- *For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.*
Well, the idea seems to have been correct but I'm still short on the execution. After creating a new GPG key pair to sign the repo (http://www.devops-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk) and downloading and importing the key into the client, I now get farther but still fall short. I also had to change one more thing in the generation of the Release and InRelease files, but an apt-get update now produces root@dc1-ubun20test:/home/ituser# apt-get update Get:1 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni InRelease [1865 B] Ign:2 https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni InRelease Get:3 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease [1839 B] Get:4 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Get:5 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease [1879 B] Ign:1 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni InRelease Get:6 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease [1867 B] Get:7 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-uyuni InRelease [1847 B] Ign:3 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease Get:8 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-updates-uyuni InRelease [1862 B] Hit:9 https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni Release Ign:5 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease Ign:10 https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni Release.gpg Ign:6 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease Hit:11 http://ca.archive.ubuntu.com/ubuntu focal InRelease Ign:7 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-uyuni InRelease Get:12 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB] Ign:8 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-updates-uyuni InRelease Get:13 http://ca.archive.ubuntu.com/ubuntu focal-security InRelease [109 kB] Fetched 335 kB in 1s (414 kB/s) Reading package lists... Done W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-updates-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A It looks like I've still got a bit to figure out. Maybe the old public key copied from the Spacewalk web service is still in the apt-key keychain and wasn't replaced with the new one I generated for Uyuni despite trying to add the latter with apt-key with no errors. I'll have to dig into apt-key to figure that out. -----Original Message----- From: Paul-Andre Panon <paul-andre.panon@avigilon.com> Sent: Saturday, February 6, 2021 12:53 AM To: 'Robert Paschedag' <robert.paschedag@web.de> Cc: 'Pau Garcia' <pau.garcia@suse.com>; 'users@lists.uyuni-project.org' <users@lists.uyuni-project.org>; 'users@lists.uyuni-project.org' <users@lists.uyuni-project.org> Subject: RE: Re: Registration problems with Ubuntu 20.04 and Uyuni Hi Robert, This is what it's looking for and I think I may have figured out as a result what was going wrong. 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" ::1 - - [06/Feb/2021:00:25:29 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty-deb/Release HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty-deb/Release HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 10.91.16.74 - - [06/Feb/2021:00:25:56 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-security-uyuni/InRelease HTTP/1.1" 200 - ::1 - - [06/Feb/2021:00:25:58 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" ::1 - - [06/Feb/2021:00:25:59 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 10.91.16.74 - - [06/Feb/2021:00:26:12 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease HTTP/1.1" 404 8191 10.91.16.74 - - [06/Feb/2021:00:26:12 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-uyuni-client/InRelease HTTP/1.1" 200 - ::1 - - [06/Feb/2021:00:26:17 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 10.91.16.74 - - [06/Feb/2021:00:26:27 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:26:42 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:26:57 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:27:12 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-updates-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:27:27 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release HTTP/1.1" 304 - 10.91.16.74 - - [06/Feb/2021:00:27:27 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release.gpg HTTP/1.1" 404 8191 I've been using a modified version of philicious's secureApt.sh script on the older Spacewalk install to generate Release, InRelease, and Release.gpg files. I copied over the script, and added it to a regular cron job and noticed that it was creating those files. What I neglected to do was perform the steps for creating a GPG key in the keyring with which to sign the release files, or notice that the .gpg and InRelease files thus being created were empty. Except for the 20.04-pool repo, which didn't have those files at all because I didn't bother with the 0-length Packages file, the other repodata sig files were all being transmitted as is and the client, seeing a 0-length file, must be interpreting it as a network error. I'll try to create the GPG key, rerun the script for the *Release* repodata files, and see if that helps. If you don't hear from me again you can assume it worked. -----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Friday, February 5, 2021 12:10 AM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: Aw: Re: Registration problems with Ubuntu 20.04 and Uyuni Hi, that is - at first - looking good (only looking to the auth.conf file). And you do not get a 401 or 403 indicating that you are not authorized or access is forbidden. Issue for me is, that you get 400 errors. Please check the apache logs (/var/log/httpd) and check, what files are exactly requested. Robert
Gesendet: Freitag, 05. Februar 2021 um 05:39 Uhr Von: "Paul-Andre Panon" <paul-andre.panon@avigilon.com> An: "Pau Garcia" <pau.garcia@suse.com>, users@lists.uyuni-project.org, "Robert Paschedag" <robert.paschedag@web.de> Betreff: Re: Registration problems with Ubuntu 20.04 and Uyuni
Actually I do and I don't. There's no auth.conf,
ppanon@mydomain@mytestclient:/etc/apt$ ls -al total 20 drwxr-xr-x 7 root root 158 Dec 7 19:42 . drwxr-xr-x 97 root root 8192 Feb 4 06:03 .. drwxr-xr-x 2 root root 296 Jan 28 06:40 apt.conf.d drwxr-xr-x 2 root root 30 Jan 26 23:17 auth.conf.d drwxr-xr-x 2 root root 6 Apr 9 2020 preferences.d -rw-r--r-- 1 root root 2779 Jan 26 23:17 sources.list -rw-r--r-- 1 root root 2743 Jul 31 2020 sources.list.curtin.old drwxr-xr-x 2 root root 39 Jan 26 23:17 sources.list.d drwxr-xr-x 2 root root 123 Jul 31 2020 trusted.gpg.d
but there is a file in the auth.conf.d subdirectory
ppanon@mydomain@mytestclient:/etc/apt$ ls -al auth.conf.d/ total 8 drwxr-xr-x 2 root root 30 Jan 26 23:17 . drwxr-xr-x 7 root root 158 Dec 7 19:42 .. -rw------- 1 _apt root 5058 Jan 26 23:17 susemanager.conf
For each channel there are two entries:
ppanon@mydomain@mytestclient:/etc/apt$ sudo more auth.conf.d/susemanager.conf [sudo] password for ppanon@mydomain: # susemanager.conf managed by SUSE Manager # Do not edit this file, changes will be overwritten #
machine myserver.mydomain:443/rhn/manager/download/dists/<channel1> login <long encrypted string> machine myserver.mydomain:443/rhn/manager/download/<channel1> login <long encrypted string>
machine myserver.mydomain:443/rhn/manager/download/dists/<channel2> login <long encrypted string#2> machine myserver.mydomain:443/rhn/manager/download/<channel2> login <long encrypted string#2> . . .
The encrypted strings are the same for the two entries for each channel, but differ from channel to channel.
So maybe the problem is that the auth.conf file which should include the files in the subdirectory are missing? I'm not sure what the syntax for that would be and it didn't look like that was necessary in the man page.
I've tried to run #sudo apt -oDebug::pkgAcquire::Worker=1 update and I don't see any indication that tokens are being submitted in the URLs listed in the output, but I don't know if that should be visible or not.
Err:1 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-main-security-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Co nnecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Co nnected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Wa iting%20for%20headers <- https:400%20URI%20Failure%0aFailReason:%20HttpError404%0aMessage:%2040 4%20%20404%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserver.mydom ain:443/rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/InRel ease Ign:8 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-20.04-pool-amd64-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-uyuni-client/InRelease%0aMessage:%20W aiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017 :04:03%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-uyuni-client/InRelease Get:9 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-uyuni-client InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aFailReason:%20 HttpError404%0aMessage:%20Undetermined%20Error%20[IP:%2010.90.16.11%20 443]%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists /ubuntu-2004-amd64-uyuni-client/InRelease -> https:600%20URI%20Acquire%0aURI:%20https://myserver.mydomain:443/rhn/m anager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release%0aFilename :%20/var/lib/apt/lists/partial/myserver.mydomain:443_rhn_manager_downl oad_dists_ubuntu-20.04-pool-amd64-uyuni_Release%0aTarget-Type:%20index %0aTarget-Release:%20ubuntu-20.04-pool-amd64-uyuni%0aTarget-Base-URI:% 20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.0 4-pool-amd64-uyuni/%0aTarget-Repo-URI:%20https://myserver.mydomain:443 /rhn/manager/download/%0aTarget-Site:%20https://myserver.mydomain:443/ rhn/manager/download%0aIndex-File:%20true%0aMaximum-Size:%2010000000%0 aLast-Modified:%20Tue,%2003%20Nov%202020%2010:18:00%20GMT%0a%0a Err:9 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-uyuni-client InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Connecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Connected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Waiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Tue,%2008%20Dec%202020%2012 :19:09%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease Get:10 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aMessage:%20Und etermined%20Error%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserve r.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-universe-u pdates-uyuni/InRelease Err:10 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Connecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Connected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Waiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017 :06:43%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-universe-uyuni/InRelease Get:11 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-uyuni InRelease
-----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Thursday, February 4, 2021 12:18 PM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni
So you really do not have an apt auth.conf file?
sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Thu Feb 04 02:24:35 GMT+01:00 2021 An: Robert Paschedag <robert.paschedag@web.de> Cc: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni
Hi Robert,
Thanks for the info on what that token should be and where. I'll keep in mind the forthcoming change of location. But for now, since we're still running Uyuni 2020.11, it should be in the sources.list file and it just isn't
ppanon@mydomain@mytestclient:/etc/apt$ more /etc/apt/sources.list.d/susemanager\:channels.list # Channels managed by SUSE Manager # Do not edit this file, changes will be overwritten #
deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-security-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-20.04-pool-amd64-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-uyuni-client main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-updates-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-updates-uyuni main
So how do I fix this? Is there a salt command I can use to try to replicate that part of the bootstrap and get more information to find out why it's failing? Is there a salt command I can use to generate and populate those tokens after the fact?
Thanks,
Paul-Andre
-----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Saturday, January 30, 2021 6:38 AM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni
Hi Paul-Andre,
when zu register via salt, within your sources.list file created by uyuni, you should have a token attached to every channel that client is subscribed to.
A latest fix moves those token information into the auth.conf file (a .netrc like file). See also
Robert
sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Wed Jan 27 01:01:40 GMT+01:00 2021 An: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni
Well, it’s a definite improvement. I’ve rolled that into the template customization scripts and I can now see more than 1 system registered. Thank you.
I’m now seeing a different problem.
W: Failed to fetch https://urldefense.proofpoint.com/v2/url?u=https-3A__myuniserver.mydom ain-3A443_rhn_manager_download_dists_ubuntu-2D2004-2Damd64-2Dmain-2Dse curity-2Duyuni_InRelease&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcn cSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=uXLXgJZnU7L6qtsKpTFhdwYWbJJ47fyrl 1qTBRu4-D8&s=RtMA8z2YPpn1X1WUP4o1G2CizV-ZfgHAHmK0hyKlDb4&e= Undetermined Error [IP: AA.BB.CC.DD 443]
If I try to go to that URL from a browser, I get
You need a token to access /manager/download/ubuntu-2004-amd64-main-security-uyuni/repodata/InRel ease
The only reference I’ve found in google for that appears to be in Spanish and CentOS related on a capa9.net forum.
--
*For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elq TrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacyst atement>.*
--
*For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elq TrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacyst atement>.*
-- *For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.*
Using the secureApt script is not needed anymore! Uyuni creates them! But die this to work, you need to configure uyuni. Don't have it on mind right now, but there should be some "mgr-create-gpg..." something script. Sorry for not being that detailed right now. Robert sent from my mobile device -------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Sat Feb 06 11:21:53 GMT+01:00 2021 An: Robert Paschedag <robert.paschedag@web.de> Cc: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Re: Registration problems with Ubuntu 20.04 and Uyuni Well, the idea seems to have been correct but I'm still short on the execution. After creating a new GPG key pair to sign the repo (http://www.devops-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk) and downloading and importing the key into the client, I now get farther but still fall short. I also had to change one more thing in the generation of the Release and InRelease files, but an apt-get update now produces root@dc1-ubun20test:/home/ituser# apt-get update Get:1 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni InRelease [1865 B] Ign:2 https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni InRelease Get:3 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease [1839 B] Get:4 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Get:5 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease [1879 B] Ign:1 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni InRelease Get:6 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease [1867 B] Get:7 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-uyuni InRelease [1847 B] Ign:3 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease Get:8 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-updates-uyuni InRelease [1862 B] Hit:9 https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni Release Ign:5 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease Ign:10 https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni Release.gpg Ign:6 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease Hit:11 http://ca.archive.ubuntu.com/ubuntu focal InRelease Ign:7 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-uyuni InRelease Get:12 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB] Ign:8 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-updates-uyuni InRelease Get:13 http://ca.archive.ubuntu.com/ubuntu focal-security InRelease [109 kB] Fetched 335 kB in 1s (414 kB/s) Reading package lists... Done W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-updates-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A It looks like I've still got a bit to figure out. Maybe the old public key copied from the Spacewalk web service is still in the apt-key keychain and wasn't replaced with the new one I generated for Uyuni despite trying to add the latter with apt-key with no errors. I'll have to dig into apt-key to figure that out. -----Original Message----- From: Paul-Andre Panon <paul-andre.panon@avigilon.com> Sent: Saturday, February 6, 2021 12:53 AM To: 'Robert Paschedag' <robert.paschedag@web.de> Cc: 'Pau Garcia' <pau.garcia@suse.com>; 'users@lists.uyuni-project.org' <users@lists.uyuni-project.org>; 'users@lists.uyuni-project.org' <users@lists.uyuni-project.org> Subject: RE: Re: Registration problems with Ubuntu 20.04 and Uyuni Hi Robert, This is what it's looking for and I think I may have figured out as a result what was going wrong. 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" ::1 - - [06/Feb/2021:00:25:29 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty-deb/Release HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty-deb/Release HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 10.91.16.74 - - [06/Feb/2021:00:25:56 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-security-uyuni/InRelease HTTP/1.1" 200 - ::1 - - [06/Feb/2021:00:25:58 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" ::1 - - [06/Feb/2021:00:25:59 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 10.91.16.74 - - [06/Feb/2021:00:26:12 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease HTTP/1.1" 404 8191 10.91.16.74 - - [06/Feb/2021:00:26:12 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-uyuni-client/InRelease HTTP/1.1" 200 - ::1 - - [06/Feb/2021:00:26:17 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 10.91.16.74 - - [06/Feb/2021:00:26:27 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:26:42 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:26:57 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:27:12 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-updates-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:27:27 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release HTTP/1.1" 304 - 10.91.16.74 - - [06/Feb/2021:00:27:27 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release.gpg HTTP/1.1" 404 8191 I've been using a modified version of philicious's secureApt.sh script on the older Spacewalk install to generate Release, InRelease, and Release.gpg files. I copied over the script, and added it to a regular cron job and noticed that it was creating those files. What I neglected to do was perform the steps for creating a GPG key in the keyring with which to sign the release files, or notice that the .gpg and InRelease files thus being created were empty. Except for the 20.04-pool repo, which didn't have those files at all because I didn't bother with the 0-length Packages file, the other repodata sig files were all being transmitted as is and the client, seeing a 0-length file, must be interpreting it as a network error. I'll try to create the GPG key, rerun the script for the *Release* repodata files, and see if that helps. If you don't hear from me again you can assume it worked. -----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Friday, February 5, 2021 12:10 AM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: Aw: Re: Registration problems with Ubuntu 20.04 and Uyuni Hi, that is - at first - looking good (only looking to the auth.conf file). And you do not get a 401 or 403 indicating that you are not authorized or access is forbidden. Issue for me is, that you get 400 errors. Please check the apache logs (/var/log/httpd) and check, what files are exactly requested. Robert
Gesendet: Freitag, 05. Februar 2021 um 05:39 Uhr Von: "Paul-Andre Panon" <paul-andre.panon@avigilon.com> An: "Pau Garcia" <pau.garcia@suse.com>, users@lists.uyuni-project.org, "Robert Paschedag" <robert.paschedag@web.de> Betreff: Re: Registration problems with Ubuntu 20.04 and Uyuni
Actually I do and I don't. There's no auth.conf,
ppanon@mydomain@mytestclient:/etc/apt$ ls -al total 20 drwxr-xr-x 7 root root 158 Dec 7 19:42 . drwxr-xr-x 97 root root 8192 Feb 4 06:03 .. drwxr-xr-x 2 root root 296 Jan 28 06:40 apt.conf.d drwxr-xr-x 2 root root 30 Jan 26 23:17 auth.conf.d drwxr-xr-x 2 root root 6 Apr 9 2020 preferences.d -rw-r--r-- 1 root root 2779 Jan 26 23:17 sources.list -rw-r--r-- 1 root root 2743 Jul 31 2020 sources.list.curtin.old drwxr-xr-x 2 root root 39 Jan 26 23:17 sources.list.d drwxr-xr-x 2 root root 123 Jul 31 2020 trusted.gpg.d
but there is a file in the auth.conf.d subdirectory
ppanon@mydomain@mytestclient:/etc/apt$ ls -al auth.conf.d/ total 8 drwxr-xr-x 2 root root 30 Jan 26 23:17 . drwxr-xr-x 7 root root 158 Dec 7 19:42 .. -rw------- 1 _apt root 5058 Jan 26 23:17 susemanager.conf
For each channel there are two entries:
ppanon@mydomain@mytestclient:/etc/apt$ sudo more auth.conf.d/susemanager.conf [sudo] password for ppanon@mydomain: # susemanager.conf managed by SUSE Manager # Do not edit this file, changes will be overwritten #
machine myserver.mydomain:443/rhn/manager/download/dists/<channel1> login <long encrypted string> machine myserver.mydomain:443/rhn/manager/download/<channel1> login <long encrypted string>
machine myserver.mydomain:443/rhn/manager/download/dists/<channel2> login <long encrypted string#2> machine myserver.mydomain:443/rhn/manager/download/<channel2> login <long encrypted string#2> . . .
The encrypted strings are the same for the two entries for each channel, but differ from channel to channel.
So maybe the problem is that the auth.conf file which should include the files in the subdirectory are missing? I'm not sure what the syntax for that would be and it didn't look like that was necessary in the man page.
I've tried to run #sudo apt -oDebug::pkgAcquire::Worker=1 update and I don't see any indication that tokens are being submitted in the URLs listed in the output, but I don't know if that should be visible or not.
Err:1 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-main-security-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Co nnecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Co nnected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Wa iting%20for%20headers <- https:400%20URI%20Failure%0aFailReason:%20HttpError404%0aMessage:%2040 4%20%20404%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserver.mydom ain:443/rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/InRel ease Ign:8 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-20.04-pool-amd64-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-uyuni-client/InRelease%0aMessage:%20W aiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017 :04:03%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-uyuni-client/InRelease Get:9 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-uyuni-client InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aFailReason:%20 HttpError404%0aMessage:%20Undetermined%20Error%20[IP:%2010.90.16.11%20 443]%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists /ubuntu-2004-amd64-uyuni-client/InRelease -> https:600%20URI%20Acquire%0aURI:%20https://myserver.mydomain:443/rhn/m anager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release%0aFilename :%20/var/lib/apt/lists/partial/myserver.mydomain:443_rhn_manager_downl oad_dists_ubuntu-20.04-pool-amd64-uyuni_Release%0aTarget-Type:%20index %0aTarget-Release:%20ubuntu-20.04-pool-amd64-uyuni%0aTarget-Base-URI:% 20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.0 4-pool-amd64-uyuni/%0aTarget-Repo-URI:%20https://myserver.mydomain:443 /rhn/manager/download/%0aTarget-Site:%20https://myserver.mydomain:443/ rhn/manager/download%0aIndex-File:%20true%0aMaximum-Size:%2010000000%0 aLast-Modified:%20Tue,%2003%20Nov%202020%2010:18:00%20GMT%0a%0a Err:9 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-uyuni-client InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Connecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Connected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Waiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Tue,%2008%20Dec%202020%2012 :19:09%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease Get:10 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aMessage:%20Und etermined%20Error%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserve r.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-universe-u pdates-uyuni/InRelease Err:10 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Connecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Connected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Waiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017 :06:43%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-universe-uyuni/InRelease Get:11 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-uyuni InRelease
-----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Thursday, February 4, 2021 12:18 PM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni
So you really do not have an apt auth.conf file?
sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Thu Feb 04 02:24:35 GMT+01:00 2021 An: Robert Paschedag <robert.paschedag@web.de> Cc: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni
Hi Robert,
Thanks for the info on what that token should be and where. I'll keep in mind the forthcoming change of location. But for now, since we're still running Uyuni 2020.11, it should be in the sources.list file and it just isn't
ppanon@mydomain@mytestclient:/etc/apt$ more /etc/apt/sources.list.d/susemanager\:channels.list # Channels managed by SUSE Manager # Do not edit this file, changes will be overwritten #
deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-security-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-20.04-pool-amd64-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-uyuni-client main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-updates-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-updates-uyuni main
So how do I fix this? Is there a salt command I can use to try to replicate that part of the bootstrap and get more information to find out why it's failing? Is there a salt command I can use to generate and populate those tokens after the fact?
Thanks,
Paul-Andre
-----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Saturday, January 30, 2021 6:38 AM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni
Hi Paul-Andre,
when zu register via salt, within your sources.list file created by uyuni, you should have a token attached to every channel that client is subscribed to.
A latest fix moves those token information into the auth.conf file (a .netrc like file). See also
Robert
sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Wed Jan 27 01:01:40 GMT+01:00 2021 An: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni
Well, it’s a definite improvement. I’ve rolled that into the template customization scripts and I can now see more than 1 system registered. Thank you.
I’m now seeing a different problem.
W: Failed to fetch https://urldefense.proofpoint.com/v2/url?u=https-3A__myuniserver.mydom ain-3A443_rhn_manager_download_dists_ubuntu-2D2004-2Damd64-2Dmain-2Dse curity-2Duyuni_InRelease&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcn cSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=uXLXgJZnU7L6qtsKpTFhdwYWbJJ47fyrl 1qTBRu4-D8&s=RtMA8z2YPpn1X1WUP4o1G2CizV-ZfgHAHmK0hyKlDb4&e= Undetermined Error [IP: AA.BB.CC.DD 443]
If I try to go to that URL from a browser, I get
You need a token to access /manager/download/ubuntu-2004-amd64-main-security-uyuni/repodata/InRel ease
The only reference I’ve found in google for that appears to be in Spanish and CentOS related on a capa9.net forum.
--
*For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elq TrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacyst atement>.*
--
*For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elq TrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacyst atement>.*
-- *For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.*
This one https://github.com/uyuni-project/uyuni/blob/master/backend/satellite_tools/m... sent from my mobile device -------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Sat Feb 06 11:21:53 GMT+01:00 2021 An: Robert Paschedag <robert.paschedag@web.de> Cc: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Re: Registration problems with Ubuntu 20.04 and Uyuni Well, the idea seems to have been correct but I'm still short on the execution. After creating a new GPG key pair to sign the repo (http://www.devops-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk) and downloading and importing the key into the client, I now get farther but still fall short. I also had to change one more thing in the generation of the Release and InRelease files, but an apt-get update now produces root@dc1-ubun20test:/home/ituser# apt-get update Get:1 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni InRelease [1865 B] Ign:2 https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni InRelease Get:3 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease [1839 B] Get:4 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Get:5 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease [1879 B] Ign:1 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni InRelease Get:6 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease [1867 B] Get:7 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-uyuni InRelease [1847 B] Ign:3 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease Get:8 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-updates-uyuni InRelease [1862 B] Hit:9 https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni Release Ign:5 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease Ign:10 https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni Release.gpg Ign:6 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease Hit:11 http://ca.archive.ubuntu.com/ubuntu focal InRelease Ign:7 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-uyuni InRelease Get:12 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB] Ign:8 https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-updates-uyuni InRelease Get:13 http://ca.archive.ubuntu.com/ubuntu focal-security InRelease [109 kB] Fetched 335 kB in 1s (414 kB/s) Reading package lists... Done W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-uyuni-client InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A W: GPG error: https://myserver.mydomain443/rhn/manager/download ubuntu-2004-amd64-main-updates-uyuni InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D6CDEED469024D9A It looks like I've still got a bit to figure out. Maybe the old public key copied from the Spacewalk web service is still in the apt-key keychain and wasn't replaced with the new one I generated for Uyuni despite trying to add the latter with apt-key with no errors. I'll have to dig into apt-key to figure that out. -----Original Message----- From: Paul-Andre Panon <paul-andre.panon@avigilon.com> Sent: Saturday, February 6, 2021 12:53 AM To: 'Robert Paschedag' <robert.paschedag@web.de> Cc: 'Pau Garcia' <pau.garcia@suse.com>; 'users@lists.uyuni-project.org' <users@lists.uyuni-project.org>; 'users@lists.uyuni-project.org' <users@lists.uyuni-project.org> Subject: RE: Re: Registration problems with Ubuntu 20.04 and Uyuni Hi Robert, This is what it's looking for and I think I may have figured out as a result what was going wrong. 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:11 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" ::1 - - [06/Feb/2021:00:25:29 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty/repodata/repomd.xml HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty-deb/Release HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 127.0.0.1 - - [06/Feb/2021:00:25:53 -0800] "HEAD /pub/repositories/empty-deb/Release HTTP/1.1" 200 - "-" "Apache-HttpClient/UNAVAILABLE (Java/11.0.9)" 10.91.16.74 - - [06/Feb/2021:00:25:56 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-security-uyuni/InRelease HTTP/1.1" 200 - ::1 - - [06/Feb/2021:00:25:58 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" ::1 - - [06/Feb/2021:00:25:59 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 10.91.16.74 - - [06/Feb/2021:00:26:12 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease HTTP/1.1" 404 8191 10.91.16.74 - - [06/Feb/2021:00:26:12 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-uyuni-client/InRelease HTTP/1.1" 200 - ::1 - - [06/Feb/2021:00:26:17 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.43 (Linux/SUSE) OpenSSL/1.1.1d mod_wsgi/4.5.18 Python/3.6 (internal dummy connection)" 10.91.16.74 - - [06/Feb/2021:00:26:27 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:26:42 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:26:57 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:27:12 -0800] "GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-updates-uyuni/InRelease HTTP/1.1" 200 - 10.91.16.74 - - [06/Feb/2021:00:27:27 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release HTTP/1.1" 304 - 10.91.16.74 - - [06/Feb/2021:00:27:27 -0800] "GET /rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release.gpg HTTP/1.1" 404 8191 I've been using a modified version of philicious's secureApt.sh script on the older Spacewalk install to generate Release, InRelease, and Release.gpg files. I copied over the script, and added it to a regular cron job and noticed that it was creating those files. What I neglected to do was perform the steps for creating a GPG key in the keyring with which to sign the release files, or notice that the .gpg and InRelease files thus being created were empty. Except for the 20.04-pool repo, which didn't have those files at all because I didn't bother with the 0-length Packages file, the other repodata sig files were all being transmitted as is and the client, seeing a 0-length file, must be interpreting it as a network error. I'll try to create the GPG key, rerun the script for the *Release* repodata files, and see if that helps. If you don't hear from me again you can assume it worked. -----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Friday, February 5, 2021 12:10 AM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: Aw: Re: Registration problems with Ubuntu 20.04 and Uyuni Hi, that is - at first - looking good (only looking to the auth.conf file). And you do not get a 401 or 403 indicating that you are not authorized or access is forbidden. Issue for me is, that you get 400 errors. Please check the apache logs (/var/log/httpd) and check, what files are exactly requested. Robert
Gesendet: Freitag, 05. Februar 2021 um 05:39 Uhr Von: "Paul-Andre Panon" <paul-andre.panon@avigilon.com> An: "Pau Garcia" <pau.garcia@suse.com>, users@lists.uyuni-project.org, "Robert Paschedag" <robert.paschedag@web.de> Betreff: Re: Registration problems with Ubuntu 20.04 and Uyuni
Actually I do and I don't. There's no auth.conf,
ppanon@mydomain@mytestclient:/etc/apt$ ls -al total 20 drwxr-xr-x 7 root root 158 Dec 7 19:42 . drwxr-xr-x 97 root root 8192 Feb 4 06:03 .. drwxr-xr-x 2 root root 296 Jan 28 06:40 apt.conf.d drwxr-xr-x 2 root root 30 Jan 26 23:17 auth.conf.d drwxr-xr-x 2 root root 6 Apr 9 2020 preferences.d -rw-r--r-- 1 root root 2779 Jan 26 23:17 sources.list -rw-r--r-- 1 root root 2743 Jul 31 2020 sources.list.curtin.old drwxr-xr-x 2 root root 39 Jan 26 23:17 sources.list.d drwxr-xr-x 2 root root 123 Jul 31 2020 trusted.gpg.d
but there is a file in the auth.conf.d subdirectory
ppanon@mydomain@mytestclient:/etc/apt$ ls -al auth.conf.d/ total 8 drwxr-xr-x 2 root root 30 Jan 26 23:17 . drwxr-xr-x 7 root root 158 Dec 7 19:42 .. -rw------- 1 _apt root 5058 Jan 26 23:17 susemanager.conf
For each channel there are two entries:
ppanon@mydomain@mytestclient:/etc/apt$ sudo more auth.conf.d/susemanager.conf [sudo] password for ppanon@mydomain: # susemanager.conf managed by SUSE Manager # Do not edit this file, changes will be overwritten #
machine myserver.mydomain:443/rhn/manager/download/dists/<channel1> login <long encrypted string> machine myserver.mydomain:443/rhn/manager/download/<channel1> login <long encrypted string>
machine myserver.mydomain:443/rhn/manager/download/dists/<channel2> login <long encrypted string#2> machine myserver.mydomain:443/rhn/manager/download/<channel2> login <long encrypted string#2> . . .
The encrypted strings are the same for the two entries for each channel, but differ from channel to channel.
So maybe the problem is that the auth.conf file which should include the files in the subdirectory are missing? I'm not sure what the syntax for that would be and it didn't look like that was necessary in the man page.
I've tried to run #sudo apt -oDebug::pkgAcquire::Worker=1 update and I don't see any indication that tokens are being submitted in the URLs listed in the output, but I don't know if that should be visible or not.
Err:1 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-main-security-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Co nnecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Co nnected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-20.04-pool-amd64-uyuni/InRelease%0aMessage:%20Wa iting%20for%20headers <- https:400%20URI%20Failure%0aFailReason:%20HttpError404%0aMessage:%2040 4%20%20404%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserver.mydom ain:443/rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/InRel ease Ign:8 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-20.04-pool-amd64-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-uyuni-client/InRelease%0aMessage:%20W aiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017 :04:03%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-uyuni-client/InRelease Get:9 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-uyuni-client InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aFailReason:%20 HttpError404%0aMessage:%20Undetermined%20Error%20[IP:%2010.90.16.11%20 443]%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists /ubuntu-2004-amd64-uyuni-client/InRelease -> https:600%20URI%20Acquire%0aURI:%20https://myserver.mydomain:443/rhn/m anager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release%0aFilename :%20/var/lib/apt/lists/partial/myserver.mydomain:443_rhn_manager_downl oad_dists_ubuntu-20.04-pool-amd64-uyuni_Release%0aTarget-Type:%20index %0aTarget-Release:%20ubuntu-20.04-pool-amd64-uyuni%0aTarget-Base-URI:% 20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.0 4-pool-amd64-uyuni/%0aTarget-Repo-URI:%20https://myserver.mydomain:443 /rhn/manager/download/%0aTarget-Site:%20https://myserver.mydomain:443/ rhn/manager/download%0aIndex-File:%20true%0aMaximum-Size:%2010000000%0 aLast-Modified:%20Tue,%2003%20Nov%202020%2010:18:00%20GMT%0a%0a Err:9 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-uyuni-client InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Connecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Connected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease%0aMe ssage:%20Waiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Tue,%2008%20Dec%202020%2012 :19:09%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease Get:10 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:400%20URI%20Failure%0aTransient-Failure:%20true%0aMessage:%20Und etermined%20Error%20[IP:%2010.90.16.11%20443]%0aURI:%20https://myserve r.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-universe-u pdates-uyuni/InRelease Err:10 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-updates-uyuni InRelease <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Connecting%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Connected%20to%20myserver.mydomain%20(10.90.16.11) <- https:102%20Status%0aURI:%20https://myserver.mydomain:443/rhn/manager/ download/dists/ubuntu-2004-amd64-universe-uyuni/InRelease%0aMessage:%2 0Waiting%20for%20headers <- https:200%20URI%20Start%0aLast-Modified:%20Sun,%2008%20Nov%202020%2017 :06:43%20+0000%0aURI:%20https://myserver.mydomain:443/rhn/manager/down load/dists/ubuntu-2004-amd64-universe-uyuni/InRelease Get:11 https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=dqUK1umlLbMzRY3vgMeXApGDhSshpw tHFz85acJjq5o&s=dUR-ezbPQfs6dC41TAC5oBsuq3Z8jR3HlTLCejun4cE&e= ubuntu-2004-amd64-universe-uyuni InRelease
-----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Thursday, February 4, 2021 12:18 PM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni
So you really do not have an apt auth.conf file?
sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Thu Feb 04 02:24:35 GMT+01:00 2021 An: Robert Paschedag <robert.paschedag@web.de> Cc: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni
Hi Robert,
Thanks for the info on what that token should be and where. I'll keep in mind the forthcoming change of location. But for now, since we're still running Uyuni 2020.11, it should be in the sources.list file and it just isn't
ppanon@mydomain@mytestclient:/etc/apt$ more /etc/apt/sources.list.d/susemanager\:channels.list # Channels managed by SUSE Manager # Do not edit this file, changes will be overwritten #
deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-security-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-20.04-pool-amd64-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-uyuni-client main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-updates-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-universe-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain -3A443_rhn_manager_download&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWE McncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=pxVgKDn-f6RHE3D2lDunlML94QxZ3C _Febju36NyR1s&s=qfcb9vUZM4RnSc2sU3_5gAtK5Q9vejVBXHPQmvug5c0&e= ubuntu-2004-amd64-main-updates-uyuni main
So how do I fix this? Is there a salt command I can use to try to replicate that part of the bootstrap and get more information to find out why it's failing? Is there a salt command I can use to generate and populate those tokens after the fact?
Thanks,
Paul-Andre
-----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: Saturday, January 30, 2021 6:38 AM To: Paul-Andre Panon <paul-andre.panon@avigilon.com> Cc: Pau Garcia <pau.garcia@suse.com>; users@lists.uyuni-project.org Subject: RE: Registration problems with Ubuntu 20.04 and Uyuni
Hi Paul-Andre,
when zu register via salt, within your sources.list file created by uyuni, you should have a token attached to every channel that client is subscribed to.
A latest fix moves those token information into the auth.conf file (a .netrc like file). See also
Robert
sent from my mobile device-------- Originale Nachricht -------- Von: Paul-Andre Panon <paul-andre.panon@avigilon.com> Gesendet: Wed Jan 27 01:01:40 GMT+01:00 2021 An: Pau Garcia <pau.garcia@suse.com>, users@lists.uyuni-project.org Betreff: RE: Registration problems with Ubuntu 20.04 and Uyuni
Well, it’s a definite improvement. I’ve rolled that into the template customization scripts and I can now see more than 1 system registered. Thank you.
I’m now seeing a different problem.
W: Failed to fetch https://urldefense.proofpoint.com/v2/url?u=https-3A__myuniserver.mydom ain-3A443_rhn_manager_download_dists_ubuntu-2D2004-2Damd64-2Dmain-2Dse curity-2Duyuni_InRelease&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcn cSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=uXLXgJZnU7L6qtsKpTFhdwYWbJJ47fyrl 1qTBRu4-D8&s=RtMA8z2YPpn1X1WUP4o1G2CizV-ZfgHAHmK0hyKlDb4&e= Undetermined Error [IP: AA.BB.CC.DD 443]
If I try to go to that URL from a browser, I get
You need a token to access /manager/download/ubuntu-2004-amd64-main-security-uyuni/repodata/InRel ease
The only reference I’ve found in google for that appears to be in Spanish and CentOS related on a capa9.net forum.
--
*For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elq TrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacyst atement>.*
--
*For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elq TrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacyst atement>.*
-- *For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.*
participants (2)
-
Paul-Andre Panon -
Robert Paschedag