QA » openQA Project » openQA Infrastructure

Unsetting since I did not set the target version

The unit is now failing on other worker hosts as well. Somebody is doing something without telling us.

Maybe the activation of the vboxdrv.service unit on the OSD workers is a result of the Leap 15.3 upgrade? Just because it doesn't look like any user played around with it (judging by the login history). The failing unit has been activated as dependency:

martchus@openqaworker6:~> systemctl list-dependencies --reverse vboxdrv
vboxdrv.service
● └─multi-user.target
●   └─graphical.target

The dots of the dependencies are actually green ones. So I'm wondering why the graphical target is active here. Note that VirtualBox was actually always installed as part of our Salt recipes (for x86_64) and now for some reason activating the graphical target also activated its systemd unit which is now failing.

Doesn't work on openqaworker9 and 8:

Dez 15 14:27:35 openqaworker9 vboxdrv.sh[20404]: Kernel modules built correctly. They will now be installed.
Dez 15 14:27:53 openqaworker9 vboxdrv.sh[27672]: modprobe: ERROR: could not insert 'vboxnetflt': Key was rejected by service
Dez 15 14:27:53 openqaworker9 vboxdrv.sh[27672]: modprobe: ERROR: could not insert 'vboxnetadp': Key was rejected by service
Dez 15 14:27:53 openqaworker9 vboxdrv.sh[27672]: insmod /lib/modules/5.3.18-59.37-default/weak-updates/extra/vboxdrv.ko
Dez 15 14:27:53 openqaworker9 vboxdrv.sh[27672]: insmod /lib/modules/5.3.18-59.37-default/weak-updates/extra/vboxdrv.ko
Dez 15 14:27:53 openqaworker9 vboxdrv.sh[20404]: Kernel modules are installed and loaded.
Dez 15 14:27:53 openqaworker9 vboxdrv.sh[20395]: vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
Dez 15 14:27:53 openqaworker9 systemd[1]: vboxdrv.service: Control process exited, code=exited, status=1/FAILURE
Dez 15 14:27:53 openqaworker9 systemd[1]: vboxdrv.service: Failed with result 'exit-code'.
Dez 15 14:27:53 openqaworker9 systemd[1]: Failed to start VirtualBox Linux kernel module.

[  648.407380] vboxdrv: Loading of module with unavailable key is rejected
[  648.422683] vboxdrv: Loading of module with unavailable key is rejected
[  648.442035] vboxdrv: Loading of module with unavailable key is rejected

It has the same kernel running and installed as e.g. openqaworker5 and also the same version of virtualbox-kmp-default.

It is likely because SecureBoot is enabled on these machines:

martchus@openqaworker9:~> sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Key was rejected by service
martchus@openqaworker9:~> sudo mokutil --sb-state
SecureBoot enabled

The SR has been merged. I removed virtualbox from all workers:

sudo salt -C 'G@roles:worker' cmd.run 'zypper --non-interactive rm -u virtualbox'

There were actually more failing systemd units. I disabled postgresql which was failing on grenache-1. Not sure why we need a PostgreSQL database on that host. It is likely a leftover. I removed the mcelog package on openqaworker3 because the corresponding systemd unit failed. The package is not installed on any other worker and there are no mentions of it in our Salt repos so I assume it is also just a leftover.

With that we're back at 0 failing systemd units so the alert should turn off soon.

The alert turned off again, I suppose everything is good now. (Except for openqaworker3 which still needs updating but that's part of the updating ticket.)