=== CyberJacob|Away is now known as CyberJacob
=== CyberJacob is now known as CyberJacob|Away
=== CyberJacob|Away is now known as CyberJacob
=== CyberJacob is now known as CyberJacob|Away
=== CyberJacob|Away is now known as CyberJacob
=== CyberJacob is now known as CyberJacob|Away
[13:00] <freeflying> http://paste.ubuntu.com/5962495/ anyone had this issue before NodesNotAvailable: No matching node is available. but actually lots of machines listed as ready in maas
[13:33] <rbasak> freeflying: bug 1064291 maybe?
[13:33] <ubot5> bug 1064291 in juju "Default constraints make no sense on MAAS" [Undecided,New] https://launchpad.net/bugs/1064291
[13:33] <rbasak> (workaround available)
[13:43] <freeflying> rbasak: sounds abit different, this maas environment worked, but after I bootstrap with constraints, then ran into the error I mentioned avove
[13:43] <freeflying> above
[13:44] <rbasak> freeflying: if you're bootstrapping with contraints, then the error means that no node matched your specified constraints, surely?
[13:45] <freeflying> rbasak: I could bootstrap with constraint, which was maas-name, but not any other instance after bootstrap
[13:45] <freeflying> rbasak: its repeatable with destroy-envirment
[13:46] <rbasak> freeflying: I think a constraint on bootstrap does something you don't expect. All other nodes you attempt to start will have the same constraint applied, and of course you can only have one node work with that constraint. Could this be your problem?
[13:46] <rbasak> freeflying: if that's what it is, then I agree it's confusing, but juju developers disagreed. I think it's in a bug somewhere.
[13:48] <freeflying> rbasak: I understand, the issue is still there even I bootstrap without constraints
[13:48] <rbasak> freeflying: I'm not sure then, sorry. You can see what constraints juju asked MAAS for in the logs somewhere I think. Maybe the web server ones?
[13:52] <freeflying> rbasak: all the nodes enlisted to maas has same spec, 1024M ram, 1 vcpus, 2 nics, 2 block disk
[13:53] <freeflying> rbasak: and now I'm rebootstraping, node was allocated without problem
[13:53] <rbasak> freeflying: I still think the problem is at the juju end. MAAS just uses the contraints it has been given, and I've never seen it fail to work. The problem's always been that the juju end has specified constraints that MAAS cannot fulfil, even if that's not what the juju user intended.
[13:55] <freeflying> rbasak:  are you referring to python version juju or it still function in this way in go version?
[13:57] <rbasak> freeflying: I know about the python version. I don't know what the go version does.
[13:59] <freeflying> rbasak: thanks a lot, I'm thinking about filing a bug against :)
=== CyberJacob|Away is now known as CyberJacob
=== CyberJacob is now known as CyberJacob|Away
=== CyberJacob|Away is now known as CyberJacob
[19:15] <AskUbuntu> juju zookeeper installation stuck | http://askubuntu.com/q/330295
=== CyberJacob is now known as CyberJacob|Away