pvetest, aptitude full-upgrade removes running kernel

[RobFantini]

When I changed a test system to use pvetest the running kernel gets removed:

uname -a 
Linux fbc73 2.6.32-14-pve #1 SMP Tue Aug 21 08:24:37 CEST 2012 x86_64 GNU/Linux

from /var/log/aptitude :

===============================================================================
[REMOVE, NOT USED] pve-kernel-2.6.32-14-pve
[INSTALL, DEPENDENCIES] attr
[INSTALL, DEPENDENCIES] dtach
[INSTALL, DEPENDENCIES] libcgroup1
[INSTALL, DEPENDENCIES] pve-kernel-2.6.32-15-pve
[UPGRADE] ceph-common 0.48argonaut-1~bpo60+1 -> 0.48.2argonaut-1~bpo60+1
[UPGRADE] corosync-pve 1.4.3-1 -> 1.4.4-1
[UPGRADE] fence-agents-pve 3.1.8-1 -> 3.1.9-1
[UPGRADE] libcorosync4-pve 1.4.3-1 -> 1.4.4-1
[UPGRADE] libiscsi1 1.5.0-1 -> 1.6.0-1
[UPGRADE] libpve-access-control 1.0-24 -> 1.0-25
[UPGRADE] libpve-common-perl 1.0-30 -> 1.0-34
[UPGRADE] libpve-storage-perl 2.0-31 -> 2.0-33
[UPGRADE] librados2 0.48argonaut-1~bpo60+1 -> 0.48.2argonaut-1~bpo60+1
[UPGRADE] librbd1 0.48argonaut-1~bpo60+1 -> 0.48.2argonaut-1~bpo60+1
[UPGRADE] proxmox-ve-2.6.32 2.1-74 -> 2.2-78
[UPGRADE] pve-cluster 1.0-27 -> 1.0-28
[UPGRADE] pve-firmware 1.0-18 -> 1.0-19
[UPGRADE] pve-manager 2.1-14 -> 2.2-21
[UPGRADE] pve-qemu-kvm 1.1-8 -> 1.2-6
[UPGRADE] qemu-server 2.0-49 -> 2.0-59
[UPGRADE] redhat-cluster-pve 3.1.92-3 -> 3.1.93-1
[UPGRADE] vzctl 3.0.30-2pve5 -> 4.0-1pve2
[UPGRADE] vzquota 3.0.12-3 -> 3.1-1

and ls -l /boot:

fbc73 s011 /var/log # ll /boot
total 98222
-rw-r--r-- 1 root root   101491 Apr 11 01:19 config-2.6.32-11-pve
-rw-r--r-- 1 root root   101492 May 15 00:04 config-2.6.32-12-pve
-rw-r--r-- 1 root root   102590 Sep 24 05:18 config-2.6.32-15-pve
drwxr-xr-x 3 root root     7168 Oct  7 19:15 grub/
-rw-r--r-- 1 root root 15867838 Apr 27 09:19 initrd.img-2.6.32-11-pve
-rw-r--r-- 1 root root 15888802 May 18 14:25 initrd.img-2.6.32-12-pve
-rw-r--r-- 1 root root 15947281 Jul 25 12:13 initrd.img-2.6.32-13-pve
-rw-r--r-- 1 root root 16188643 Aug 22 08:48 initrd.img-2.6.32-14-pve
-rw-r--r-- 1 root root 16193559 Oct  7 19:15 initrd.img-2.6.32-15-pve
drwx------ 2 root root    12288 Apr 20 13:23 lost+found/
-rw-r--r-- 1 root root   165084 Oct 21  2010 memtest86+.bin
-rw-r--r-- 1 root root   167264 Oct 21  2010 memtest86+_multiboot.bin
-rw-r--r-- 1 root root  2380725 Apr 11 01:19 System.map-2.6.32-11-pve
-rw-r--r-- 1 root root  2384628 May 15 00:04 System.map-2.6.32-12-pve
-rw-r--r-- 1 root root  2418918 Sep 24 05:18 System.map-2.6.32-15-pve
-rw-r--r-- 1 root root  4054432 Apr 11 01:19 vmlinuz-2.6.32-11-pve
-rw-r--r-- 1 root root  4060544 May 15 00:04 vmlinuz-2.6.32-12-pve
-rw-r--r-- 1 root root  4116032 Sep 24 05:18 vmlinuz-2.6.32-15-pve

is that a bug or something I did wrong?

 

[dietmar]

This seems normal 'aptitude' behavior. AFAIK 'safe-upgrade' does not remove any packages.

 

[RobFantini]

I do not think removing the running kernel is safe.

 

[udo]

I do not think removing the running kernel is safe.

Hi,
this is the reason why Dietmar mean safe-upgrade is in this case better. safe-upgrade != full-upgrade.

If you use "apt-get dist-upgrade" you will allways keep the old kernel (except the kernel has the same name). This is aptitude related and not pve...

Udo

 

[RobFantini]

Udo - I know there is a difference, yet I've always used full-upgrade when using pve not pvetest and have not seen the running kernel removed. For pvetest It could be that the pvetest kernel debian control dependency set up [I am not an expert on the subject ] is set up to remove the pve kernel?

 

[mir]

Hi,
this is the reason why Dietmar mean safe-upgrade is in this case better. safe-upgrade != full-upgrade.

If you use "apt-get dist-upgrade" you will allways keep the old kernel (except the kernel has the same name). This is aptitude related and not pve...

Udo

aptitude full-upgrade will only remove another packages in one of three situations:
1) The package has been marked obsolete
2) The package is replaced by a new package
3) A new package has marked an installed package in conflict with this package or a package this package depend on

If an installed package does not fall under one of the above three categories then uninstalling a package seems like a bug.

In the specific case I see no reason to uninstall an already installed kernel and to the best off my knowledge proxmox has never showed this behavior before.