Registration problems with Ubuntu 20.04 and Uyuni
Hi, I’m trying to set up an Uyuni server to replace a Spacewalk server, starting with setting up support for Ubuntu 20.04. Ideally we would like to be able to use a vSphere VM template that we can use to generate/clone new VMs, and then run a script on that new VM to customize it with the specific desired hostname, AD domain registration, and Uyuni registration. For the Uyuni registration, I started with the generated bootstrap script and customized it with an Activation Key and the Ubuntu GPG keys (ubuntu-gpg-pubkey-871920D1991BC93C.key,uyuni-gpg-pubkey-0d20833e.key) . The registration script appears to work. If I look in Uyuni’s Salt->Keys page, I see the key, can approve it and the system shows up in the system list…. the first time. On subsequent VMs however, I see the key in the Salt->Keys page, can approve them, and then after some time I only see one of the two VMs in the system list, usually the last one added. While setting up the Uyuni server and VM template, it took me a while to figure out I was supposed to use the modified bootstrap script, so I had first tried to install salt packages on the template and thought that might be the problem. I took a hint from the bootstrap script and tried to run apt-get purge salt-minion apt-get purge salt-common rm -rf /etc/salt/minion.d/ on the template to clear any salt state, cleared systems and keys on the Uyuni server, and started over creating new VMs,… with the same result. Any suggestions on what could be going wrong? Thanks, Paul-Andre Panon, B.Sc. Senior Systems Administrator Video Security & Analytics *o:* +1.604.629.5182 ext 2190 *m*: +1.604.787.4547 -- *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>.*
Hello Have you checked this? https://www.uyuni-project.org/uyuni-docs/uyuni/administration/tshoot-registe... Troubleshooting Registering Cloned Clients :: Uyuni Documentation<https://www.uyuni-project.org/uyuni-docs/uyuni/administration/tshoot-registerclones.html> If you are using Uyuni to manage virtual machines, you might find it useful to create clones of your VMs. A clone is a VM that uses a primary disk that is an exact copy of an existing disk. www.uyuni-project.org Thank you Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager SUSE Software Solutions Spain ________________________________ From: Paul-Andre Panon <paul-andre.panon@avigilon.com> Sent: Tuesday, January 26, 2021 8:30 AM To: users@lists.uyuni-project.org <users@lists.uyuni-project.org> Subject: Registration problems with Ubuntu 20.04 and Uyuni Hi, I’m trying to set up an Uyuni server to replace a Spacewalk server, starting with setting up support for Ubuntu 20.04. Ideally we would like to be able to use a vSphere VM template that we can use to generate/clone new VMs, and then run a script on that new VM to customize it with the specific desired hostname, AD domain registration, and Uyuni registration. For the Uyuni registration, I started with the generated bootstrap script and customized it with an Activation Key and the Ubuntu GPG keys (ubuntu-gpg-pubkey-871920D1991BC93C.key,uyuni-gpg-pubkey-0d20833e.key) . The registration script appears to work. If I look in Uyuni’s Salt->Keys page, I see the key, can approve it and the system shows up in the system list…. the first time. On subsequent VMs however, I see the key in the Salt->Keys page, can approve them, and then after some time I only see one of the two VMs in the system list, usually the last one added. While setting up the Uyuni server and VM template, it took me a while to figure out I was supposed to use the modified bootstrap script, so I had first tried to install salt packages on the template and thought that might be the problem. I took a hint from the bootstrap script and tried to run apt-get purge salt-minion apt-get purge salt-common rm -rf /etc/salt/minion.d/ on the template to clear any salt state, cleared systems and keys on the Uyuni server, and started over creating new VMs,… with the same result. Any suggestions on what could be going wrong? Thanks, Paul-Andre Panon, B.Sc. Senior Systems Administrator Video Security & Analytics [https://www.motorolasolutions.com/content/dam/msi/images/logos/corporate/msi...] o: +1.604.629.5182 ext 2190 m: +1.604.787.4547 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, 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://myuniserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd6... 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. *From:* Pau Garcia <pau.garcia@suse.com> *Sent:* Tuesday, January 26, 2021 1:18 AM *To:* Paul-Andre Panon <paul-andre.panon@avigilon.com>; users@lists.uyuni-project.org *Subject:* Re: Registration problems with Ubuntu 20.04 and Uyuni Hello Have you checked this? https://www.uyuni-project.org/uyuni-docs/uyuni/administration/tshoot-registe... <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.uyuni-2Dproject.org_uyuni-2Ddocs_uyuni_administration_tshoot-2Dregisterclones.html&d=DwMF-g&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=1eukOzzSEjOtVn2k1EHN31r5jyNgS5MGJsmhyH8zORk&s=f_jplxDISPWHgOxPvgeHoTERl7TEsIFO6RV6bBD8GIU&e=> Troubleshooting Registering Cloned Clients :: Uyuni Documentation <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.uyuni-2Dproject.org_uyuni-2Ddocs_uyuni_administration_tshoot-2Dregisterclones.html&d=DwMF-g&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=1eukOzzSEjOtVn2k1EHN31r5jyNgS5MGJsmhyH8zORk&s=f_jplxDISPWHgOxPvgeHoTERl7TEsIFO6RV6bBD8GIU&e=> If you are using Uyuni to manage virtual machines, you might find it useful to create clones of your VMs. A clone is a VM that uses a primary disk that is an exact copy of an existing disk. www.uyuni-project.org Thank you Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager SUSE Software Solutions Spain ------------------------------ *From:* Paul-Andre Panon <paul-andre.panon@avigilon.com> *Sent:* Tuesday, January 26, 2021 8:30 AM *To:* users@lists.uyuni-project.org <users@lists.uyuni-project.org> *Subject:* Registration problems with Ubuntu 20.04 and Uyuni Hi, I’m trying to set up an Uyuni server to replace a Spacewalk server, starting with setting up support for Ubuntu 20.04. Ideally we would like to be able to use a vSphere VM template that we can use to generate/clone new VMs, and then run a script on that new VM to customize it with the specific desired hostname, AD domain registration, and Uyuni registration. For the Uyuni registration, I started with the generated bootstrap script and customized it with an Activation Key and the Ubuntu GPG keys (ubuntu-gpg-pubkey-871920D1991BC93C.key,uyuni-gpg-pubkey-0d20833e.key) . The registration script appears to work. If I look in Uyuni’s Salt->Keys page, I see the key, can approve it and the system shows up in the system list…. the first time. On subsequent VMs however, I see the key in the Salt->Keys page, can approve them, and then after some time I only see one of the two VMs in the system list, usually the last one added. While setting up the Uyuni server and VM template, it took me a while to figure out I was supposed to use the modified bootstrap script, so I had first tried to install salt packages on the template and thought that might be the problem. I took a hint from the bootstrap script and tried to run apt-get purge salt-minion apt-get purge salt-common rm -rf /etc/salt/minion.d/ on the template to clear any salt state, cleared systems and keys on the Uyuni server, and started over creating new VMs,… with the same result. Any suggestions on what could be going wrong? Thanks, Paul-Andre Panon, B.Sc. Senior Systems Administrator Video Security & Analytics *o:* +1.604.629.5182 ext 2190 *m*: +1.604.787.4547 *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>.*
On 27/01/2021, at 01:01, Paul-Andre Panon wrote:
W: Failed to fetch https://myuniserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd6... <https://myuniserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-main-security-uyuni/InRelease> Undetermined Error [IP: AA.BB.CC.DD 443]
Can any of the clients access myuniserver.mydomain? Try with: % curl -vv https://myuniserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd6... from any client -- Michele Bologna <michele.bologna@suse.com> SUSE Software Solutions Italy srl - https://www.suse.com
On Thursday, January 28, 2021 9:02 AM, Michele Bologna <mbologna@suse.de> wrote:
Can any of the clients access myuniserver.mydomain?
Try with:
% curl -vv https://myuniserver.mydomain/rhn/manager/download/dists/ubuntu-2004-amd64-ma...
from any client
-- Michele Bologna <michele.bologna@suse.com> SUSE Software Solutions Italy srl
Yes. Curl appears to return the same required token error I saw from my web browser ppanon@mydomain@dc1-ubun20test:~$ curl -vv https://myuniserver.mydomain/rhn/manager/download/dists/ubuntu-2004-amd64-ma... * Trying AA.BB.CC.DD:443... * TCP_NODELAY set * Connected to myuniserver.mydomain (AA.BB.CC.DD) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server accepted to use http/1.1 * Server certificate: * subject: C=CA; ST=BC; L=Vancouver; O=Avigilon Corporation; OU=IT; CN=myuniserver.mydomain; emailAddress=internal.it.operations@avigilon.com * start date: Dec 5 02:14:41 2020 GMT * expire date: Dec 5 02:14:41 2021 GMT * subjectAltName: host "myuniserver.mydomain" matched cert's "myuniserver.mydomain" * issuer: C=CA; O=Avigilon Corporation; CN=Avigilon Issuing CA 1 * SSL certificate verify ok.
GET /rhn/manager/download/dists/ubuntu-2004-amd64-main-security-uyuni/InRelease HTTP/1.1 Host: myuniserver.mydomain User-Agent: curl/7.68.0 Accept: */*
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing * Mark bundle as not supporting multiuse < HTTP/1.1 403 403 < Date: Fri, 29 Jan 2021 17:41:13 GMT < Server: Apache < X-Frame-Options: SAMEORIGIN < Content-Type: text/html;charset=UTF-8 < Content-Length: 7400 < Set-Cookie: JSESSIONID=7682A90DCBB1C5CCE654AADBC4722BC6; Path=/; Secure; HttpOnly; HttpOnly;HttpOnly;Secure < Set-Cookie: pxt-session-cookie=708xd1eb0c0bff31657a7fe27a302d52fe1c83377822dc20463e40568a3a090e427d; Max-Age=0; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly;HttpOnly;Secure < Content-Security-Policy: default-src 'self' https: wss: ; script-src 'self' https: 'unsafe-inline' 'unsafe-eval'; img-src 'self' https: data: ;style-src 'self' https: 'unsafe-inline' < X-XSS-Protection: 1; mode=block < X-Content-Type-Options: nosniff < X-Permitted-Cross-Domain-Policies: master-only < <!DOCTYPE HTML> <html> <head> <!-- enclosing head tags in layout_c.jsp --> <meta http-equiv="X-UA-Compatible" content="IE=edge"/> <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries --> <!--[if lt IE 9]> <script type='text/javascript' src="/javascript/html5.js"></script> <script type='text/javascript' src="/javascript/respond.js"></script> <![endif]--> <meta http-equiv="content-type" content="text/html;charset=UTF-8"/> <title> Uyuni </title> <link rel="shortcut icon" href="/img/favicon.ico" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <!-- import default fonts/icons styles --> <link rel="stylesheet" href="/fonts/font-awesome/css/font-awesome.css?cb=20201125131554" /> <!-- import custom fonts/icons styles --> <link rel="stylesheet" href="/fonts/font-spacewalk/css/spacewalk-font.css?cb=20201125131554" /> <!-- import plugins styles --> <link rel="stylesheet" href="/css/jquery.timepicker.css?cb=20201125131554" /> <link rel="stylesheet" href="/css/bootstrap-datepicker.css?cb=20201125131554" /> <link rel="stylesheet" href="/javascript/select2/select2.css?cb=20201125131554" /> <link rel="stylesheet" href="/javascript/select2/select2-bootstrap.css?cb=20201125131554" /> <!-- import styles --> <link rel="stylesheet" href="/css/uyuni.css?cb=20201125131554" /> <!-- expose user preferred language to the application --> <script>window.preferredLocale='en_US'</script> <!-- expose user preferred documentation language to the application --> <script>window.docsLocale='en'</script> <script src="/javascript/loggerhead.js?cb=20201125131554"></script> <script src="/javascript/frontend-log.js?cb=20201125131554"></script> <script src="/javascript/jquery.js?cb=20201125131554"></script> <script src="/javascript/bootstrap.js?cb=20201125131554"></script> <script src="/javascript/select2/select2.js?cb=20201125131554"></script> <script src="/javascript/spacewalk-essentials.js?cb=20201125131554"></script> <script src="/javascript/spacewalk-checkall.js?cb=20201125131554"></script> <script src="/rhn/dwr/engine.js?cb=20201125131554"></script> <script src="/rhn/dwr/util.js?cb=20201125131554"></script> <script src="/rhn/dwr/interface/DWRItemSelector.js?cb=20201125131554"></script> <script src="/javascript/jquery.timepicker.js?cb=20201125131554"></script> <script src="/javascript/bootstrap-datepicker.js?cb=20201125131554"></script> <script src='/vendors/vendors.bundle.js?cb=20201125131554'></script> <script src='/javascript/manager/core.bundle.js?cb=20201125131554'></script> <script src='/javascript/manager/main.bundle.js?cb=20201125131554'></script> <script src='/javascript/momentjs/moment-with-langs.min.js?cb=20201125131554' type='text/javascript'></script> </head> <body onload=""> <div class="senna-loading-bar"></div> <header class="navbar-pf"> <!-- header.jsp --> <div class="navbar-header"> <a href="#" class="navbar-toggle"> <i class="fa fa-bars" aria-hidden="true"></i> </a> <div id="breadcrumb"></div> </div> <ul class="nav navbar-nav navbar-utility"> <li> <a class="about-link" href="/rhn/help/about.do">About</a> </li> </ul> <!-- end header.jsp --> </header> <div class="spacewalk-main-column-layout"> <aside id="spacewalk-aside" class="navbar-collapse in"> <div id="nav"></div> <div id="left-menu-data"> <script type="text/javascript"> window.JSONMenu = [{"label":"About","primaryUrl":"#","urls":[],"directories":[],"active":false,"target":"","icon":"fa-question-circle","isVisible":true,"submenu":[{"label":"Overview","primaryUrl":"/rhn/help/about.do","urls":[],"directories":[],"active":false,"target":"","icon":"","isVisible":true},{"label":"Sign In","primaryUrl":"/rhn/manager/login","urls":[],"directories":[],"active":false,"target":"","icon":"","isVisible":true},{"label":"Documentation 2020.11","primaryUrl":"/docs/en/index.html","urls":[],"directories":[],"active":false,"target":"_blank","icon":"","isVisible":true},{"label":"Lookup Login/Password","primaryUrl":"/rhn/help/ForgotCredentials.do","urls":[],"directories":[],"active":false,"target":"","icon":"","isVisible":true},{"label":"Release Notes","primaryUrl":"#","urls":[],"directories":[],"active":false,"target":"_blank","icon":"","isVisible":true,"submenu":[{"label":"Uyuni Server","primaryUrl":"/docs/en/release-notes/release-notes-server.html","urls":[],"directories":[],"active":false,"target":"_blank","icon":"","isVisible":true},{"label":"Uyuni Proxy","primaryUrl":"/docs/en/release-notes/release-notes-proxy.html","urls":[],"directories":[],"active":false,"target":"_blank","icon":"","isVisible":true}]},{"label":"API","primaryUrl":"#","urls":[],"directories":[],"active":false,"target":"","icon":"","isVisible":true,"submenu":[{"label":"Overview","primaryUrl":"/rhn/apidoc/index.jsp","urls":[],"directories":["/rhn/apidoc"],"active":false,"target":"","icon":"","isVisible":true},{"label":"FAQ","primaryUrl":"/rhn/apidoc/faqs.jsp","urls":[],"directories":[],"active":false,"target":"","icon":"","isVisible":true},{"label":"Sample Scripts","primaryUrl":"/rhn/apidoc/scripts.jsp","urls":[],"directories":[],"active":false,"target":"","icon":"","isVisible":true}]},{"label":"Search","primaryUrl":"/rhn/help/Search.do","urls":[],"directories":[],"active":false,"target":"","icon":"","isVisible":true}]},{"label":"External Links","primaryUrl":"#","urls":[],"directories":[],"active":false,"target":"","icon":"fa-link","isVisible":true,"submenu":[{"label":"Knowledgebase","primaryUrl":"https://www.suse.com/support/kb/product.php?id\u003dSUSE_Manager","urls":[],"directories":[],"active":false,"target":"_blank","icon":"","isVisible":true},{"label":"Documentation","primaryUrl":"https://www.uyuni-project.org/uyuni-docs/uyuni/index.html","urls":[],"directories":[],"active":false,"target":"_blank","icon":"","isVisible":true}]}]; window._IS_UYUNI = true; </script> </div> <footer> <div class="wrapper"> <div class="footer-copyright"> <a href="/rhn/help/Copyright.do">Copyright Notice</a> </div> <div class="footer-release"> Uyuni release <a href="/docs/en/release-notes/release-notes-server.html" target="_blank">2020.11</a> </div> </div> </footer> </aside> <div id="page-body"> <section id="spacewalk-content"> <noscript> <div class="alert alert-danger"> Some features require JavaScript in order to work properly. Make sure you enable JavaScript in your browser. </div> </noscript> <!-- Alerts and messages --> You need a token to access /manager/download/ubuntu-2004-amd64-main-security-uyuni/repodata/InRelease </section> </div> <script type="text/javascript"> spaImportReactPage('shared/menu'); window.pageRenderers && window.pageRenderers.spaengine.init && window.pageRenderers.spaengine.init(); </script> </div> <button id="scroll-top"><i class='fa fa-angle-up'></i></button> </body> </html> * Connection #0 to host myuniserver.mydomain left intact -- *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 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 https://github.com/uyuni-project/uyuni/pull/3147 and https://github.com/uyuni-project/uyuni/pull/2572 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://myuniserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd6... 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. *From:* Pau Garcia <pau.garcia@suse.com> *Sent:* Tuesday, January 26, 2021 1:18 AM *To:* Paul-Andre Panon <paul-andre.panon@avigilon.com>; users@lists.uyuni-project.org *Subject:* Re: Registration problems with Ubuntu 20.04 and Uyuni Hello Have you checked this? https://www.uyuni-project.org/uyuni-docs/uyuni/administration/tshoot-registe... <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.uyuni-2Dproject.org_uyuni-2Ddocs_uyuni_administration_tshoot-2Dregisterclones.html&d=DwMF-g&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=1eukOzzSEjOtVn2k1EHN31r5jyNgS5MGJsmhyH8zORk&s=f_jplxDISPWHgOxPvgeHoTERl7TEsIFO6RV6bBD8GIU&e=> Troubleshooting Registering Cloned Clients :: Uyuni Documentation <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.uyuni-2Dproject.org_uyuni-2Ddocs_uyuni_administration_tshoot-2Dregisterclones.html&d=DwMF-g&c=q3cDpHe1hF8lXU5EFjNM_A&r=2sQoWEMcncSKL5kWoc_nrZbhUyhuj8tJfA91_lDSglQ&m=1eukOzzSEjOtVn2k1EHN31r5jyNgS5MGJsmhyH8zORk&s=f_jplxDISPWHgOxPvgeHoTERl7TEsIFO6RV6bBD8GIU&e=> If you are using Uyuni to manage virtual machines, you might find it useful to create clones of your VMs. A clone is a VM that uses a primary disk that is an exact copy of an existing disk. www.uyuni-project.org Thank you Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager SUSE Software Solutions Spain ------------------------------ *From:* Paul-Andre Panon <paul-andre.panon@avigilon.com> *Sent:* Tuesday, January 26, 2021 8:30 AM *To:* users@lists.uyuni-project.org <users@lists.uyuni-project.org> *Subject:* Registration problems with Ubuntu 20.04 and Uyuni Hi, I’m trying to set up an Uyuni server to replace a Spacewalk server, starting with setting up support for Ubuntu 20.04. Ideally we would like to be able to use a vSphere VM template that we can use to generate/clone new VMs, and then run a script on that new VM to customize it with the specific desired hostname, AD domain registration, and Uyuni registration. For the Uyuni registration, I started with the generated bootstrap script and customized it with an Activation Key and the Ubuntu GPG keys (ubuntu-gpg-pubkey-871920D1991BC93C.key,uyuni-gpg-pubkey-0d20833e.key) . The registration script appears to work. If I look in Uyuni’s Salt->Keys page, I see the key, can approve it and the system shows up in the system list…. the first time. On subsequent VMs however, I see the key in the Salt->Keys page, can approve them, and then after some time I only see one of the two VMs in the system list, usually the last one added. While setting up the Uyuni server and VM template, it took me a while to figure out I was supposed to use the modified bootstrap script, so I had first tried to install salt packages on the template and thought that might be the problem. I took a hint from the bootstrap script and tried to run apt-get purge salt-minion apt-get purge salt-common rm -rf /etc/salt/minion.d/ on the template to clear any salt state, cleared systems and keys on the Uyuni server, and started over creating new VMs,… with the same result. Any suggestions on what could be going wrong? Thanks, Paul-Andre Panon, B.Sc. Senior Systems Administrator Video Security & Analytics *o:* +1.604.629.5182 ext 2190 *m*: +1.604.787.4547 *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, 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@dc1-ubun20test:/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://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-uyuni-client main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-main-uyuni main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download 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>.*
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@dc1-ubun20test:/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://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-main-security-uyuni main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download ubuntu-20.04-pool-amd64-uyuni main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-uyuni-client main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-universe-updates-uyuni main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-main-uyuni main deb [trusted=yes] https://myserver.mydomain:443/rhn/manager/download 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>.*
participants (4)
-
Michele Bologna -
Pau Garcia -
Paul-Andre Panon -
Robert Paschedag