pve6to7 - Adding 'diversion of /usr/sbin/grub-install to /usr/sbin/grub-install.real by pve-kernel-helper'

[Arnaud F.]

Hello,

I runned the pve6to7 command in order to check if everything is okay before thinking about migrating from 6 to 7 and here is the result :

= CHECKING VERSION INFORMATION FOR PVE PACKAGES =

Checking for package updates..
PASS: all packages uptodate

Checking proxmox-ve package version..
Use of uninitialized value in pattern match (m//) at /usr/share/perl5/PVE/CLI/pve6to7.pm line 170.
Use of uninitialized value $maj in numeric gt (>) at /usr/share/perl5/PVE/CLI/pve6to7.pm line 174.
Use of uninitialized value $maj in numeric ge (>=) at /usr/share/perl5/PVE/CLI/pve6to7.pm line 177.
FAIL: proxmox-ve package is too old, please upgrade to >= 6.4-1!

Checking running kernel version..
PASS: expected running kernel '5.4.114-1-pve'.

= CHECKING CLUSTER HEALTH/SETTINGS =

SKIP: standalone node.

= CHECKING HYPER-CONVERGED CEPH STATUS =

SKIP: no hyper-converged ceph setup detected!

= CHECKING CONFIGURED STORAGES =

SKIP: storage 'local' disabled.
PASS: storage 'ssd' enabled and active.
PASS: storage 'storage' enabled and active.

= MISCELLANEOUS CHECKS =

INFO: Checking common daemon services..
PASS: systemd unit 'pveproxy.service' is in state 'active'
PASS: systemd unit 'pvedaemon.service' is in state 'active'
PASS: systemd unit 'pvestatd.service' is in state 'active'
INFO: Checking for running guests..
WARN: 8 running guest(s) detected - consider migrating or stopping them.
INFO: Checking if the local node's hostname 'server' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '10.243.36.2' configured and active on single interface.
INFO: Checking backup retention settings..
WARN: storage 'storage' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
WARN: storage 'local' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking custom roles for pool permissions..
INFO: Checking node and guest description/note legnth..
PASS: All node config descriptions fit in the new limit of 64 KiB
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
WARN: The following CTs have 'lxc.cgroup' keys configured, which will be ignored in the new default unified cgroupv2:
CT 115
Often it can be enough to change to the new 'lxc.cgroup2' prefix after the upgrade to Proxmox VE 7.x
INFO: Checking storage content type configuration..
PASS: no problems found
INFO: Checking if the suite for the Debian security repository is correct..
INFO: Make sure to change the suite of the Debian security repository from 'buster/updates' to 'bullseye-security' - in /etc/apt/sources.list:4
SKIP: NOTE: Expensive checks, like CT cgroupv2 compat, not performed without '--full' parameter

= SUMMARY =

TOTAL: 21
PASSED: 12
SKIPPED: 4
WARNINGS: 4
FAILURES: 1

ATTENTION: Please check the output for detailed information!
Try to solve the problems one at a time and then run this checklist tool again.

Seeing error I took a look at this particular and is not installed:

# dpkg -l |grep proxmox
rc  proxmox-ve                           4.4-87                                  all          The Proxmox Virtual Environment

And therefore installed it :

# apt install proxmox-ve
Reading package lists... Done
Building dependency tree    
Reading state information... Done
The following additional packages will be installed:
  proxmox-archive-keyring pve-kernel-helper
The following NEW packages will be installed:
  proxmox-archive-keyring proxmox-ve pve-kernel-helper
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 23.2 kB of archives.
After this operation, 105 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://download.proxmox.com/debian buster/pve-no-subscription amd64 proxmox-archive-keyring all 1.1 [5,480 B]
Get:2 http://download.proxmox.com/debian buster/pve-no-subscription amd64 pve-kernel-helper all 6.4-19 [12.1 kB]
Get:3 http://download.proxmox.com/debian buster/pve-no-subscription amd64 proxmox-ve all 6.4-1 [5,620 B]
Fetched 23.2 kB in 0s (74.1 kB/s)
Selecting previously unselected package proxmox-archive-keyring.
(Reading database ... 90909 files and directories currently installed.)
Preparing to unpack .../proxmox-archive-keyring_1.1_all.deb ...
Unpacking proxmox-archive-keyring (1.1) ...
Selecting previously unselected package pve-kernel-helper.
Preparing to unpack .../pve-kernel-helper_6.4-19_all.deb ...
Adding 'diversion of /usr/sbin/grub-install to /usr/sbin/grub-install.real by pve-kernel-helper'
Unpacking pve-kernel-helper (6.4-19) ...
Selecting previously unselected package proxmox-ve.
Preparing to unpack .../proxmox-ve_6.4-1_all.deb ...
Unpacking proxmox-ve (6.4-1) ...
Setting up pve-kernel-helper (6.4-19) ...
Setting up proxmox-archive-keyring (1.1) ...
Setting up proxmox-ve (6.4-1) ...

My question is about this line :

Adding 'diversion of /usr/sbin/grub-install to /usr/sbin/grub-install.real by pve-kernel-helper'

What should I really do?
Can I just ignore it or next time I will reboot the server won't restart because of failing grub-install?

 

[Stoiko Ivanov]

Can I just ignore

more or less this change was introduced with PVE 6.4 - the background is explained in:

https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool

put shortly - the diversion is there on purpose and should not have any negative consequences for you