- ARCHIVED: Uyuni Users

Re: Upgrade stuck or not...
by Tim Shaw 05 Mar '21

05 Mar '21

Thanks to several people for the advice. It is now 5 hours with no visible change although postgres is certainly busy... PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 14080 postgres 20 0 3232908 2.918g 2.856g R 99.34 24.89 350:24.35 postgres Files in /var/lib/pgsql/data/pg_stat_tmp/ are constantly changing I will leave it running overnight. I think it would be helpful for the scripts involved in this process to make some sort of report back to the user on progress from time to time! T *Please note I am not normally in the office on Mondays or Fridays* ___________________________________________________________ TIM SHAW - Deputy Director - Network Services Medical Sciences Division - University of Oxford email : tim.shaw(a)medsci.ox.ac.uk tel : +44 (0)1865 289480 >>> Julio González Gil <jgonzalez(a)suse.com> 04/03/2021 17:28 >>> Most likely it's not stuck. At the release notes there's a note for the 2021.01 entry about the PostgreSQL upgrade taking up to several hours depending on the environment. On jueves, 4 de marzo de 2021 17:24:08 (CET) Tim Shaw wrote: > Hello > > Just upgrading today from 2020.03. Yes ‑ from last March. All seems to be > going well but... > > The database migration from 10 to 12 has been sitting without any obvious > progress for over an hour ‑ is it stuck? > > The processes are still running: > > 13756 ? Ss 0:00 /bin/bash /usr/sbin/spacewalk‑startup‑helper > check‑database 13768 ? S 0:08 /usr/bin/perl > /usr/bin/spacewalk‑schema‑upgrade ‑y 14078 ? S 0:00 psql ‑U > uyuni ‑d uyuni ‑h localhost ‑p 5432 ‑v ON_ERROR_STOP=ON ‑f ‑ > > And the screen running the upgrade says: > > 15:03:44 Successfully upgraded database to postgresql 12. > 15:03:44 Tune new postgresql configuration... > INFO: Database configuration has been changed. > INFO: Wrote new general configuration. Backup as > /var/lib/pgsql/data/postgresql.2021‑03‑04‑15‑03‑46.conf INFO: Wrote new > client auth configuration. Backup as > /var/lib/pgsql/data/pg_hba.2021‑03‑04‑15‑03‑46.conf INFO: Configuration has > been changed, but your database is right now offline. Database is offline > System check finished > 15:03:46 Successfully tuned new postgresql configuration. > 15:03:46 Starting spacewalk services... > Starting spacewalk services... > Running DB schema upgrade. This may take a while. > Call the following command to see progress: journalctl ‑f ‑u > uyuni‑check‑database.service > > But this hasn't changed for over an hour: > > spacewalk:~ # journalctl ‑f ‑u uyuni‑check‑database.service > ‑‑ Logs begin at Thu 2021‑03‑04 13:50:15 GMT. ‑‑ > Mar 04 15:03:58 spacewalk spacewalk‑startup‑helper[13756]: Schema upgrade: > [susemanager‑schema‑4.1.7‑1.1.uyuni] ‑> > [susemanager‑schema‑4.2.8‑1.3.uyuni] Mar 04 15:03:58 spacewalk > spacewalk‑startup‑helper[13756]: Searching for upgrade path to: > [susemanager‑schema‑4.2.8‑1] Mar 04 15:03:58 spacewalk > spacewalk‑startup‑helper[13756]: Searching for upgrade path to: > [susemanager‑schema‑4.2.8] Mar 04 15:03:58 spacewalk > spacewalk‑startup‑helper[13756]: Searching for start path: > [susemanager‑schema‑4.1.7‑1] Mar 04 15:03:58 spacewalk > spacewalk‑startup‑helper[13756]: Searching for start path: > [susemanager‑schema‑4.1.7] Mar 04 15:03:58 spacewalk > spacewalk‑startup‑helper[13756]: The path: [susemanager‑schema‑4.1.7] ‑> > [susemanager‑schema‑4.1.8] ‑> [susemanager‑schema‑4.1.9] ‑> > [susemanager‑schema‑4.1.10] ‑> [susemanager‑schema‑4.1.11] ‑> > [susemanager‑schema‑4.2.0] ‑> [susemanager‑schema‑4.2.1] ‑> > [susemanager‑schema‑4.2.2] ‑> [susemanager‑schema‑4.2.3] ‑> > [susemanager‑schema‑4.2.4] ‑> [susemanager‑schema‑4.2.5] ‑> > [susemanager‑schema‑4.2.6] ‑> [susemanager‑schema‑4.2.7] ‑> > [susemanager‑schema‑4.2.8] Mar 04 15:03:58 spacewalk > spacewalk‑startup‑helper[13756]: Planning to run schema upgrade with dir > '/var/log/spacewalk/schema‑upgrade/schema‑from‑20210304‑150358' Mar 04 > 15:03:58 spacewalk spacewalk‑startup‑helper[13756]: Executing > spacewalk‑sql, the log is in > [/var/log/spacewalk/schema‑upgrade/schema‑from‑20210304‑150358‑to‑susemanag > er‑schema‑4.2.8.log]. Mar 04 15:04:01 spacewalk > spacewalk‑startup‑helper[13756]: [2.0K blob data] Mar 04 15:04:03 spacewalk > spacewalk‑startup‑helper[13756]: [2.0K blob data] > > Should I be more patient? Advice welcome! > > T > > *Please note I am not normally in the office on Mondays or Fridays* > ___________________________________________________________ > TIM SHAW ‑ Deputy Director ‑ Network Services > Medical Sciences Division ‑ University of Oxford > email : tim.shaw(a)medsci.ox.ac.uk > tel : +44 (0)1865 289480 ‑‑ Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

