=== ming is now known as Guest53326
=== wolsen_ is now known as wolsen
=== zz_CyberJacob is now known as CyberJacob
=== CyberJacob is now known as Guest44438
[08:09] <mup> Bug #1448901 was opened: MAAS deployment fails on P8 PowerKVM (SVA GmbH) <MAAS:New> <https://launchpad.net/bugs/1448901>
=== rawang is now known as Guest70583
=== bladernr_ is now known as bladernr-malta
=== rawang is now known as Guest20018
=== ahasenac` is now known as ahasenack
=== rawang is now known as Guest8315
=== rawang is now known as Guest46821
[13:01] <mup> Bug #1449011 was opened: 1.8b3: maas root node  start distro_series=precise on a non-allocated node returns wrong error message <oil> <MAAS:New> <https://launchpad.net/bugs/1449011>
[13:07] <mup> Bug #1449011 changed: 1.8b3: maas root node  start distro_series=precise on a non-allocated node returns wrong error message <oil> <MAAS:New> <https://launchpad.net/bugs/1449011>
[13:16] <mup> Bug #1449011 was opened: 1.8b3: maas root node  start distro_series=precise on a non-allocated node returns wrong error message <oil> <MAAS:New> <https://launchpad.net/bugs/1449011>
[13:33] <nodtkn> Howdy.  If disk erasing is disabled, can I assume maas will reinstall the node after it is released and (acquired and started) by someone else?
[13:37] <roaksoax> nodtkn: yes
[13:41] <mup> Bug #1449033 was opened: 1.8b4: Can not access device details by clicking on entry in device list <oil> <MAAS:New> <https://launchpad.net/bugs/1449033>
[13:41] <nodtkn> roaksoax: Interesting that is not what I am seeing.
[13:44] <roaksoax> nodtkn: then installation may be failing
[13:44] <roaksoax> nodtkn: or PXE booting might be failing?
[13:45] <nodtkn> I see the node PXE booting under MAAS direction
=== jfarschman is now known as MilesDenver
[13:46] <roaksoax> nodtkn: right, so when the node is marked deployed, you should see an installation log
[13:46] <nodtkn> roaksoax: I see in pserv.log the requests for PXE boot images.
[13:47] <roaksoax> nodtkn: what does the node event log say?
[13:50] <nodtkn> roaksoax: 1) status from ready to allocated userA 2) status from allocated to deploying 3) powering node on 4) node powered on 5) status from deploying to depoyed
[13:51] <nodtkn> roaksoax: then I released the node 6) status from releasing to ready 7) node powered off
[13:52] <nodtkn> roaksoax: then I allocated it with a different ID and it powere the node on with out installing
[13:58] <roaksoax> nodtkn: ah, if you power the node *without* re-installing, then yes, MAAS is not going to re-install it
[13:58] <roaksoax> nodtkn: you need to deploy the node again
[14:07] <nodtkn> roaksoax: I do not understand.  If the node is in the ready state and not allocated to anyone. What is supposed to happen when I select the node and choose start selected node from the bulk actions?  Is that different than what should happen when I click on the node and select "Acquire and start node"
[14:11] <mup> Bug #1449043 was opened: UI should display a notification until SSH key is uploaded <MAAS:New> <https://launchpad.net/bugs/1449043>
[15:16] <roaksoax> nodtkn: the node is allocated (owned) and you power it on (not deploy it), then you are basically telling it "just power on the node, don't re-install it"
=== imthewherd`away is now known as imthewherd
[15:58] <francokaerntna> hello, can anybody of you tell me, how the hostnames for the nodes are generated?
=== essembe is now known as sbeattie
[16:56] <nodtkn> roaksoax: After releasing the node from one user ID and I selected the node under another user ID and pressed the "Acquire and Start button" is that not the correct thing to do?
[17:41] <mup> Bug #1449173 was opened: maas does not reinstall node <maas (Ubuntu):New> <https://launchpad.net/bugs/1449173>
[18:35] <mup> Bug #1449206 was opened: maas installation fails because of missing AppCache module in django <MAAS:New> <https://launchpad.net/bugs/1449206>