Upgrade issues almalinux 9

Upgrade from centos 7 AlmaLinux 9 package issue.

I am currently in midprocess of upgrading. I upgraded centos then upgraded to AlmaLinux 8 and now upgrading to almalinux 9. I am stuck at the beginning of the process of the upgrade to 9

The step I am at…

yum install -y http://repo.almalinux.org/elevate/elevate-release-latest-el$(rpm --eval %rhel).noarch.rpm

  • Install leapp packages and upgrade data for AlmaLinux:

yum install -y leapp-upgrade leapp-data-almalinux

The repo installs fine BUT when I try to do the install of leapp-upgrade and leapp-data-almalinux the leapp-data-almalinux comes up as “Unable to find a match for leapp-data-almalinux”.

Any help here would be awesome as I have the VM sitting waiting for me to continue.

Lee

Is the elevate repo enabled?
Please post the output of dnf repoinfo and rpm -q elevate-release.

yum repoinfo then?

Actually, if you don’t have dnf installed, did you really successfully upgrade to AlmaLinux 8?

Sry Typo…

It’s the same for me so leapp-data-almalinux should exist.

Repo-id            : elevate
Repo-name          : ELevate
Repo-revision      : 1749122658
Repo-updated       : Thu Jun  5 11:24:18 2025
Repo-pkgs          : 91
Repo-available-pkgs: 91
Repo-size          : 25 M
Repo-baseurl       : https://repo.almalinux.org/elevate/el8/x86_64/
Repo-expire        : 172800 second(s) (last: Thu Jun 26 10:45:47 2025)
Repo-filename      : /etc/yum.repos.d/ELevate.repo
[root@dc4b6e0f600b /]# dnf info leapp-data-almalinux
Last metadata expiration check: 0:00:46 ago on Thu Jun 26 10:45:47 2025.
Available Packages
Name         : leapp-data-almalinux
Version      : 0.9
Release      : 1.el8.20250505
Architecture : noarch
Size         : 501 k
Source       : leapp-data-almalinux-0.9-1.el8.20250505.src.rpm
Repository   : elevate
Summary      : data for migrating tool
URL          : https://github.com/AlmaLinux/leapp-data
License      : ASL 2.0
Description  : almalinux data for migrating tool

Can you post the full output of the install command you ran?

This install for the repo?

Looks like there’s a typo: leap-data-almalinux → leapp-data-almalinux

Try dnf install leapp-data-almalinux again.

That worked thanks for catching that. silly mistake

1 Like

New problem…

“auth substack password-auth” is missing from the /etc/pam.d/sshd so I can’t log in via ssh. I edit the file as root and save and I look at the file and it did not really save??

I am hoping this is the auth problem I am having

You can remove the file, then run dnf reinstall openssh-server to restore the default config.

No did not work. Still missing substack setting

I completely removed sshd and reinstalled and still the same issue

:man_shrugging:
Can you post the output of authselect current and ls -l /etc/pam.d