3 3

Upgrade stuck or not...
by Tim Shaw 04 Mar '21

04 Mar '21

Hello Just upgrading today from 2020.03. Yes - from last March. All seems to be going well but... The database migration from 10 to 12 has been sitting without any obvious progress for over an hour - is it stuck? The processes are still running: 13756 ? Ss 0:00 /bin/bash /usr/sbin/spacewalk-startup-helper check-database 13768 ? S 0:08 /usr/bin/perl /usr/bin/spacewalk-schema-upgrade -y 14078 ? S 0:00 psql -U uyuni -d uyuni -h localhost -p 5432 -v ON_ERROR_STOP=ON -f - And the screen running the upgrade says: 15:03:44 Successfully upgraded database to postgresql 12. 15:03:44 Tune new postgresql configuration... INFO: Database configuration has been changed. INFO: Wrote new general configuration. Backup as /var/lib/pgsql/data/postgresql.2021-03-04-15-03-46.conf INFO: Wrote new client auth configuration. Backup as /var/lib/pgsql/data/pg_hba.2021-03-04-15-03-46.conf INFO: Configuration has been changed, but your database is right now offline. Database is offline System check finished 15:03:46 Successfully tuned new postgresql configuration. 15:03:46 Starting spacewalk services... Starting spacewalk services... Running DB schema upgrade. This may take a while. Call the following command to see progress: journalctl -f -u uyuni-check-database.service But this hasn't changed for over an hour: spacewalk:~ # journalctl -f -u uyuni-check-database.service -- Logs begin at Thu 2021-03-04 13:50:15 GMT. -- Mar 04 15:03:58 spacewalk spacewalk-startup-helper[13756]: Schema upgrade: [susemanager-schema-4.1.7-1.1.uyuni] -> [susemanager-schema-4.2.8-1.3.uyuni] Mar 04 15:03:58 spacewalk spacewalk-startup-helper[13756]: Searching for upgrade path to: [susemanager-schema-4.2.8-1] Mar 04 15:03:58 spacewalk spacewalk-startup-helper[13756]: Searching for upgrade path to: [susemanager-schema-4.2.8] Mar 04 15:03:58 spacewalk spacewalk-startup-helper[13756]: Searching for start path: [susemanager-schema-4.1.7-1] Mar 04 15:03:58 spacewalk spacewalk-startup-helper[13756]: Searching for start path: [susemanager-schema-4.1.7] Mar 04 15:03:58 spacewalk spacewalk-startup-helper[13756]: The path: [susemanager-schema-4.1.7] -> [susemanager-schema-4.1.8] -> [susemanager-schema-4.1.9] -> [susemanager-schema-4.1.10] -> [susemanager-schema-4.1.11] -> [susemanager-schema-4.2.0] -> [susemanager-schema-4.2.1] -> [susemanager-schema-4.2.2] -> [susemanager-schema-4.2.3] -> [susemanager-schema-4.2.4] -> [susemanager-schema-4.2.5] -> [susemanager-schema-4.2.6] -> [susemanager-schema-4.2.7] -> [susemanager-schema-4.2.8] Mar 04 15:03:58 spacewalk spacewalk-startup-helper[13756]: Planning to run schema upgrade with dir '/var/log/spacewalk/schema-upgrade/schema-from-20210304-150358' Mar 04 15:03:58 spacewalk spacewalk-startup-helper[13756]: Executing spacewalk-sql, the log is in [/var/log/spacewalk/schema-upgrade/schema-from-20210304-150358-to-susemanager-schema-4.2.8.log]. Mar 04 15:04:01 spacewalk spacewalk-startup-helper[13756]: [2.0K blob data] Mar 04 15:04:03 spacewalk spacewalk-startup-helper[13756]: [2.0K blob data] Should I be more patient? Advice welcome! T *Please note I am not normally in the office on Mondays or Fridays* ___________________________________________________________ TIM SHAW - Deputy Director - Network Services Medical Sciences Division - University of Oxford email : tim.shaw(a)medsci.ox.ac.uk tel : +44 (0)1865 289480

