MAAS from cloud-tools-next on precise fails because python-amqp too new

Bug #1316404 reported by Haw Loeung
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned
Ubuntu Cloud Archive
New
Undecided
Unassigned
maas (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi,

We're testing MAAS 1.5 on precise using the cloud-tools-next pocket in the cloud archives. It seems that python-amqp seems too new and MAAS celery services fail because of this:

$ sudo service maas-cluster-celery start
maas-cluster-celery start/running, process 15005
hloeung@mabolo:/var/log/upstart$
==> maas-cluster-celery.log <==
Traceback (most recent call last):
  File "/usr/bin/celeryd", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2711, in <module>
    parse_requirements(__requires__), Environment()
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 584, in resolve
    raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: amqp>=1.0.12,<1.1.0

$ dpkg -l | grep amqp
ii python-amqp 1.3.3-1ubuntu1~ctools0 Low-level AMQP client

Downgrading to 1.0.12-0ubuntu1~cloud0 fixes this.

Regards,

Haw

Changed in maas:
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.