mup | Bug #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 working | 03:12 |
sentinel__ | ...anyone | 03:20 |
mup | Bug #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 | ||
angelinux | hello do you know how to setup wake-on-lan power type on maas 2.2 ? | 09:59 |
angelinux | https://stgraber.org/2017/04/02/using-wake-on-lan-with-maas-2-x/ this is not working anymore | 10:01 |
=== cnfer is now known as cnf | ||
mup | Bug #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 | ||
mup | Bug #1726534 opened: [2.3, HWTv2] Fio does not always gather metrics <MAAS:Triaged> <https://launchpad.net/bugs/1726534> | 19:13 |
bdx | ryebot: juju reload-spaces | 20:00 |
lamont | roaksoax: 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 again | 20:41 |
* lamont will turn on more debugging later, but it may be quite later | 20:42 | |
roaksoax | lamont: 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 server | 20:43 |
roaksoax | lamont: or actuall, also check /etc/maas/regiond.conf has the correct maas_url too | 20:44 |
edmz | I 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 |
edmz | Is there a way to specify which ip the booting node must use for accessing MAAS? | 20:44 |
lamont | maas_url: http://localhost:5240/MAAS | 20:45 |
* lamont updates | 20:45 | |
roaksoax | edmz: same as for lamont, make sure /etc/maas/rackd.conf doesn't point to localhost and points to an IP the machines can access to | 20:45 |
edmz | roaksoax : thank you | 20:47 |
lamont | roaksoax: when the maas_url in regiond.conf was a hostname, everything hated life. | 20:50 |
lamont | roaksoax: which was left over from having ipv4 and 6 active on different vlans on the same rack | 20:51 |
lamont | I'll poke at it some more at some point | 20:52 |
edmz | roaksoax: it worked. | 20:54 |
roaksoax | lamont: probably dns resolution ? | 20:54 |
lamont | I 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 |
roaksoax | lamont: but yes there's still some leftovers there | 20:54 |
lamont | roaksoax: yeah, possibly that | 20:54 |
roaksoax | edmz: cool! | 20:54 |
edmz | is there a place where I can read about the support/limits of using servers that dont have IPMI/BMC? | 20:55 |
roaksoax | edmz: supported power types are listed here: https://docs.ubuntu.com/maas/devel/en/nodes-power-types | 20:56 |
edmz | roaksoax : currently I am testing with virtualbox. My real servers do have BMC | 20:57 |
roaksoax | edmz: you can use "manual" power type | 20:59 |
edmz | That 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 |
edmz | and I get a "failed comissioning" status. | 21:01 |
roaksoax | edmz: uhmm are they pxe booting and then something happens, and then it changes to failed commissioning ? | 21:02 |
edmz | I only see 1 node in the nodes page. It always has "failed commisioning" status. | 21:04 |
edmz | If I boot that node, while the boot process is going on nothing changes on the nodes page. | 21:04 |
edmz | The boot processs continues past the part where it is downloading packages from ubuntu servers | 21:05 |
edmz | then the virtualbox window suddenly closes. | 21:05 |
edmz | I managed to save a video of the output with Virtualbox. | 21:05 |
edmz | I see, it is actually running shutdown. | 21:06 |
edmz | the only odd thing I see is "ci-info: no authorized ssh keys fingerprints found for user ubuntu" | 21:08 |
roaksoax | edmz: right so the commissioning process actually starts doing something | 21:10 |
roaksoax | did you see if any of the commissioning scripts failed | 21:10 |
roaksoax | edmz: go to the machine details page and look at 2 things: | 21:10 |
roaksoax | 1. 'Commissioning' tab and 'Event's tab | 21:10 |
roaksoax | that should give you more details on what may be wrong | 21:10 |
edmz | i just deleted the machine. Originally i had to add it via the nodes page "Add Hardware" option. Then specifying the MAC address. | 21:11 |
edmz | I was abou to do that again. | 21:11 |
edmz | Maybe I am missing a step. | 21:12 |
roaksoax | edmz: so auto enlistment may have been failing due to the localhost thing | 21:12 |
roaksoax | if that's what you mean | 21:12 |
edmz | yeah | 21:12 |
edmz | so should I try to boot it without adding it? so it tries to auto enlist it? | 21:13 |
roaksoax | edmz: yeah, | 21:14 |
roaksoax | but i'm pretty sure that's the issue | 21:14 |
edmz | yeah, that did it | 21:16 |
edmz | Status new. | 21:16 |
edmz | roaksoax : I really appreciate your help. It worked. | 21:21 |
roaksoax | edmz: cool! glad it does | 21:25 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!