[07:39] <mup> Bug #1774135 opened: [2.5, snap] dhcpd wasn't started after enabling dhcp on a subnet <MAAS:New> <https://launchpad.net/bugs/1774135>
[07:48] <mup> Bug #1774135 changed: [2.5, snap] dhcpd wasn't started after enabling dhcp on a subnet <MAAS:New> <https://launchpad.net/bugs/1774135>
[07:51] <mup> Bug #1774135 opened: [2.5, snap] dhcpd wasn't started after enabling dhcp on a subnet <MAAS:New> <https://launchpad.net/bugs/1774135>
[11:45] <bjarne> Hi, I saw that 2.4.0-6981-g011e51b7a-0ubuntu1~18.04.1 was availeble in next repo, but  seems  like 2.4.0~rc2 isn't releaset yet. Which branch is that build based on?
[13:01] <roaksoax> bjarne: ? 2.4.0~rc2 -> 2.4.0
[14:03] <roaksoax> bjarne: its the same , its just renamed
[14:49] <mup> Bug #1774206 opened: MAAS denies recursive DNS queries from subnets it doesn't know about <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1774206>
[16:04] <mup> Bug #1774186 opened: curtin does not recognize / partition created in MAAS <cdo-qa> <cdo-qa-blocker> <cpe-onsite> <foundations-engine> <curtin:Triaged> <MAAS:New> <https://launchpad.net/bugs/1774186>
[18:21] <xygnal> is 2.4.0 final out?
[19:31] <xygnal> Ability to increase the number of regiond workers
[19:31] <xygnal> Following the improved way MAAS daemons are run, further internal changes have been made to allow the number of regiond workers to be increased automatically. This allows MAAS to scale to handle an increased number of internal operations in larger environments.
[19:31] <xygnal> does this affect more than UI?
[19:45] <roaksoax> xygnal: yes
[19:46] <roaksoax> xygnal: /win 3
[19:46] <roaksoax> err
[19:47] <roaksoax> xygnal: it allows for more workers communicate with the DB, but would require to increase the amximum number of db connections postgresql accepts
[19:47] <roaksoax> xygnal: but at the same, your issues with the UI should be considerably improved in 2.4
[19:48] <roaksoax> xygnal: without increasing the number of workers
[20:15] <xygnal> yes. impressive release notes sir.
[20:15] <xygnal> looking forward to a lot
[20:16] <mup> Bug #1774266 opened: Validate boot images are available for applicable rack controllers only <MAAS:Triaged> <https://launchpad.net/bugs/1774266>
[21:29] <bdx> concerning 3rd party drivers
[21:29] <bdx> here is my commissioning script https://paste.ubuntu.com/p/V7RZBRRqtq/
[21:30] <bdx> I've tried a few different paths, but can't get maas to pick up the mellanox interfaces in commissioning
[21:31] <bdx> even though the driver install succeeds, and I can ssh into the node following commissioning and see the physical interfaces are there
[21:31] <bdx> no matter what I do, I can't seem to get maas to pick up the mellanox interface in commissioning
[21:31] <bdx> any ideas?
[21:31] <bdx> bug?
[21:32] <roaksoax> bjarne: whats the name of your script ?
[21:32] <roaksoax> err
[21:32] <roaksoax> bdx: ^^ what's the name of your script ?
[21:32] <bdx> 00-install-xenial-mlnx-drivers
[21:33] <bdx> the name in the metadata
[21:35] <roaksoax> bdx: maas should be grabbing the interface information from 'ip addr'
[21:36] <roaksoax> bdx: so that could mean there's no 'ip addr' info for your interface ?
[21:37] <bdx> roaksoax: the node isn't powered on anymore, but a few moments ago this is what `ip a` showed https://paste.ubuntu.com/p/6CjG9MKWPq/
[21:37] <bdx> enp130s0 and enp130s0d1
[21:37] <bdx> ^ the mellanox
[21:38] <roaksoax> bdx: check the output in  99-maas-03-network-interfaces
[21:41] <bdx> roaksoax: it shows the mellanox nic
[21:42] <bdx> https://imgur.com/a/c3XoTcY
[21:42] <roaksoax> bdx: and it is not shown on the interfaces tab ?
[21:42] <bdx> correct
[21:43] <roaksoax> bdx: and when you commissioning, are you selecting 'Retain network configuration' ?
[21:44] <bdx> I have been, let me run another commissioning with that checked just for an isolated test
[21:47] <bdx> jesus
[21:47] <bdx> they just showed up in the interfaces tab
[21:47] <bdx> ahh
[21:47] <bdx> I think I know what changed
[21:48] <bdx> previously, I wasn't adding the metadata tag to recommission
[21:48] <roaksoax> ah gotcha
[21:48] <bdx> as well as checking "retain network"
[21:48] <bdx> roaksoax: thanks
[21:49] <bdx> roaksoax: now I have the drivers being installed during commissioning, and the interfaces recognized
[21:49] <bdx> is my next step to get the drivers into the image at deploy time to build a deb and add them to the drivers.yaml?
[21:53] <roaksoax> bdx: i would probably recommend you install them the same way you are doing in the ephemeral enviromment
[21:53] <roaksoax> bdx: via curtin preseeding
[21:53] <roaksoax> bdx: i have  quesiton though, are these drivers not available in Ubuntu at all ?
[21:53] <bdx> roaksoax: correct
[21:54] <roaksoax> so i guess mellanox has not upstreamed these drivers into the linux kernel?
[21:54] <bdx> also correct
[21:54] <roaksoax> ok gotcha
[21:55] <bdx> http://www.mellanox.com/related-docs/prod_software/Mellanox_EN_for_Linux_User_Manual_v4_3.pdf - chapter 2.9 "Installing using apt-get"
[21:55] <bdx> they suggest building a deb with the included packaging and serving them up from a local file repo
[21:56] <bdx> I have been trying to build the deb and upload it to launchpad under my own ppa
[21:56] <bdx> ^ then I could just create an entry in drivers yaml
[21:56] <bdx> the preseed may be easier for sure
[21:56] <bdx> because the packaging doesn't build successfully on launchpad
[21:56] <roaksoax> right
[21:57] <bdx> I've been trying to fix/hack it
[21:57] <roaksoax> yeah the preseed may be straightforward since you already have such script
[21:57] <roaksoax> you could just run that script in a late_command
[21:57] <roaksoax> inside the installed target
[21:57] <bdx> totally
[21:58] <bdx> I've done this before back in 1.7 or something ..... are the preseeds under SNAP_COMMON now I take it?
[22:03] <bdx> I can setup a new apt installed maas
[22:03] <bdx> I want to deploy all my new things under maas 2.4 anyway
[22:03] <roaksoax> probably not, since we are still working on getting the snap done for 2.4, we haven't made changes wrt to the snap in 2.3
[22:04] <bdx> ok
[22:04] <bdx> I may want to use maas from apt is what you are saying
[22:04] <bdx> got it
[22:04] <roaksoax> indeed
[22:04] <bdx> ok
[22:04] <roaksoax> bdx: you could then migrate to a 2.4 snap, once ready, pointing it to your current DB
[22:05] <bdx> roaksoax: totally
[22:05] <bdx> well, I have the two entirely decoupled
[22:06] <bdx> so that will probably be even easier
[22:07] <bdx> roaksoax: how do I migrate the db from 2.3.x -> 2.4 ?
[22:29] <mup> Bug #1771885 opened: bionic: static maas missing search domain in systemd-resolve configuration <bionic> <network> <cloud-init:New> <juju:Fix Committed by ecjones> <juju 2.3:Fix Released by ecjones> <MAAS:New> <https://launchpad.net/bugs/1771885>
[22:38] <roaksoax> bdx: i would suggest you backup your db
[22:38] <roaksoax> bdx: once that's done, isntall maas from packages
[22:38] <roaksoax> sudo service maas-regiond stop
[22:38] <roaksoax> bdx: then configure /etc/maas/regiond.conf to point to where the 2.3 db is
[22:39] <roaksoax> bdx: and then run: sudo maas-region dbupgrade
[22:39] <roaksoax> bdx: then: sudo service maas-regiond restart
[22:39] <roaksoax> bdx: you /may/ need to rm -rf /var/lib/maas/secret and let maas re-create a new one
[22:40] <bdx> ok, awesome
[22:40] <bdx> roaksoax: my maas is currently deployed to a xenial box, and my postgresql is on another xenial box
[22:41] <bdx> roaksoax: is 2.4 compatible with xenial, or should I deploy a bionic host to install maas from apt on?
[22:41] <roaksoax> bdx: you'd need bionic
[22:41] <bdx> thats what I thought
[22:41] <roaksoax> bdx: i'll check what the status of the snap is tomorrow though, since we were dependent on core18 changes
[22:41] <roaksoax> s/core18/base18
[22:43] <bdx> great, thanks for all of this
[22:50] <roaksoax> np!