March 2021 - ARCHIVED: Uyuni Users - openSUSE Mailing Lists

Post 2021.02 upgrade issues
by Tim Shaw 05 Mar '21

05 Mar '21

Hello Thanks to all who offered advice during the very long 13 hour postgres schema update on my Uyuni system! Since the update completed I've been testing things today and the first issue I see is that hitherto trouble free CentOS7 client systems will now no longer apply patches scheduled from Uyuni. If the packages rather than the patches are scheduled there is no problem. SLES based systems appear to be patching just fine.... The errors look like this: Mar 5 13:40:24 zabbix salt-minion: [ERROR ] An exception occurred in this state: Traceback (most recent call last): Mar 5 13:40:24 zabbix salt-minion: File "/usr/lib/python2.7/site-packages/salt/state.py", line 1939, in call Mar 5 13:40:24 zabbix salt-minion: ret = self.states[cdata['full']](*cdata['args'], **cdata['kwargs']) Mar 5 13:40:24 zabbix salt-minion: File "/usr/lib/python2.7/site-packages/salt/loader.py", line 2006, in wrapper Mar 5 13:40:24 zabbix salt-minion: return f(*args, **kwargs) Mar 5 13:40:24 zabbix salt-minion: File "/usr/lib/python2.7/site-packages/salt/states/pkg.py", line 2160, in patch_installed Mar 5 13:40:24 zabbix salt-minion: targets = _find_advisory_targets(name, advisory_ids, **kwargs) Mar 5 13:40:24 zabbix salt-minion: File "/usr/lib/python2.7/site-packages/salt/states/pkg.py", line 386, in _find_advisory_targets Mar 5 13:40:24 zabbix salt-minion: cur_patches = __salt__['pkg.list_installed_patches'](**kwargs) Mar 5 13:40:24 zabbix salt-minion: File "/usr/lib/python2.7/site-packages/salt/modules/yumpkg.py", line 3273, in list_installed_pat ches Mar 5 13:40:24 zabbix salt-minion: return _get_patches(installed_only=True) Mar 5 13:40:24 zabbix salt-minion: File "/usr/lib/python2.7/site-packages/salt/modules/yumpkg.py", line 3222, in _get_patches Mar 5 13:40:24 zabbix salt-minion: line).groups() Mar 5 13:40:24 zabbix salt-minion: AttributeError: 'NoneType' object has no attribute 'groups' Can anyone offer any ideas as to where to start troubleshooting this please (rebooting the CentOS7 client makes no difference) ? 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

2 1

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