migration failure with MLNX_OFED_LINUX 4.9 (LTS) installed #158
Comments
|
@pajamian With packages excluded... ...it appears manual With this knowlege it's likely the next migration will go a fair bit more smoothly if not automatically. Thanks for all the work you've put into |
|
@pajamian Final update for this issue report. Migration went more smoothly on the primary headnode of this system with the addition of the exclusion of many/most non-{CentOS|Fedora} packages from the migration via an The excluded packages are all from local installation or install from alternate repositories that After migration and reboot the repositories were re-enabled, the The same general sequence was used to migrate The sequence of commands to build up this list of excludable packages was similar for the physical host and chroot example# ./migrate2rocky.sh -V
# ls -l /root/convert
total 1532
-rw-r--r-- 1 root root 101541 Feb 11 14:05 node-installer-rpm-list-begin.log
-rw-r--r-- 1 root root 1464834 Feb 11 14:05 node-installer-rpm-list-verified-begin.log
# echo "exclude=$(grep -Ev "centos|fedora" /root/convert/node-installer-rpm-list-begin.log | grep -v gpg-pubkey | column -s\| -t | awk '{print $1}' | tr '\n' ' ')" >> /etc/dnf/dnf.conf
# dnf check -v
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, groups-manager, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync
DNF version: 4.7.0
cachedir: /var/cache/dnf
User-Agent: constructed: 'libdnf (CentOS Linux 8; generic; Linux.x86_64)'
Excludes in dnf.conf: MegaCli ar_mgr dapl-devel-static dapl-devel dapl-utils dapl dump_pr elrepo-release hcoll ibacm ibsim ibutils2 infiniband-diags kmod-bnxt_en kmod-elx-lpfc kmod-isert kmod-iser kmod-kernel-mft-mlnx kmod-knem kmod-megaraid_sas kmod-mlnx-ofa_kernel kmod-rshim kmod-srp knem libibumad libibverbs-utils libibverbs librdmacm-utils librdmacm lustre-client-dkms lustre-client mft mlnx-ethtool mlnx-fw-updater mlnx-iproute2 mlnx-ofa_kernel-devel mlnx-ofa_kernel mlnxofed-docs mpi-selector mstflint ofed-scripts openmpi opensm-devel opensm-libs opensm-static opensm perftest qperf rdma-core-devel rdma-core sharp srp_daemon srvadmin-argtable2 srvadmin-hapi srvadmin-idracadm7 telegraf ucx-cma ucx-devel ucx-ib ucx-knem ucx-rdmacm ucx
# ./migrate2rocky.sh -V -r
migrate2rocky - Begin logging at Fri Feb 11 14:15:00 2022.
Creating a list of RPMs installed: begin
Verifying RPMs installed against RPM database: begin
Removing dnf cache
Preparing to migrate CentOS Linux 8 to Rocky Linux 8.
Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist
Baseurl for appstream is invalid, setting to https://dl.rockylinux.org/vault/centos/8.5.2111/AppStream/x86_64/os/.
Error: Failed to download metadata for repo 'baseos': Cannot prepare internal mirrorlist: No URLs in mirrorlist
Baseurl for baseos is invalid, setting to https://dl.rockylinux.org/vault/centos/8.5.2111/BaseOS/x86_64/os/.
Determining repository names for CentOS Linux 8......
Found the following repositories which map from CentOS Linux 8 to Rocky Linux 8:
CentOS Linux 8 Rocky Linux 8
appstream appstream
baseos baseos
extras extras
...<snip>...
xkeyboard-config-2.28-1.el8.noarch
zip-3.0-23.el8.x86_64
zlib-1.2.11-17.el8.x86_64
Removed:
kernel-4.18.0-147.el8.x86_64 kernel-core-4.18.0-147.el8.x86_64
kernel-modules-4.18.0-147.el8.x86_64
Complete!
Creating a list of RPMs installed: finish
Verifying RPMs installed against RPM database: finish
You may review the following files:
/root/convert/node-installer-rpm-list-begin.log
/root/convert/node-installer-rpm-list-finish.log
/root/convert/node-installer-rpm-list-verified-begin.log
/root/convert/node-installer-rpm-list-verified-finish.log
Done, please reboot your system.
A log of this installation can be found at /var/log/migrate2rocky.logIn my experiece with multiple migration attempts on these systems some packages could be safely removed and no longer needed to be excluded explicitly but others could not. Still others would only trigger a failure during transaction processing of I'm not convinced this sequence should be generalized and added explicitly to This might be used to alert the user to the potential list of packages that could break In short, if you feel there is anything useful in this issue that can be added to Otherwise, it'll be fine to clone this issue and perhaps keep it in mind if others show up with similar problems. Clever folks will search the closed issues for hints and maybe stumble on this potential solution without any additional help. Thanks again for all the work on |
|
Well, I think running dnf check ahead of time and checking the result will help. Also it makes me think that package exclusions should be copied over from the source repo to the RockyLinux equivalents, so if there are exclude= lines in, say, appstream currently appstream gets replaced by the rockylinux appstream, and exclusions are lost. that could make the difference between a failing or passing migration at the distro-sync stage. |
|
Copying existing per-repository exclusions does sound like a good addition to |
System is installed with the following which are related to this issue:
This is second migration attempt of development system secondary head node after re-image following initial failed migration with manual resolution.
Previous migration was eventually completed and the system was running Rocky 8.5 with BCM 9.0-17 and MLNX_OFED_LINUX 4.9 (LTS) without issues. In attempt to confirm all issues were resolved the system was restored to pre-migration state, any previous issues (extra installed kernels and remaining rhel8u0 kmods with no matching kernel and missing deps) were resolved and migration was re-attempted.
It seems possible that the addition of
--setopt=<reponame>.excludepkgs=options may resolve (may be able to investigate) and could be supported in a future version ofmigrate2rocky.sh.Configuration of
dnfvia/etc/dnf/dnf.confto ignore MLNX_OFED_LINUX packages may also resolve (for example)......and this will be attempted again via manual resolution with existing Rocky repository configuration in place...
Any additional recommendations for resolving manually would be appreciated.
migrate2rocky.log
The text was updated successfully, but these errors were encountered: