nova-objectstore start errors after install

Bug #660428 reported by Mark Gallop
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nova (Ubuntu)
Fix Released
Medium
Soren Hansen

Bug Description

I received the following error when installing nova on a fresh Ubuntu 10.10 server:

Setting up nova-objectstore (0.9.1~bzr331-0ubuntu2) ...
 * Starting nova objectstore nova-objectstore
Traceback (most recent call last):
  File "/usr/bin/nova-objectstore", line 38, in <module>
    from nova.objectstore import handler
  File "/usr/lib/pymodules/python2.6/nova/objectstore/handler.py", line 58, in <module>
    from nova.api.ec2 import context
  File "/usr/lib/pymodules/python2.6/nova/api/__init__.py", line 30, in <module>
    from nova.api import rackspace
  File "/usr/lib/pymodules/python2.6/nova/api/rackspace/__init__.py", line 35, in <module>
    from nova.api.rackspace import backup_schedules
  File "/usr/lib/pymodules/python2.6/nova/api/rackspace/backup_schedules.py", line 24, in <module>
    import nova.image.service
ImportError: No module named image.service
   ...fail!
invoke-rc.d: initscript nova-objectstore, action "start" failed.

I ran the following command to get the packages:

sudo apt-get install nova-api nova-objectstore nova-compute \
                nova-scheduler nova-network euca2ools unzip

Revision history for this message
Soren Hansen (soren) wrote :

Oh, dear. I see what's going on here. nova-objectstore is missing a dependency on python-nova. :(

Changed in nova (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Soren Hansen (soren)
Revision history for this message
Soren Hansen (soren) wrote :

Ah, sorry, no it's not.

Revision history for this message
Soren Hansen (soren) wrote : Re: [Bug 660428] [NEW] nova-objectstore start errors after install

On 14-10-2010 13:20, Launchpad Bug Tracker wrote:
> Setting up nova-objectstore (0.9.1~bzr331-0ubuntu2) ...
> * Starting nova objectstore nova-objectstore
> Traceback (most recent call last):
> File "/usr/bin/nova-objectstore", line 38, in <module>
> from nova.objectstore import handler
> File "/usr/lib/pymodules/python2.6/nova/objectstore/handler.py", line 58, in <module>
> from nova.api.ec2 import context
> File "/usr/lib/pymodules/python2.6/nova/api/__init__.py", line 30, in <module>
> from nova.api import rackspace
> File "/usr/lib/pymodules/python2.6/nova/api/rackspace/__init__.py", line 35, in <module>
> from nova.api.rackspace import backup_schedules
> File "/usr/lib/pymodules/python2.6/nova/api/rackspace/backup_schedules.py", line 24, in <module>
> import nova.image.service
> ImportError: No module named image.service
> ...fail!
> invoke-rc.d: initscript nova-objectstore, action "start" failed.
>
> I ran the following command to get the packages:
>
> sudo apt-get install nova-api nova-objectstore nova-compute \
> nova-scheduler nova-network euca2ools unzip
>

This happens because python-support hasn't run yet when we attempt to start the daemon.

--
Soren Hansen
Ubuntu Developer http://www.ubuntu.com/
OpenStack Developer http://www.openstack.org/

Revision history for this message
Soren Hansen (soren) wrote :

Fix committed:

    http://bazaar.launchpad.net/~nova-core/nova/ubuntu-packaging/revision/280

It'll be included in an SRU soon, hopefully.

Test case:
On a system without python-nova, run "apt-get install nova-objectstore". It will fail to start the daemon, citing missing modules. With this fix applied, it will start the daemon succesfully.

Revision history for this message
Stephen Milton (milton-isomedia) wrote :

I think this dependency problem also causes the openssl config in /var/lib/nova/CA to fail. It can be avoided on a new install by running two install commands instead of one:

sudo apt-get install python-nova
sudo apt-get install nova-api nova-objectstore nova-compute nova-scheduler nova-network euca2ools unzip

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nova - 2011.1~bzr412-0ubuntu1

---------------
nova (2011.1~bzr412-0ubuntu1) natty; urgency=low

  [ Soren Hansen ]
  * New upstream snapshot.
  * Added the new tarballs page to debian/watch.
  * Clean out patch-branches (everything is upstream now).
  * Remove redis-server as a build-depends and don't start it for tests
    anymore.
  * Add missing dependency on python-webob.
  * Force a python-support run (so avoid deferring it until dpkg
    triggers run). (LP: #660428)
  * Remove build and runtime dependencies on python-tornado. It's not
    needed anymore.
  * logdir.patch: Add a --logdir option to workers so that they can all
    use the same flagfile. (lp:~soren/nova/logdir-flag)
  * Consolidate all the flagfiles into one.
  * flagfile_location.patch: Patch from upstream to ensure all workers
    have a consistent way of finding their flagfile.
    (lp:~soren/nova/unify-default-flagfile-location)
  * nova-manage_flagfile_location.patch: Make sure nova-manage uses
    /etc/nova/nova.conf by default.
  * Add build and runtime dependency on openssl. It used to be pulled in
    by python-tornado, but is actually used directly by nova.

  [ Chuck Short ]
  * debian/control:
   - Add dependency to python-rrdtool so that nova-instancemonitor
     doesnt complain about missing python modules when starting.
  * debian/nova-common.install: Add missing templates.
  * debian/nova-*.conf: Update flagfiles to handle upstream changes.
  * Dropped start-redis since we dont do redis anymore.
 -- Soren Hansen <email address hidden> Tue, 23 Nov 2010 11:17:09 +0100

Changed in nova (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Joseph Heck (heckj) wrote :

This bug surfaced again while testing the diablo-1 milestone against Ubuntu maverick.

running /etc/init.d/nova-objectstore start right after the install started the service without issue.

Revision history for this message
Soren Hansen (soren) wrote : Re: [Bug 660428] Re: nova-objectstore start errors after install

Can you post the exact error message, please? Thanks!

Revision history for this message
Thierry Carrez (ttx) wrote :

@Joseph Heck: please open a separate bug and post the error message there. The fix for this bug is still in current nova, so it's probably the same symptoms but a different bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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