Ticket #9206 (new defect)

Opened 4 years ago

Last modified 4 years ago

VirtualBox RPM dependencies not complete

Reported by: dclark Owned by:
Priority: minor Component: other
Version: VirtualBox 4.0.10 Keywords: kickstart RPM
Cc: Guest type: Linux
Host type: Linux


When installing VirtualBox-4.0-4.0.10_72479_rhel5-1 in a kickstart installation I get the following error in the install.log file:


Installing VirtualBox-4.0-4.0.10_72479_rhel5-1.i386
warning: VirtualBox-4.0-4.0.10_72479_rhel5-1: Header V4 DSA signature: NOKEY, key ID 98ab5139
/etc/init.d/vboxdrv: line 36: /sbin/modprobe: No such file or directory
/etc/init.d/vboxdrv: line 87: /etc/init.d/functions: No such file or directory
/etc/init.d/vboxballoonctrl-service: line 91: /etc/init.d/functions: No such file or directory
/etc/init.d/vboxweb-service: line 91: /etc/init.d/functions: No such file or directory
error: %post(VirtualBox-4.0-4.0.10_72479_rhel5-1.i386) scriptlet failed, exit status 1


This indicates that there are tools that the VirtualBox RPM relies on but does not list in it's spec file which means they are not guaranteed to be present.

Change History

comment:1 follow-up: ↓ 2 Changed 4 years ago by frank

Which distribution is that, are you really talking about RHEL5?

comment:2 in reply to: ↑ 1 Changed 4 years ago by dclark

Replying to frank:

Which distribution is that, are you really talking about RHEL5?

Yes we are using Red Hat Enterprise Linux 5.6

Linux 2.6.18-238.12.1.el5PAE SMP

Let me know if there is more information you need.

comment:3 Changed 4 years ago by frank

So the missing packages are module-init-tools and initscripts, correct? Actually both should be installed on a normal RHEL5 system, at least initscripts.

comment:4 Changed 4 years ago by dclark

The missing packages are whatever RPMs provide '/sbin/modprobe' and '/etc/init.d/functions'. I'm not in the office today so I can't do an 'rpm --what-provides /sbin/modprobe' or 'rpm --what-provides /etc/init.d/functions'

It's not that those packages are not installed, it's that the VirtualBox RPM does not say in it's spec file that it depends on the RPMs that provide these 2 files. When kickstart begins it's install it build a dependency tree of all the RPMs to be installed. We install almost 1000 RPMs and both of these files appear on the system when we boot it. It's just an order thing. I also don't know what really fails in the VirtualBox RPM's post because those tool aren't there. The modprobe command is probably the kickstart process trying to load VirtualBox modules inside the chroot environment during the install.

comment:5 Changed 4 years ago by frank

The 4.0.12 packages contains a dependency to initscripts, this should fix your problem.

comment:6 Changed 4 years ago by dclark

Great, I'll download it Monday and try it out and let you know what happens. I just downloaded 4.0.10 a couple of days ago so 4.0.12 must have just come out. Thanks.

comment:7 Changed 4 years ago by dclark

It looks like the VirtualBox RPM should depend on module-init-tools. Without that dependency /sbin/modprobe and /etc/lsmod tools are not available. You can see that VirtualBox installs at line 869 and module-init-tools installs at line 901

869 Installing VirtualBox-4.0-4.0.12_72916_rhel5-1.i386
 870 warning: VirtualBox-4.0-4.0.12_72916_rhel5-1: Header V4 DSA signature: NOKEY, key ID 98ab5139
 871 /etc/init.d/vboxdrv: line 36: /sbin/modprobe: No such file or directory
 872 /etc/init.d/vboxdrv: line 157: lsmod: command not found
 873 /etc/init.d/vboxdrv: line 157: lsmod: command not found
 874 Installing 1:quota-3.13-5.el5.i386
 875 Installing acpid-1.0.4-9.el5_4.2.i386
 876 Installing 2:irqbalance-0.55-15.el5.i386
 877 Installing dhcpv6-client-1.0.10-20.el5.i386
 878 Installing 1:microcode_ctl-1.17-1.52.el5.i386
 879 Installing ipsec-tools-0.6.5-14.el5_5.5.i386
 880 Installing rp-pppoe-3.5-32.1.i386
 881 Installing 1:rng-utils-2.0-4.el5.i386
 882 Installing 1:smartmontools-5.38-2.el5.i386
 883 Installing bluez-utils-3.7-2.2.i386
 884 Installing libglade2-devel-2.6.0-2.i386
 885 Installing libgnomecanvas-devel-2.14.0-4.1.i386
 886 Installing libXmu-devel-1.0.2-5.i386
 887 Installing mingw32-nsiswrapper-5-1.el5.noarch
 888 Installing libwnck-devel-2.16.0-4.fc6.i386
 889 Installing selinux-policy-targeted-2.4.6-300.el5_6.1.noarch
 890 Installing yum-security-1.1.16-13.el5_4.1.noarch
 891 Installing 1:yum-updatesd-0.9-2.el5.noarch
 892 Installing system-config-printer-
 893 Installing redhat-lsb-4.0-2.1.4.el5.i386
 894 Installing openmotif-devel-2.3.1-5.el5_5.1.i386
 895 Installing xbae-devel-4.60.4-12.i386
 896 Installing chkfontpath-1.10.1-1.1.i386
 897 Installing sane-backends-libs-1.0.18-5.el5.i386
 898 Installing pcsc-lite-1.4.4-4.el5_5.i386
 899 Installing 6:kdelibs-3.5.4-25.el5_4.1.i386
 900 Installing mkinitrd-
 901 Installing module-init-tools-3.3-0.pre3.1.60.el5_5.1.i386

Running the rpm command to determine what provides /bin/modprobe

rpm -q --whatprovides /sbin/modprobe 

comment:8 Changed 4 years ago by frank

But initscript depends on module-init-tools itself so I wonder why module-init-tools is not immediately installed after initscripts (which is before VirtualBox).

$ rpm -qR initscripts | grep module-init-tools
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use