[07:13] <jojden> hi roaksoax
[10:00] <BlackDex> Hello there. I have maas running and using a dhcp-relay with different subnets on the same fabric. This seems to give some trouble because it doesn't responed with the correct subnet. It just picks a subnet (i think the first subnet it sees) and uses that to allocat an IP Address. It should just respond with an IP on the same subnet the relay is on. Is there a special setting i need to do. Add it to a seperate space? Or a sub-fabric or something?
[14:07] <tarantul> anyone can help with 'failed commissioning' node?
[14:08] <tarantul> I see many Calling 'http://169.254.168.254/2009-04-04/meta-data/instance-id in boot screen. May be it's a cause?
[15:01] <D4RKS1D3> hi
[15:02] <D4RKS1D3> I have one question, it is posible to change automatically the state new to ready?
[15:34] <kiko> D4RKS1D3, by automatically do you mean "automatically accept and commission every node which has enlisted"?
[15:34] <kiko> D4RKS1D3, the easiest way to do that is via the API
[15:34] <kiko> BlackDex, hmmm
[15:34] <kiko> BlackDex, not sure what you are doing
[15:34] <kiko> tarantul, could it be because of anoher failure? you'll need to look at the logs to figure it out
[15:35] <D4RKS1D3> Via api is possible
[15:36] <D4RKS1D3> but I do not know if with one command similiar to "accept-all" it is possible
[15:36] <D4RKS1D3> thank for your contribution kiko
[15:58] <tarantul> kiko: what log I need check?
[15:58] <kiko> D4RKS1D3, no, you'll need to accept one by one -- in part to avoid the race condition of a rogue node enlisting between you looking and accepting all
[15:58] <kiko> tarantul, the install log -- turn on the flag when you commission that leaves the machine running to check it
[16:02] <tarantul> kiko: Node is runing, but I can't login. Does MAAS set default user/pass?
[16:36] <tarantul> I soled my problem, but have another now. Node boots, do some stuff and shutdown. After reboot it's boot into old linux, not in a new 16.4 setup.
[16:49] <kiko> tarantul, you now need to deploy -- commissioning does not write to disk
[16:52] <kiko> tarantul, what was the problem with commissioning, incidentally?
[19:24] <mup> Bug #1587163 opened: Error: No boot sources provide Ubuntu images <MAAS:New> <https://launchpad.net/bugs/1587163>
[22:19] <batz77> hi there.. im having trouble with deploying a vivid node. pollinate/seeding appears to fail in the same way outlined in https://bugs.launchpad.net/maas/+bug/1424549 . there's a lot of replies in that bug and im confused as to what the actual fix is, if there is one
[22:20] <batz77> one side of the threads says "change your image sources to get the newer baked in cert" (I think) and the other says that doesnt matter its a red herring