package eucalyptus-nc 1.6.2-0ubuntu30.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Bug #615943 reported by Tony Flint
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Invalid
Low
Unassigned

Bug Description

OS:
Description: Ubuntu 10.04.1 LTS
Release: 10.04

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: eucalyptus-nc 1.6.2-0ubuntu30.3
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Aug 4 11:19:48 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
SourcePackage: eucalyptus
Title: package eucalyptus-nc 1.6.2-0ubuntu30.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Revision history for this message
Tony Flint (koyote2600) wrote :
Revision history for this message
C de-Avillez (hggdh2) wrote :

From the DpkgTerminalLog.gz:

Selecting previously deselected package eucalyptus-gl.

Unpacking eucalyptus-gl (from .../eucalyptus-gl_1.6.2-0ubuntu30.3_amd64.deb) ...

Selecting previously deselected package eucalyptus-nc.

Unpacking eucalyptus-nc (from .../eucalyptus-nc_1.6.2-0ubuntu30.3_amd64.deb) ...

Selecting previously deselected package vlan.

Unpacking vlan (from .../vlan_1.9-3ubuntu3_amd64.deb) ...

Processing triggers for man-db ...

Processing triggers for ufw ...

Processing triggers for ureadahead ...

Setting up libaprutil1-dbd-sqlite3 (1.3.9+dfsg-3build1) ...

Setting up libaprutil1-ldap (1.3.9+dfsg-3build1) ...

Setting up apache2.2-bin (2.2.14-5ubuntu8) ...

Setting up apache2-utils (2.2.14-5ubuntu8) ...

Setting up apache2.2-common (2.2.14-5ubuntu8) ...

Setting up apache2-mpm-worker (2.2.14-5ubuntu8) ...

 * Starting web server apache2  apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName

[ OK ]

Setting up libapache2-mod-axis2c (1.6.0-0ubuntu8) ...

Setting up libvirt-bin (0.7.5-5ubuntu27) ...

libvirt-bin start/running, process 19025

Setting up powernap (1.9-0ubuntu1) ...

Setting up eucalyptus-gl (1.6.2-0ubuntu30.3) ...

Setting up vlan (1.9-3ubuntu3) ...

Processing triggers for python-central ...

Setting up eucalyptus-nc (1.6.2-0ubuntu30.3) ...

/var/lib/dpkg/info/eucalyptus-nc.postinst: 47: cannot create /etc/eucalyptus/eucalyptus-nc.conf: Directory nonexistent

dpkg: error processing eucalyptus-nc (--configure):

 subprocess installed post-installation script returned error exit status 2

Eucalyptus-common should also be installed. How did you select the eucalyptus packages?

Changed in eucalyptus (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
C de-Avillez (hggdh2) wrote :

Also, please run on this machine:

dpkg -l euca\*

and post the result here.

Thank you.

Revision history for this message
Tony Flint (koyote2600) wrote :

Hi,

This upgrade was performed automatically via update manager. I had previously installed eucalyptus via apt-get on the command line. I'm not sure how I ended up with eucalyptus-nc being installed without eucalyptus-common being present.

Here's the output of dpkg:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=================================-=================================-==================================================================================
un euca2ools <none> (no description available)
un eucalyptus-cc <none> (no description available)
un eucalyptus-cloud <none> (no description available)
ii eucalyptus-common 1.6.2-0ubuntu30.3 Elastic Utility Computing Architecture - Common files
ii eucalyptus-gl 1.6.2-0ubuntu30.3 Elastic Utility Computing Architecture - Logging service
rc eucalyptus-java-common 1.6.2-0ubuntu30.3 Elastic Utility Computing Architecture - Common Java package
un eucalyptus-javadeps <none> (no description available)
ii eucalyptus-nc 1.6.2-0ubuntu30.3 Elastic Utility Computing Architecture - Node controller
un eucalyptus-sc <none> (no description available)
un eucalyptus-walrus <none> (no description available)

Revision history for this message
C de-Avillez (hggdh2) wrote :

Thank you for the quick response. Eucalyptus-common *is* installed, at the correct version... I wonder if you previously installed eucalyptus, then partially uninstalled.

This might be the reason for the error:

/var/lib/dpkg/info/eucalyptus-nc.postinst: 47: cannot create /etc/eucalyptus/eucalyptus-nc.conf: Directory nonexistent

Meaning '/etc/eucalyptus' does not exist -- like it was forcefully removed ('rm -rf /etc/eucalyptus'-type of action).

Can you please reinstall -common:

sudo apt-get --reinstall install eucalyptus-common

Revision history for this message
Tony Flint (koyote2600) wrote :

It appears to have installed correctly, though with a strange 'unknown parameter' message when stopping/starting the service:

Preparing to replace eucalyptus-common 1.6.2-0ubuntu30.3 (using .../eucalyptus-common_1.6.2-0ubuntu30.3_amd64.deb) ...
eucalyptus stop/waiting
stop: Unknown parameter: IFACE
Unpacking replacement eucalyptus-common ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up eucalyptus-common (1.6.2-0ubuntu30.3) ...
eucalyptus start/running, process 2477
start: Unknown parameter: IFACE
start: Job is already running: eucalyptus

I now have an /etc/eucalyptus directory with the .conf files.

Revision history for this message
C de-Avillez (hggdh2) wrote :

You can disregard the "Unknown parameter: IFACE", this is a known issue, and brings no problems. You should be good to go now. Please check, and let me know.

Revision history for this message
Dave Walker (davewalker) wrote :

I'm marking this Invalid, as others have not been able to reproduce this issue. It sounds like might have been an oddity during initial installation. This others are able to reproduce this, please update the bug accordingly, and we'll re-open it.

Thanks!

Changed in eucalyptus (Ubuntu):
status: Incomplete → 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.