[Bug 1316404] [NEW] MAAS from cloud-tools-next on precise fails because python-amqp too new

[Haw Loeung]

Public bug reported:

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 at 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

** Affects: maas
     Importance: Undecided
         Status: New

** Affects: maas (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: maas (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1316404

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1316404/+subscriptions