[00:21] Bug #1722962 opened: Connection broken: IncompleteRead on rackd [09:18] Hi all [09:19] Can I have a Dell related question? [09:22] When I am trying to comission manually defined nodes, MaaS duplicates them and defines the duplicates with different IPMI credentials [09:24] It seems that it creates maas IPMI user for some reasons [12:31] TheGOro: maas autodetects IPMI and auto-configures it for usage, yes [17:11] apologies if this is a know issue: bootstrapping Juju controller Attempting to connect :22 [17:11] what did i miss? [17:49] spaniard: did the node with come up right? Can you ping the node via that from maas server? [17:51] yes the node comes up, displays the correct info and is pingable [17:54] spaniard: does it show deployed successfully on maas? if so, how long have juju bootstrap been stuck at Attempting to connect :22/ [17:54] ? [17:56] catbus: maybe an hour stuck on "Attempting to ssh" [17:57] spaniard: can you ssh to the machine from MAAS? [17:58] spaniard: I'd kill current juju bootstrap, make sure the machine is released on MAAS, then juju bootstrap again with --debug flag to get more info. [18:01] catbus: I can not ssh, did i miss adding a key somewhere? [18:02] spaniard: if you can't ssh ubuntu@ from MAAS, you should check if an ssh key is imported in MAAS, click on the admin account on the top right, then it will bring you to a page where you can import ssh keys. [18:03] ah user ubuntu ..yes i can ssh to the node [18:04] spaniard: I'd kill current juju bootstrap, make sure the bootstrap machine is released on MAAS, then juju bootstrap again with --debug flag to get more info. [18:12] catbus: thank you! i'll start again with the --debug, approximately how long should it take to pass this step Attempting to connect :22/ [18:14] spaniard: However long it takes the machine to finish OS install and reachable via that IP. When you see it shows deployed successfully on maas, juju should be able to contact the node. [19:25] Bug #1723232 opened: [2.3, UI] Move event log dates to the left [20:43] Bug #1707999 changed: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server [20:43]