4 3

Reminder: Uyuni Community Hours today at 4pm CET
by Pau Garcia 04 Mar '21

04 Mar '21

Hello Join this month's Uyuni Community Hour to know what's new, what's next, ask questions and provide feedback on Uyuni Project, the best tool manage your enterprise Linux systems. Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting<https://clicks.eventbrite.com/f/a/ylvUnm8JwAi2vp_I-i_2yA~~/AAQxAQA~/RgRiGMs…> Or call in (audio only) +34 917 94 59 77,,868473242#<tel:+34917945977,,868473242#> Spain, Madrid Phone Conference ID: 868 473 242# Find a local number<https://clicks.eventbrite.com/f/a/L04b5iUvOa6eXg1B0ZgrHg~~/AAQxAQA~/RgRiGMs…> | Reset PIN<https://clicks.eventbrite.com/f/a/dlcnYzzXBqNDpzuxHNragw~~/AAQxAQA~/RgRiGMs…> Learn More<https://clicks.eventbrite.com/f/a/Y_VRSV09nl9zC1z4aJlecQ~~/AAQxAQA~/RgRiGMs…> | Meeting options<https://clicks.eventbrite.com/f/a/itAB67N-cRlBNcB6nDNK0w~~/AAQxAQA~/RgRiGMs…> Thank you Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager Phone: +34 91 048 7632 SUSE Software Solutions Spain

2 2

Uyuni 2021.02 is released!
by Julio González Gil 01 Mar '21

01 Mar '21

Hello everyone! We are happy to announce the immediate availability of Uyuni 2021.02 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2021.02, including the release notes, documentation, requirements and setup instructions. IMPORTANT: Always review the release notes and all changes since your current Uyuni version. Sometimes special procedures are needed! Some examples are if you are updating from Uyuni <= 2020.06 or if you are updating from Uyuni <= 2021.01 This is mostly a bugfix release, with a couple of important highlights: * Recent Salt CVEs remediation [1] * Prometheus exporters' reverse proxy formula Ubuntu support Please check the release notes for full details. Remember that Uyuni will follow a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be no maintenance of 2021.02 As always, we hope you will enjoy Uyuni 2021.02 and we invite everyone of you to send us your feedback [2] and of course your patches, if you can contribute. Happy hacking! [1] https://saltproject.io/security_announcements/active-saltstack-cve-release-… [2] https://www.uyuni-project.org/pages/contact.html -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Uyuni Community Hours
by Pau Garcia 26 Feb '21

26 Feb '21

