View Issue Details

IDProjectCategoryView StatusLast Update
0000140AlmaLinux-8-OTHERpublic2021-11-01 12:29
Reporterkfujinaga Assigned Toalukoshko  
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
PlatformVirtuozzo Hybrid ServerOSCentOSOS Version8.4
Summary0000140: almalinux-deploy: almalinux-deploy install unnecessary kernel packages in the Virtuozzo/OpenVZ container enviroments.
DescriptionIn the Virtuozzo/OpenVZ container enviroments, each container use host's kernel.
So kernel packages are not installed in the container.

But almalinux-deploy install kernel packages at the migration.
These packages are unnecessary and are not used.
# NOTE: The migration was successful, and AlmaLinux container works fine.

On the other hand, the migration tools of Rocky Linux and CentOS Stream doesn't install kernel packages in the Virtuozzo/OpenVZ container enviroments.

Unnecessary kernel packages cause a misunderstanding for users.
So I want you to fix this problem.
Steps To ReproduceRun almalinux-deploy in the Virtuozzo/OpenVZ container enviroments.

1. Check enviroment before migration

------------
[[email protected] ~]# uname -a
Linux fujinaga-test 4.18.0 #1 SMP Tue Jun 9 12:58:54 MSK 2020 x86_64 x86_64 x86_64 GNU/Linux
[[email protected] ~]# cat /etc/redhat-release
CentOS Linux release 8.4.2105
[[email protected] ~]# ls /boot/
efi grub2
[[email protected] ~]# ls /lib/modules
[[email protected] ~]# rpm -qa |grep kernel
[[email protected] ~]#
------------

No kernel package is installed.

2. Run almalinux-deploy

------------
[[email protected] ~]# bash almalinux-deploy.sh

   ...

Complete!
Run dnf distro-sync -y OK
Restoring of alternatives is done OK
Install AlmaLinux kernel OK
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.18.0-305.19.1.el8_4.x86_64
Found initrd image: /boot/initramfs-4.18.0-305.19.1.el8_4.x86_64.img
done
grep: /boot/grub2/grubenv: No such file or directory
All Secure Boot related packages which were released by not AlmaLinux are reinstalledOK

Migration to AlmaLinux is completed
------------

Migration is completed.
But following message is outputed.
  "grep: /boot/grub2/grubenv: No such file or directory"

3. Check enviroment after migration

------------
[[email protected] ~]# uname -a
Linux fujinaga-test 4.18.0 #1 SMP Tue Jun 9 12:58:54 MSK 2020 x86_64 x86_64 x86_64 GNU/Linux
[[email protected] ~]# cat /etc/redhat-release
AlmaLinux release 8.4 (Electric Cheetah)
[[email protected] ~]# ls /boot/
System.map-4.18.0-305.19.1.el8_4.x86_64
config-4.18.0-305.19.1.el8_4.x86_64
efi
grub2
initramfs-4.18.0-305.19.1.el8_4.x86_64.img
loader
vmlinuz-4.18.0-305.19.1.el8_4.x86_64
[[email protected] ~]# ls /lib/modules
4.18.0-305.19.1.el8_4.x86_64
[[email protected] ~]# rpm -qa |grep kernel
kernel-core-4.18.0-305.19.1.el8_4.x86_64
kernel-4.18.0-305.19.1.el8_4.x86_64
kernel-modules-4.18.0-305.19.1.el8_4.x86_64
[[email protected] ~]#
------------

Kernel packages are installed.

These kernel packages are unnecessary.
If the container is restarted, the container use host's kernel.
TagsNo tags attached.
abrt_hash
URL

Activities

alukoshko

2021-11-01 12:29

developer   ~0000369

Hi. Thanks for report.
Right now almalinux-deploy detects only LXC containers, we're working on detection of others too.

Issue History

Date Modified Username Field Change
2021-10-31 06:27 kfujinaga New Issue
2021-11-01 12:27 alukoshko Assigned To => alukoshko
2021-11-01 12:27 alukoshko Status new => assigned
2021-11-01 12:29 alukoshko Note Added: 0000369