-rw-r–r-- 1 root root 272 Oct 14 2022 atd
-rw-r–r-- 1 root root 192 Mar 13 02:30 chfn
-rw-r–r-- 1 root root 192 Mar 13 02:30 chsh
-rw-r–r-- 1 root root 232 Jun 24 12:32 config-util
-rw-r–r-- 1 root root 322 Feb 15 2019 crond
-r–r–r-- 1 root root 146 Mar 12 09:38 cups
lrwxrwxrwx 1 root root 32 Jun 26 11:45 fingerprint-auth → /etc/authselect/fingerprint-auth
-rw-r–r-- 1 root root 702 Jun 25 17:27 fingerprint-auth-ac
-rw-r–r-- 1 root root 701 Nov 26 2024 fingerprint-auth.rpmnew
-rw-r–r-- 1 root root 622 Jul 23 2021 gdm-autologin
-rw-r–r-- 1 root root 561 Jul 23 2021 gdm-fingerprint
-rw-r–r-- 1 root root 307 Jul 23 2021 gdm-launch-environment
-rw-r–r-- 1 root root 856 Sep 19 2024 gdm-password
-rw-r–r-- 1 root root 787 Jul 7 2021 gdm-password.orig
-rw-r–r-- 1 root root 813 Sep 19 2024 gdm-password.prev
-rw-r–r-- 1 root root 800 Jul 23 2021 gdm-pin
-rw-r–r-- 1 root root 553 Jul 23 2021 gdm-smartcard
-rw-r–r-- 1 root root 676 Mar 13 02:30 login
-rw-r–r-- 1 root root 796 Apr 5 2023 login.orig
-rw------- 1 root root 0 Jun 27 06:44 lsal.txt
-rw-r–r-- 1 root root 154 Jun 24 12:32 other
-rw-r–r-- 1 root root 168 Apr 14 2022 passwd
lrwxrwxrwx 1 root root 29 Jun 26 11:45 password-auth → /etc/authselect/password-auth
-rw-r–r-- 1 root root 971 Jun 25 17:27 password-auth-ac
-rw-r–r-- 1 root root 971 Sep 2 2020 password-auth.orig
-rw-r–r-- 1 root root 760 Nov 26 2024 password-auth.rpmnew
-rw-r–r-- 1 root root 510 Mar 12 19:14 pluto
-rw-r–r-- 1 root root 155 Oct 3 2024 polkit-1
-rw-r–r-- 1 root root 71 Feb 21 06:44 postgresql
lrwxrwxrwx 1 root root 25 Jun 26 11:45 postlogin → /etc/authselect/postlogin
-rw-r–r–. 1 root root 330 Jun 25 17:15 postlogin-ac
-rw-r–r-- 1 root root 398 Nov 26 2024 postlogin.rpmnew
-rw-r–r-- 1 root root 144 Mar 25 2022 ppp
-rw-r–r-- 1 root root 640 Mar 13 02:30 remote
-rw-r–r-- 1 root root 143 Mar 13 02:30 runuser
-rw-r–r-- 1 root root 138 Mar 13 02:30 runuser-l
-rw-r–r-- 1 root root 177 Jun 20 14:31 samba
lrwxrwxrwx 1 root root 30 Jun 26 11:45 smartcard-auth → /etc/authselect/smartcard-auth
-rw-r–r-- 1 root root 754 Jun 25 17:27 smartcard-auth-ac
-rw-r–r-- 1 root root 743 Jun 24 12:32 smartcard-auth.rpmnew
lrwxrwxrwx 1 root root 25 Jun 25 16:18 smtp → /etc/alternatives/mta-pam
-rw-r–r-- 1 root root 76 Oct 2 2024 smtp.postfix
-rw-r–r-- 1 root root 715 Jun 27 06:16 sshd
-rw------- 1 root root 892 Jun 27 06:05 sshd.bac
-rw-r–r-- 1 root root 894 Jun 30 2021 sshd.orig
-rw-r–r-- 1 root root 689 Jun 27 06:16 sshd.prev
-rw-r–r-- 1 root root 727 Feb 19 15:59 sshd.rpmnew
-rw-r–r-- 1 root root 715 Jun 27 06:10 sshd.rpmsave
-rw-r–r-- 1 root root 566 Mar 13 02:30 su
-rw-r–r-- 1 root root 154 Feb 13 2024 sudo
-rw-r–r-- 1 root root 178 Feb 13 2024 sudo-i
-rw-r–r-- 1 root root 137 Mar 13 02:30 su-l
lrwxrwxrwx 1 root root 27 Jun 26 11:45 system-auth → /etc/authselect/system-auth
-rw-r–r-- 1 root root 971 Jun 25 17:27 system-auth-ac
-rw-r–r-- 1 root root 971 Sep 2 2020 system-auth.orig
-rw-r–r-- 1 root root 760 Nov 26 2024 system-auth.rpmnew
-rw-r–r-- 1 root root 414 Jun 24 09:02 systemd-user
-rw-r–r-- 1 root root 84 Mar 13 04:14 vlock
-rw-r–r-- 1 root root 159 Jun 17 10:28 vmtoolsd
-rw-r–r-- 1 root root 335 Oct 2 2024 vsftpd
-rw-r–r-- 1 root root 163 Jun 23 06:34 xserver

I have no idea, honestly.
Maybe some third party software is interfering.
see: Can't login via ssh using password after migration - Rocky Linux Help & Support - Rocky Linux Forum

Note: a new problem could be a new thread.

The sshd of el9 did finally got support for /etc/ssh/sshd_config.d/
That is a directory where one can drop in additional config files. Some packages already do.
One should not edit the /etc/ssh/sshd_config

The /etc/ssh/sshd_config includes *.conf files from /etc/ssh/sshd_config.d/ first.

A thing about sshd is that if you set an option more than once in config, then the first occurrence is used. Hence content of /etc/ssh/sshd_config.d/ might override whatever you append into /etc/ssh/sshd_config
Therefore, add your options to file /etc/ssh/sshd_config.d/00-site.conf to mask later config.


Root can run sshd -T to see effective config.