________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting<https://teams.microsoft.com/l/meetup-join/19%3ameeting_OTIyZTM4OWUtNWQ5Ni00…> Or call in (audio only) +34 917 94 59 77,,861379706#<tel:+34917945977,,861379706#> Spain, Madrid Phone Conference ID: 861 379 706# Find a local number<https://dialin.teams.microsoft.com/58c3986f-4c3a-4b77-b4e8-f431171ef66d?id=…> | Reset PIN<https://mysettings.lync.com/pstnconferencing> Learn More<https://aka.ms/JoinTeamsMeeting> | Meeting options<https://teams.microsoft.com/meetingOptions/?organizerId=83d1ce03-a2c8-4530-…> ________________________________________________________________________________

1 0

Open positions to work on Uyuni!
by Johannes Renner 17 Feb '21

17 Feb '21

Hello, for those of you who might be interested but were not present during the last community hour: We currently have two open positions at SUSE (with flexible location) to work on Uyuni full-time, and if you are familiar with the project or if you are already a contributor this would be a great advantage! Here are the links to those positions: https://jobs.suse.com/us/en/job/71000171/Software-Engineer-Flexible-Location https://jobs.suse.com/us/en/job/71000288/Software-Engineer-Flexible-Location Please reach out to me in case you have any questions. Otherwise feel free to apply directly via those pages, or maybe consider to recommend those jobs to your friends. Greetings, Johannes -- Johannes Renner - Engineering Manager, SUSE Manager; R&D SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer

1 0

Conceptual question on configuration management
by Martin Willisegger 10 Feb '21

10 Feb '21

Hello List Suppose I were to manage 100 servers with Uyuni and had to roll out a system configuration that looked like this: parameterA=value1 parameterB=value2 parameterC=value3 parameterD=value4 On most servers it would look the same, but some servers would need e.g. parameterB=value5 parameterD=value6 Other servers would need an additional line: parameterE=value7 And other servers would not need a single parameter #parameterA=value1 Can this requirement be easily managed and clearly displayed via Uyuni's configuration management, and can it be adapted at any time for further requirements or omitted exceptions? Would it only work with fully supported clients (SLES), or also with openSuSE/Uyuni clients via salt? Best regards Martin

3 2

Uyuni 2021.01 fix for /etc/uyuni-release and WebUI version and release notes update
by Julio González Gil 08 Feb '21

08 Feb '21

