From 98fd78e2b63813d31c866b49372e781ac5a63d09 Mon Sep 17 00:00:00 2001 From: Peter Ajamian Date: Mon, 31 May 2021 21:12:32 +1200 Subject: [PATCH] Add a "known issues" section to the README Add a section to the README file for known issues so that we don't have to repeatedly answer questions about them in sujpport channels. --- README.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/README.md b/README.md index b9800d1..87626f0 100644 --- a/README.md +++ b/README.md @@ -19,6 +19,30 @@ Running this script will convert an existing CentOS 8 system to Rocky Linux 8. [!! USE WITH CAUTION !!] ``` +### Known Issues + +#### RHEL migrations show error messages during conversion + +``` + Installing : rocky-release-8.3-13.el8.noarch 2/5Error unpacking rpm package rocky-release-8.3-13.el8.noarch +... +error: unpacking of archive failed on file /usr/share/redhat-release: cpio: File from package already exists as a directory in system +error: rocky-release-8.3-13.el8.noarch: install failed +Error: Transaction failed +``` + +This results from conflicts in the directory structure of RHEL with that of +RockyLinux. migrate2rocky will detect the issue and go on to remove the +conflicting directory and install rocky-release with the rpm command. + +#### Grub still shows kernel entries from previous installation + +This is normal. The running kernel cannot be safely removed when migrate2rocky +is run. The RockyLinux kernel should come up as the default highlighed kernel +on reboot but the other ones will remain until they are removed or replaced by +newer kernels. If you want you can manually remove the old kernels after reboot +with dnf or rpm. + ### Debugging The `migrate2rocky` script pipes everything shown on `stdout` and `stderr` to