Hi List, hi Julio, yes, you are right, output is from my test system that was installed from a repo snapshot (to get the same uyuni version we are running on prod): I returned to my snapshot from before the upgrade and this is the result of zypper lr --url: # zypper lr --url Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh | URI ---+---------------------------+------------------------------------+---------+-----------+---------+------------------------------------------------------------------------------------------------------------------------------------- 1 | openSUSE-Leap-15.2-1 | openSUSE-Leap-15.2-1 | No | ---- | ---- | cd:/?devices=/dev/disk/by-id/ata-VMware_Virtual_SATA_CDRW_Drive_00000000000000000001 2 | repo-debug | Debug Repository | No | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.2/repo/oss/ 3 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.2/repo/non-oss/ 4 | repo-debug-update | Update Repository (Debug) | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.2/oss/ 5 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.2/non-oss/ 6 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.2/repo/non-oss/ 7 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.2/repo/oss/ 8 | repo-source | Source Repository | No | ---- | ---- | http://download.opensuse.org/source/distribution/leap/15.2/repo/oss/ 9 | repo-source-non-oss | Source Repository (Non-OSS) | No | ---- | ---- | http://download.opensuse.org/source/distribution/leap/15.2/repo/non-oss/ 10 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.2/oss/ 11 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | ( p) Yes | Yes | http://download.opensuse.org/update/leap/15.2/non-oss/ 12 | uyuni-server-2021-02 | uyuni-server-2021-02 | Yes | (r ) Yes | No | https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapsho... So if this is the expected behavior when using a repo snapshot, then everything is fine for me, because my prod was installed using "latest" and I can assume this problem won't occur there. Maybe you could add a hint into future upgrade docs to inform that this is normal when coming from a snapshotted repo? Or as an alternative let the script check repo urls first and warn only if a snapshot is used? Thanks for this very fast reply! BR Heiner Am Mi., 1. Sept. 2021 um 16:17 Uhr schrieb Julio Gonzalez < jgonzalez@suse.com>:

On miércoles, 1 de septiembre de 2021 15:49:53 (CEST) Heiner Wulfhorst wrote:

...

Hi List,

first i ran zypper ref and zypper up susemanager which said " *No update candidate*, *The highest available version is already installed* , Nothing to do ": # *zypper ref* Repository 'Non-OSS Repository' is up to date. Repository 'Main Repository' is up to date. Repository 'Main Update Repository' is up to date. Repository 'Update Repository (Non-Oss)' is up to date. Repository 'uyuni-server-2021-02' is up to date.

This part looks strange. The repository should not mention the version at all. Stable is Stable and it's a rolling release.

Looks as if you were using one of snapshot repositories. But since you executed the migration script twice, I think those repositores are gone from your system and we can't confirm my suspcions.

After this, it seems the server-migratior you applied is the old one, meaning the it pointed again to the Stable repositories, but kept 15.2

After that the update for susemanager with the migration to 15.3 became available.

First if all, I hope there's a backup.

If you still didn't call pg-migrate-10-to-12.sh or pg-migrate-x-to-y.sh, you should be able to call `server-migrator.sh` again, and the the script should not report errors and it should upgrade a lot of packages (Uyuni to 2021.08, and Leap from 15.2 to 15.3)

If that works, the follow the rest of the upgrade procedure normally.

If it doesn't, then please restore the backup and provide the output of:

zypper lr --url

...

*All repositories have been refreshed.* # *zypper up susemanager* Loading repository data... Reading installed packages... *No update candidate for 'susemanager-4.2.8-1.1.uyuni.x86_64'. The highest available version is already installed.* Resolving package dependencies... *Nothing to do.*

But then i got this error when running /usr/lib/susemanager/bin/ server-migrator.sh (for full output see attachment):