Hello, Those of you that already updated to 2021.01 maybe already noticed that the WebUI incorrectly says "2021.02", and the same information is present at /etc/uyuni-release [1] We added an update to the Patches repository [2] that can be installed on top of 2021.01 to fix this issue. The patches repository also contains updated release notes with the information about the WebUI not starting because of a vendor change for some Java dependencies [3] To get the fixes installed, follow the next steps (as root) at the Uyuni Server: 1. Install the patches repository (if it's already present, zypper will exit with an error that you can just ignore) zypper ar https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable… 2. Refresh the repositories: zypper ref 3. Stop the services: spacewalk-service stop 4. Run the update (this will get you updates for at least release-notes-uyuni, spacewalk-base, spacewalk-base-minimal, spacewalk-base-minimal-config, spacewalk-common, spacewalk-html, spacewalk-postgresql, susemanager-web-libs and any other pending updates from Leap): zypper up 5. After the update is complete, start the services: spacewalk-service start You will see the correct version 2021.01 at the WebUI, /etc/uyuni-release as well as the updated release notes. NOTE: Starting the services will tell you about a schema upgrade. Do not worry. That is perfectly normal and you will see that message each time you start the services. An upgrade is always attempted, in case there is something pending. [1] https://github.com/uyuni-project/uyuni/issues/3233 [2] https://www.uyuni-project.org/pages/patches.html [3] https://github.com/uyuni-project/uyuni/issues/3230 -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Re: Registration problems with Ubuntu 20.04 and Uyuni
by Paul-Andre Panon 06 Feb '21

06 Feb '21

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-amd64-uyuni/InRelease%0aMessage:%20Connecting%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:%20Connected%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:%20Waiting%20for%20headers <- 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-amd64-uyuni/InRelease 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-uyuni-client/InRelease%0aMessage:%20Waiting%20for%20headers <- 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-uyuni-client/InRelease 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-uyuni-client/InRelease -> https:600%20URI%20Acquire%0aURI:%20https://myserver.mydomain:443/rhn/manager/download/dists/ubuntu-20.04-pool-amd64-uyuni/Release%0aFilename:%20/var/lib/apt/lists/partial/myserver.mydomain:443_rhn_manager_download_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.04-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%0aLast-Modified:%20Tue,%2003%20Nov%202020%2010:18:00%20GMT%0a%0a 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-universe-updates-uyuni/InRelease%0aMessage:%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%0aMessage:%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%0aMessage:%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/download/dists/ubuntu-2004-amd64-universe-updates-uyuni/InRelease 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-universe-updates-uyuni/InRelease 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-universe-uyuni/InRelease%0aMessage:%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-uyuni/InRelease%0aMessage:%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-uyuni/InRelease%0aMessage:%20Waiting%20for%20headers <- 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-universe-uyuni/InRelease Get:11 https://myserver.mydomain:443/rhn/manager/download ubuntu-2004-amd64-universe-uyuni InRelease -----Original Message----- From: Robert Paschedag <robert.paschedag(a)web.de> Sent: Thursday, February 4, 2021 12:18 PM To: Paul-Andre Panon <paul-andre.panon(a)avigilon.com> Cc: Pau Garcia <pau.garcia(a)suse.com>; users(a)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(a)avigilon.com> Gesendet: Thu Feb 04 02:24:35 GMT+01:00 2021 An: Robert Paschedag <robert.paschedag(a)web.de> Cc: Pau Garcia <pau.garcia(a)suse.com>, users(a)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-3A44… ubuntu-2004-amd64-main-security-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A44… ubuntu-20.04-pool-amd64-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A44… ubuntu-2004-amd64-uyuni-client main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A44… ubuntu-2004-amd64-universe-updates-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A44… ubuntu-2004-amd64-universe-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A44… ubuntu-2004-amd64-main-uyuni main deb [trusted=yes] https://urldefense.proofpoint.com/v2/url?u=https-3A__myserver.mydomain-3A44… 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(a)web.de> Sent: Saturday, January 30, 2021 6:38 AM To: Paul-Andre Panon <paul-andre.panon(a)avigilon.com> Cc: Pau Garcia <pau.garcia(a)suse.com>; users(a)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(a)avigilon.com> Gesendet: Wed Jan 27 01:01:40 GMT+01:00 2021 An: Pau Garcia <pau.garcia(a)suse.com>, users(a)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-3… 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?elqTrackI…>.* -- *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?elqTrackI…>.*

2 5

Uyuni 2021.01 is released!
by Julio González Gil 05 Feb '21

05 Feb '21

Hello everyone! We are happy to announce the immediate availability of Uyuni 2021.01 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2021.01, including the release notes, documentation, requirements and setup instructions. IMPORTANT: Keep in mind Uyuni 2020.07 changed the base OS to openSUSE Leap 15.2, so a special procedure is needed if you are not upgrading from 2020.07 or later, but from a previous version! Check the release notes and the documentation for all the details This is the list of highlights for this release: * Fix version comparison algorithm for deb packages (Ubuntu) * New products enabled * SAP content * CPU mitigations formula * Vendor change on SP migration * Autoinstallation of older operating systems * Oracle Linux ULN repositories * CentOS 6 repositories * New countries and timezones * Cluster management: upgrade plan * Yomi refresh * Uyuni Server connections are always and only secure * Monitoring updates - Grafana 7.3.1 - Prometheus 2.22.1 - Prometheus Exporter Exporter for Ubuntu 18.04/20.04 and Debian 9/10 Please check the release notes for full details. For the fixes for salt CVEs, there will be an Uyuni 2021.02 release by the end of February as the fixes rescheduled by upstream [2] Remember that Uyuni will follow a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be no maintenance of 2021.01 As always, we hope you will enjoy Uyuni 2021.01 and we invite everyone of you to send us your feedback [1] and of course your patches, if you can contribute. Happy hacking! [1] https://www.uyuni-project.org/pages/contact.html [2] https://saltproject.io/security_announcements/salt-feb-4th-cve-release-dela… -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 3