kexec-tools : errors while installing kexec tools package

[bugproxy]

== Comment: #0 - ABDUL HALEEM <email address hidden> - 2016-02-09 07:43:53 ==
--- Problem Description ---
root@powerkvm5:~# sudo apt-get install kexec
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package kexec
root@powerkvm5:~# sudo apt-get install kexec-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  kexec-tools
0 upgraded, 1 newly installed, 0 to remove and 18 not upgraded.
Need to get 0 B/69.2 kB of archives.
After this operation, 404 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package kexec-tools.
(Reading database ... 64579 files and directories currently installed.)
Preparing to unpack .../kexec-tools_1%3a2.0.10-1ubuntu1_ppc64el.deb ...
Unpacking kexec-tools (1:2.0.10-1ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (228-5ubuntu3) ...
Setting up kexec-tools (1:2.0.10-1ubuntu1) ...
Generating grub configuration file ...
Found linux image: /boot/vmlinux-4.5.0-rc3-autotest
Found initrd image: /boot/initrd.img-4.5.0-rc3-autotest
Found linux image: /boot/vmlinux-4.4.0-2-generic
Found initrd image: /boot/initrd.img-4.4.0-2-generic
[ 391.517954] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 391.519126] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 391.520791] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 391.522239] FAT-fs (sda1): bogus number of reserved sectors
[ 391.538972] FAT-fs (sda1): bogus number of reserved sectors
[ 391.545915] qnx4: no qnx4 filesystem (no root dir).
[ 391.546978] ufs: You didn't specify the type of your ufs filesystem
[ 391.546978]
[ 391.546978] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 391.546978]
[ 391.546978] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 391.547378] ufs: ufs_fill_super(): bad magic number
[ 391.580050] EXT4-fs (sdh1): VFS: Can't find ext4 filesystem
[ 391.580996] EXT4-fs (sdh1): VFS: Can't find ext4 filesystem
[ 391.582088] EXT4-fs (sdh1): VFS: Can't find ext4 filesystem
[ 391.583200] FAT-fs (sdh1): bogus number of reserved sectors
[ 391.593086] FAT-fs (sdh1): bogus number of reserved sectors
[ 391.599678] qnx4: no qnx4 filesystem (no root dir).
[ 391.600832] ufs: You didn't specify the type of your ufs filesystem
[ 391.600832]
[ 391.600832] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 391.600832]
[ 391.600832] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 391.601241] ufs: ufs_fill_super(): bad magic number
[ 391.753019] EXT4-fs (sdm1): VFS: Can't find ext4 filesystem
[ 391.754649] EXT4-fs (sdm1): VFS: Can't find ext4 filesystem
[ 391.756177] EXT4-fs (sdm1): VFS: Can't find ext4 filesystem
[ 391.757796] FAT-fs (sdm1): bogus number of reserved sectors
[ 391.768774] FAT-fs (sdm1): bogus number of reserved sectors
[ 391.775763] qnx4: no qnx4 filesystem (no root dir).
[ 391.776784] ufs: You didn't specify the type of your ufs filesystem
[ 391.776784]
[ 391.776784] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 391.776784]
[ 391.776784] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 391.777416] ufs: ufs_fill_super(): bad magic number
Found Ubuntu 14.04.3 LTS (14.04) on /dev/sdh2
Found Ubuntu 14.04.3 LTS (14.04) on /dev/sdm2
done
insserv: warning: script 'S99autotest' missing LSB tags and overrides
insserv: warning: script 'autotest' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and procps if started
insserv: loop involving service procps at depth 2
insserv: loop involving service udev at depth 1
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv: loop involving service irqbalance at depth 1
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop at service autotest if started
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service autotest and hwclock if started
insserv: loop involving service hwclock at depth 1
insserv: loop involving service networking at depth 4
insserv: There is a loop between service plymouth and urandom if started
insserv: loop involving service urandom at depth 4
insserv: loop involving service mountdevsubfs at depth 2
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service autotest and dns-clean if started
insserv: loop involving service dns-clean at depth 1
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package kexec-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 kexec-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

root@powerkvm5:~# uname -a
Linux powerkvm5 4.4.0-2-generic #16-Ubuntu SMP Thu Jan 28 15:42:17 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

---Machine---
platform : PowerNV

# dpkg -l | grep kexec
iF kexec-tools 1:2.0.10-1ubuntu1 ppc64el tools to support fast kexec reboots

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1544926/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Steve Langasek (vorlon)]

The error in your log is:

insserv: warning: script 'S99autotest' missing LSB tags and overrides
insserv: warning: script 'autotest' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and procps if started
insserv: loop involving service procps at depth 2
insserv: loop involving service udev at depth 1
insserv: Starting autotest depends on plymouth and therefore on system facility `$all' which can not be true!

This is not a bug in Ubuntu. You have an init script on your system, /etc/init.d/autotest, which is not from Ubuntu and which is not an LSB-compliant init script. This is not supported, and will cause insserv to fail to calculate boot order as shown here.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-02-19 01:15 EDT-------
(In reply to comment #6)
> The error in your log is:
>
> insserv: warning: script 'S99autotest' missing LSB tags and overrides
> insserv: warning: script 'autotest' missing LSB tags and overrides
> insserv: There is a loop at service plymouth if started
> insserv: There is a loop between service plymouth and procps if started
> insserv: loop involving service procps at depth 2
> insserv: loop involving service udev at depth 1
> insserv: Starting autotest depends on plymouth and therefore on system
> facility `$all' which can not be true!
>
> This is not a bug in Ubuntu. You have an init script on your system,
> /etc/init.d/autotest, which is not from Ubuntu and which is not an
> LSB-compliant init script. This is not supported, and will cause insserv to
> fail to calculate boot order as shown here.

alright, Yes I had run a kernel build test case from autotest earlier which created /etc/init.d/autotest.

kexec-tools insall worked fine, when /etc/init.d/autotest is removed.

This is not a bug