Computing distribution upgrade... 5 Problems: Problem: nothing provides 'postgresql13' needed by the to be installed spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch Problem: nothing provides 'libcrypt.so.1(XCRYPT_2.0)(64bit)' needed by the to be installed jabberd-sqlite-2.7.0-5.5.uyuni1.x86_64 Problem: nothing provides 'product(Leap) >= 15.3' needed by the to be installed product:Uyuni-Server-2021.08-0.x86_64 Problem: nothing provides 'product(Leap) >= 15.3' needed by the to be installed product:Uyuni-Server-2021.08-0.x86_64 Problem: nothing provides 'postgresql13' needed by the to be installed spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch

Problem: nothing provides 'postgresql13' needed by the to be installed spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch Solution 1: Following actions will be done: deinstallation of spacewalk-postgresql-4.2.3-1.2.uyuni.noarch deinstallation of spacewalk-common-4.2.3-1.2.uyuni.noarch Solution 2: keep obsolete spacewalk-postgresql-4.2.3-1.2.uyuni.noarch Solution 3: break spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): c

=================================================================== If you did not yet migrate the database to postgresql12, do so now by running /usr/lib/susemanager/bin/pg-migrate-10-to-12.sh

Reboot system afterwards. ===================================================================

After that error i ran zypper ref and zypper up susemanager again, which (whyever) then found this update for susemanager: # zypper ref Repository 'Non-OSS Repository' is up to date. Repository 'Main Repository' is up to date. Repository 'Main Update Repository' is up to date. Repository 'Update Repository (Non-Oss)' is up to date. Repository 'Uyuni Server Stable' is up to date. All repositories have been refreshed.

# zypper up susemanager Loading repository data... Reading installed packages... Resolving package dependencies...

The following package is going to be upgraded: susemanager

1 package to upgrade. Overall download size: 83.8 KiB. Already cached: 0 B. After the operation, additional 14.0 KiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package susemanager-4.3.2-1.1.uyuni1.x86_64 (1/1), 83.8 KiB (197.6 KiB unpacked) Retrieving: susemanager-4.3.2-1.1.uyuni1.x86_64.rpm

............................................................................

...

.................[done]

Checking for file conflicts:

............................................................................

...

........................................[done] (1/1) Installing: susemanager-4.3.2-1.1.uyuni1.x86_64

............................................................................

...

...............[done] Executing %posttrans scripts

............................................................................

...

........................................[done]

After that i ran /usr/lib/susemanager/bin/server-migrator.sh again which then returned no more errors/problems and began to upgrade my system: <...> Executing %posttrans scripts

............................................................................

...

........................................[done] Update notifications were received from the following packages: susemanager-schema-4.3.1-1.2.uyuni1.noarch (/var/adm/update-messages/susemanager-schema-4.3.1-1.2.uyuni1) View the notifications now? [y/n] (n): n There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs.

Since the last system boot core libraries or services have been updated. Reboot is suggested to ensure that your system benefits from these updates.

=================================================================== If you did not yet migrate the database to postgresql13, do so now by running /usr/lib/susemanager/bin/pg-migrate-x-to-y.sh

Reboot system afterwards. ===================================================================

What went wrong? Is there an error in the upgrade guide ( https://www.uyuni-project.org/doc/2021.08/uyuni_upgrade_guide.pdf)? Looks like at first try it is using leap/15.2 repos and at second try 15.3...

BR, Heiner

-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com

Hi List, hi Julio, you are right, my fault, i was warned about using the repo snapshot but totally forgot about being on such a snapshot when i tried the upgrade. So yes, if server-migrator would just remind ppl they are using an unsupported version and they should at least modify repo URLs etc., that would be great! Thanks for helping! BR Heiner Am Do., 2. Sept. 2021 um 10:46 Uhr schrieb Julio Gonzalez < jgonzalez@suse.com>:

<...> Strictly speaning, Snapshot are not supported or even announced at any place (we discussed them a couple of times at the mailing lists, as they are useful to debug problems, which is the reason we create them).

But since I understand the use case, FMPOV the best approach here is for the server-migrator script to exit with an error and maybe provide some hint (basically change the URL for the Uyuni Server repo and then update the `susemanager` package again). <...> -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com