/srv/irclogs.ubuntu.com/2015/04/27/#maas.txt

=== 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
mupBug #1448901 was opened: MAAS deployment fails on P8 PowerKVM (SVA GmbH) <MAAS:New> <https://launchpad.net/bugs/1448901>08:09
=== 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
mupBug #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:01
mupBug #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:07
mupBug #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:16
nodtknHowdy.  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:33
roaksoaxnodtkn: yes13:37
mupBug #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
nodtknroaksoax: Interesting that is not what I am seeing.13:41
roaksoaxnodtkn: then installation may be failing13:44
roaksoaxnodtkn: or PXE booting might be failing?13:44
nodtknI see the node PXE booting under MAAS direction13:45
=== jfarschman is now known as MilesDenver
roaksoaxnodtkn: right, so when the node is marked deployed, you should see an installation log13:46
nodtknroaksoax: I see in pserv.log the requests for PXE boot images.13:46
roaksoaxnodtkn: what does the node event log say?13:47
nodtknroaksoax: 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 depoyed13:50
nodtknroaksoax: then I released the node 6) status from releasing to ready 7) node powered off13:51
nodtknroaksoax: then I allocated it with a different ID and it powere the node on with out installing13:52
roaksoaxnodtkn: ah, if you power the node *without* re-installing, then yes, MAAS is not going to re-install it13:58
roaksoaxnodtkn: you need to deploy the node again13:58
nodtknroaksoax: 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:07
mupBug #1449043 was opened: UI should display a notification until SSH key is uploaded <MAAS:New> <https://launchpad.net/bugs/1449043>14:11
roaksoaxnodtkn: 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"15:16
=== imthewherd`away is now known as imthewherd
francokaerntnahello, can anybody of you tell me, how the hostnames for the nodes are generated?15:58
=== essembe is now known as sbeattie
nodtknroaksoax: 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?16:56
mupBug #1449173 was opened: maas does not reinstall node <maas (Ubuntu):New> <https://launchpad.net/bugs/1449173>17:41
mupBug #1449206 was opened: maas installation fails because of missing AppCache module in django <MAAS:New> <https://launchpad.net/bugs/1449206>18:35

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!