maas-devel team mailing list archive

[Dafang Zhang <me2050@xxxxxxxxx>]

In short, yes, the juju packages from quantal seemed fixed it.  

From what I experienced, I believe the key is to have 12.10 quantal image loaded 
on the zookeeper node.  This is done by changing the /etc/maas/import_pxe_files, 
executing the maas-import-pxe-files command, and using the maas webui to edit 
the zookeeper node to use 12.10 image.  This automatically lifted the juju packages 
up to version 0.6-1ubuntu1 on the zookeeper node.  In the old non-working setup, 
the zookeeper node was loaded with the precise image, and the juju version was 
0.5+bzr531-0ub.  

Additional test - I tried both quantal and precise images as the service nodes 
(for example, mysql is on quantal, tomcat7 on precise), they both worked, despite 
of different version of the juju packages on each node. 

A side note - the maas packages were updated from 0.1+bzr1264+ to 0.1+bzr1269+ 
by pulling them from the quantal-proposed repository.

Best Wishes,



----- Original Message -----
From: Julian Edwards <julian.edwards@xxxxxxxxxxxxx>
To: Dafang Zhang <me2050@xxxxxxxxx>
Cc: Maas Devel <maas-devel@xxxxxxxxxxxxxxxxxxx>
Sent: Thursday, November 1, 2012 3:17 AM
Subject: Re: [Maas-devel] Ready State not Changed to Allocated after Juju Deploy

On Wednesday 31 Oct 2012 22:35:22 Dafang Zhang wrote:
> Thanks to Julian for pointing out that this issue could be due to the bug
> (linked in his reply below).  I checked the provision-agent.log on the
> zookeeper node and found that the exceptions matched the bug description.
>  So I followed the workaround and it did work.  Sounds like the latest juju
> packages fixed the original issue I had.  Here're the steps that worked for
> me.  Hope this help those who would have similar issues.  

Good news, thank you!

Could you summarise the actual changes you made from the old non-working 
setup?  Was it literally just a case of upgrading the juju packages?  If so, 
what version of juju packaging did you have?

Cheers.