Failure to install lio-utils on fresh cloud-image

Bug #1479424 reported by Dave Chiluk
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lio-utils (Ubuntu)
Fix Released
Undecided
Unassigned
Precise
Fix Released
Undecided
Unassigned
targetcli (Ubuntu)
Invalid
Undecided
Unassigned
Precise
Invalid
Undecided
Unassigned

Bug Description

On a fresh cloud-image I attempt to install lio-utils and it encounters errors. See below

ubuntu@target2-precise:~$ sudo apt-get install lio-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  lio-utils
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 102 kB of archives.
After this operation, 589 kB of additional disk space will be used.
Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu/ precise/universe lio-utils amd64 3.1+git0.91b96103-2 [102 kB]
Fetched 102 kB in 0s (4,689 kB/s)
Selecting previously unselected package lio-utils.
(Reading database ... 47562 files and directories currently installed.)
Unpacking lio-utils (from .../lio-utils_3.1+git0.91b96103-2_amd64.deb) ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.2.0-88-virtual
Processing triggers for ureadahead ...
Setting up lio-utils (3.1+git0.91b96103-2) ...
Loading target_core_mod/ConfigFS core: [FAILED]: 1
invoke-rc.d: initscript target, action "start" failed.
dpkg: error processing lio-utils (--configure):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports is reached already
                                                              Errors were encountered while processing:
 lio-utils
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lio-utils 3.1+git0.91b96103-2
ProcVersionSignature: User Name 3.2.0-88.126-virtual 3.2.69
Uname: Linux 3.2.0-88-virtual x86_64
ApportVersion: 2.0.1-0ubuntu17.9
Architecture: amd64
Date: Wed Jul 29 15:58:31 2015
Ec2AMI: ami-00000ecf
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: cpu2-ram8-disk10-ephemeral20
Ec2Kernel: aki-00000548
Ec2Ramdisk: ari-00000548
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lio-utils
UpgradeStatus: No upgrade log present (probably fresh install)

Tags: sts
Revision history for this message
Dave Chiluk (chiluk) wrote :
Revision history for this message
Dave Chiluk (chiluk) wrote :

Adding targetcli also as it depends on lio-utils. It is my recommendation that both of these be removed from universe as it appears impossible to install either.

Revision history for this message
Adam Conrad (adconrad) wrote :

13:58 < infinity> chiluk: When packages are buggy, the usual thing to do is to fix them.
13:59 < infinity> chiluk: And given that your test case is precise, removal isn't an option anyway.

Revision history for this message
Adam Conrad (adconrad) wrote :

lio-utils was removed from wily two months ago.

Changed in targetcli (Ubuntu):
status: New → Invalid
Changed in lio-utils (Ubuntu):
status: New → Fix Released
Changed in lio-utils (Ubuntu Precise):
status: New → Fix Released
Changed in targetcli (Ubuntu Precise):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.