Re: [uyuni-users] repo issue?
On miércoles, 31 de julio de 2019 21:21:38 (CEST) David Mace wrote:
Will there be a bug fix release afterwards? For example some important functionality is still broken like cobbler sync to proxies.
Not exactly. The model Uyuni intends to follow is that of a rolling release. There will be a next release after this one (most probably 4.1.0) with bugfixing and probably more features. Regarding https://github.com/uyuni-project/uyuni/issues/1200 (cobbler sync to proxy fails) it's part of the functionality provided by Uyuni, so should get a fix. Sadly we had a lot of work adapting Uyuni to openSUSE 15.1 because of the switch of many components (JDK version, python2->python3, etc), and then summer just caught us and we had less people available to get Uyuni stable enough for a release. That is the reason it took us so long to get this version ready. However my expectation is to have a new release soon (let's say 4-6 weeks), and meanwhile keep working on having a public CI with two things in mind: 1. Providing feedback to the contributors 2. Getting their help to get the product stable more quickly.
Also although unsupported, will it be possible to zypper in --force a switch from 4.0.2-dev in master to this stable release?
It is a conditional "it depends". RPMs should be able to update, but you will need to make sure on your own that the database schema is coherent. Nothing official, but my suggestion is: - Take note of your current susemanager-schema version (4.0.X, let's call it current_version) - Apply the upgrade procedure. - Take note of the susemanager-schema version installed by the update (should be 4.0.13) - This will create a log at /var/log/spacewalk/schema-upgrade where you will see lines like "SQL> select 'susemanager-schema-3.2.18-to-susemanager- schema-3.2.19/002-alter-susesaltevent.sql.postgresql' from dual;" for each SQL script applied. - Then review /etc/sysconfig/rhn/schema-upgrade/ and verify if everything from the migration path from current_version up to 4.0.13 was applied. If something is missing, you will need to apply it manually: $ sudo su - postgres $ psql -f <SQL_SCRIPT> <yourdbname-usually-uyuni> But of course, despite you already said it, I have to repeat it: it is not supported in anyway and could bring problems in the future.
Thanks
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
participants (1)
-
Julio Gonzalez