[10:49] <melmoth> with maas 1.2 i deploy a nova-compute charm but no machine is being allocated to root once it s done.
[10:49] <melmoth> i have the same behaviour if i use a constraint (so i can pick up the node i want), or none (just for testing)
[10:49] <melmoth> i was able to deploy other charm on at least one box
[10:49] <melmoth> not sure where to look/how to investigate this
[11:57] <melmoth> food
=== frankban_ is now known as frankban
[13:12] <melmoth> anyone knows how to investigate /where to look when machine in ready state are not allocated when i deploy a charm ?
[13:13] <melmoth> it used to work yesterday, i deployed several charm on one box (juju+maas-name constraint, then jitsu deploy-to)
[13:13] <melmoth> then, today i cannot deploy anything, even without constraint at all. all my ready nodes stay in ready state
[13:34] <roaksoax> melmoth: check the constraints juju get-constraints and check /var/log/maas/maas.log
[13:35] <melmoth> roaksoax, constraint looks "normal" arch: amd64, cpu: 1.0, maas-name: null, maas-tags: null, mem: 512.0, provider-type: maas,  ubuntu-series: null}
[13:35] <melmoth> now, for the maas log, there s no new line appened to it when i reproduce the porblem. But.
[13:36] <melmoth> but, there is this; wich happen today, so may be it s related:
[13:37] <melmoth> hmm, actually it dates from yesterday http://pastebin.ubuntu.com/5652291/
=== kentb-out is now known as kentb
=== jlondon_ is now known as jlondon