mupBug #1726202 opened: maas rackd tftp bootstrap.py: 'Nonetype' object has no attribute 'stopListening' <cpe-onsite> <MAAS:New> <https://launchpad.net/bugs/1726202>02:33
sentinel__so i am new to maas and am trying to setup a home labe for testing it would someone be able to help me get this working03:12
mupBug #1708918 changed: maas node failed commisioning , failed to connect node via ssh <MAAS:Expired> <https://launchpad.net/bugs/1708918>04:18
=== frankban|afk is now known as frankban
angelinuxhello do you know how to setup wake-on-lan power type on maas 2.2 ?09:59
angelinuxhttps://stgraber.org/2017/04/02/using-wake-on-lan-with-maas-2-x/ this is not working anymore10:01
=== cnfer is now known as cnf
mupBug #1726474 opened: psycopg2.IntegrityError: update or delete on table "maasserver_node" violates foreign key constraint "maasserver_event_node_id_xxx_fk_maasserver_node_id" on table "maasserver_event" DETAIL:  Key (id)=(xx) is still referenced from table "maasserver_event". <cdo-qa>16:40
mup<cdo-qa-blocker> <foundations-engine> <MAAS:Triaged> <https://launchpad.net/bugs/1726474>16:40
=== frankban is now known as frankban|afk
mupBug #1726534 opened: [2.3, HWTv2] Fio does not always gather metrics <MAAS:Triaged> <https://launchpad.net/bugs/1726534>19:13
bdxryebot: juju reload-spaces20:00
lamontroaksoax: http://paste.ubuntu.com/25803994/ <-- how long should 2.3.0~beta2 take to enlist a new vm?  it would seem that it's hating my setup again20:41
* lamont will turn on more debugging later, but it may be quite later20:42
roaksoaxlamont: should be no different than 2.2 or older... check that /etc/maas/rackd.conf is pointing to an IP and not localhost, which could be messing communication with the metadata server20:43
roaksoaxlamont: or actuall, also check /etc/maas/regiond.conf has the correct maas_url too20:44
edmzI am trying MAAS with virtualbox. My MAAS server has 2 ip address  (one for internet, one for dhcp). The node is booting fine with DHCP/PXE but then cloud-init seems to be trying to get an image/file using the other ip (the public one, which it has no access to).20:44
edmzIs there a way to specify which ip the booting node must use for accessing MAAS?20:44
lamontmaas_url: http://localhost:5240/MAAS20:45
* lamont updates20:45
roaksoaxedmz: same as for lamont, make sure /etc/maas/rackd.conf doesn't point to localhost and points to an IP the machines can access to20:45
edmzroaksoax : thank you20:47
lamontroaksoax: when the maas_url in regiond.conf was a hostname, everything hated life.20:50
lamontroaksoax: which was left over from having ipv4 and 6 active on different vlans on the same rack20:51
lamontI'll poke at it some more at some point20:52
edmzroaksoax: it worked.20:54
roaksoaxlamont: probably dns resolution ?20:54
lamontI really should purge/reinstall maas on this cluster, since it's the left over from whatever the last hacking I was doing was.  with the IP there, the commissioning worked.20:54
roaksoaxlamont: but yes there's still some leftovers there20:54
lamontroaksoax: yeah, possibly that20:54
roaksoaxedmz: cool!20:54
edmzis there a place where I can read about the support/limits of using servers that dont have IPMI/BMC?20:55
roaksoaxedmz: supported power types are listed here: https://docs.ubuntu.com/maas/devel/en/nodes-power-types20:56
edmzroaksoax : currently I am testing with virtualbox. My real servers do have BMC20:57
roaksoaxedmz: you can use "manual" power type20:59
edmzThat is what I currently have. After the boot process the booting node just closes suddenly. I am wondering if it's because of lacking bmc/ipmi.21:00
edmzand I get a "failed comissioning" status.21:01
roaksoaxedmz: uhmm are they pxe booting and then something happens, and then it changes to failed commissioning ?21:02
edmzI only see 1 node in the nodes page. It always has "failed commisioning" status.21:04
edmzIf I boot that node, while the boot process is going on nothing changes on the nodes page.21:04
edmzThe boot processs continues past the part where it is downloading packages from ubuntu servers21:05
edmzthen the virtualbox window suddenly closes.21:05
edmzI managed to save a video of the output with Virtualbox.21:05
edmzI see, it is actually running shutdown.21:06
edmzthe only odd thing I see is "ci-info: no authorized ssh keys fingerprints found for user ubuntu"21:08
roaksoaxedmz: right so the commissioning process actually starts doing something21:10
roaksoaxdid you see if any of the commissioning scripts failed21:10
roaksoaxedmz: go to the machine details page and look at 2 things:21:10
roaksoax1. 'Commissioning' tab and 'Event's tab21:10
roaksoaxthat should give you more details on what may be wrong21:10
edmzi just deleted the machine. Originally i had to add it via the nodes page "Add Hardware" option. Then specifying the MAC address.21:11
edmzI was abou to do that again.21:11
edmzMaybe I am missing a step.21:12
roaksoaxedmz: so auto enlistment may have been failing due to the localhost thing21:12
roaksoaxif that's what you mean21:12
edmzso should I try to boot it without adding it? so it tries to auto enlist it?21:13
roaksoaxedmz: yeah,21:14
roaksoaxbut i'm pretty sure that's the issue21:14
edmzyeah, that did it21:16
edmzStatus new.21:16
edmzroaksoax : I really appreciate your help. It worked.21:21
roaksoaxedmz: cool! glad it does21:25

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