[10:18] <eriklonroth> Hello, I'm taking my first steps in a real MAAS setup and got stuck at enlisting my nodes. What is the most default procedure to enlist a node in MAAS? As of today, I seem to hit an error in the final stage of cloud-init.  "Can not apply stage final, no datasource found! Likely bad things to come!". The nodes fetches the PXE image and is now also reachable on the network at the same vlan/subnet as my region and rack
[10:18] <eriklonroth> controller.  https://pasteboard.co/H5BL9bp.png   What am I doing wrong?
[10:25] <eriklonroth> Do I have to go through the "Nodes" -> "Add machine" and enter the MAC addresses of my nodes?
[14:18] <roaksoax> eriklonroth: that looks like your machines dont have access
[14:18] <roaksoax> eriklonroth: to the metadata
[14:18] <roaksoax> eriklonroth: ensure that /etc/maas/rackd.conf has maas_url pointing to the IP of the region that the machines can access to
[14:18] <eriklonroth> I think I might have hot something like this: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1665680
[14:18] <eriklonroth> hit*
[14:19] <roaksoax> eriklonroth: did you ensure that /etc/maas/rackd.conf maas_url points to the IP address of the machines can access to ?
[14:19] <eriklonroth> I have 2 interfaces where one is public 138.106.9.174 and the other local/private 10.6.5.1
[14:20] <roaksoax> eriklonroth: the error on the screenshot looks to me that it is misconfigured
[14:20] <eriklonroth> Currently, the 138.106.9.174 is in both  /etc/maas/rackd.conf  and  /etc/maas/regiond.conf
[14:21] <eriklonroth> The interface dhcp is on is 10.6.5.0
[14:21] <roaksoax> i bet
[14:21] <roaksoax> ok
[14:21] <roaksoax> so that's the bug
[14:21] <eriklonroth> Should I set rackd.conf to 10.6.5.1 ?
[14:21] <roaksoax> the amchine is trying to access 138.106.9.174
[14:21] <roaksoax> from the 10.6.5.x
[14:21] <roaksoax> and it cannot reach it
[14:22] <roaksoax> so you need to change rackd.conf to point to itself on the IP the deploying machiens can access to
[14:23] <eriklonroth> OK, regiond can stay the same 138.106.9.174 ?
[14:23] <eriklonroth> Do I need to restart any services after that config change? ?
[14:25] <roaksoax> eriklonroth: only rackd.conf should really be the one needed to be changed
[14:25] <roaksoax> yes, sudo service maas-rackd restart
[14:37] <eriklonroth> It worked!
[14:37] <eriklonroth> I'm commissioning the server as it should. Thanx for assisting me!
[14:56] <roaksoax> eriklonroth: cool
[15:05] <kiko> excellent
[16:32] <mup> Bug #1746760 opened: feature: MAAS to collect curtin error_tarfile in post_files curtin config <MAAS:New> <https://launchpad.net/bugs/1746760>
[16:35] <mup> Bug #1746760 changed: feature: MAAS to collect curtin error_tarfile in post_files curtin config <MAAS:New> <https://launchpad.net/bugs/1746760>
[16:41] <mup> Bug #1746760 opened: feature: MAAS to collect curtin error_tarfile in post_files curtin config <MAAS:New> <https://launchpad.net/bugs/1746760>
[20:13] <mpontillo> xygnal: replied on your bug with an idea for testing
[20:37] <mpontillo> xygnal: even though network discovery is disabled, it is still maintaining historical data which could be removed
[20:38] <xygnal> wiped that now
[20:38] <mpontillo> xygnal: thanks
[20:46] <xygnal> attached ss of one of the larger payloads
[20:46] <xygnal> not sure what its doing
[21:09] <mpontillo> xygnal: so clearing the discovery data didn't help?
[21:09] <Phill93_> Hi
[21:10] <Phill93_> is it possible to set the default domain for new nodes?
[21:10] <mpontillo> Phill93_: currently the only way is to use the API to rename the default domain to what you want
[21:11] <mpontillo> Phill93_: that is, you can use the `maas` command (it's a front-end to the API)
[21:12] <Phill93_> ok a rename is a good idea
[21:16] <mpontillo> roaksoax: updated citibank doc with a few words on archive mirroring
[21:17] <mpontillo> roaksoax: I think I'll leave it at that. they didn't really take action on our comments though. I feel we've reviewed, revised, and given our input at this point
[21:17]  * mpontillo -> lunch
[21:17] <Phill93_> thank you mpontillo that worked
[21:17] <Phill93_> bye
[21:54] <mup> Bug #1746817 opened: Failed Commissioning smartctl-validate <commisioning> <hardwaretest> <smartctl-validates> <MAAS:New> <https://launchpad.net/bugs/1746817>
[23:42] <mup> Bug #1746831 opened: [2.3, 2.4] Error on node storage section not surface <MAAS:New> <https://launchpad.net/bugs/1746831>
[23:48] <mup> Bug #1746831 changed: [2.3, 2.4] Error on node storage section not surface <MAAS:New> <https://launchpad.net/bugs/1746831>
[23:57] <mup> Bug #1746831 opened: [2.3, 2.4] Error on node storage section not surface <MAAS:New> <https://launchpad.net/bugs/1746831>