MAAS from cloud-tools-next on precise fails because python-amqp too new
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@
==> maas-cluster-
Traceback (most recent call last):
File "/usr/bin/celeryd", line 5, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/
parse_
File "/usr/lib/
raise DistributionNot
pkg_resources.
$ dpkg -l | grep amqp
ii python-amqp 1.3.3-1ubuntu1~
Downgrading to 1.0.12-
Regards,
Haw
Changed in maas: | |
status: | New → Invalid |