[04:29] Bug #1643651 changed: MAAS UI takes a long time to load a node page [04:29] Bug #1653308 changed: MAAS Power check fails before deployment for AMT > 8 === frankban|afk is now known as frankban [09:21] Hi @here [09:22] Is there anyone up there? [10:00] hi elmo [10:03] Hi D4RKS1D3 [10:04] Did someone already tryed to deploy servers with MAAS setting all NICs in Bonding mode? I've got a really weird situation. [10:06] The server is correctly installing and finishing the curtin install. However, the server is unable to be reached over the network at the next reboot because of an error at launch. [10:07] For me is working fine this funcionally since 1.9.3 [10:08] the error is ubuntu initialization getting stuck with: "Starting to raise a job for network interface" message, waiting for more than 5 mins and then failing to get any IPs and so retrieve Maas Datasource Metadata [10:08] using Rescue mode is working perfectly [10:09] when the machine is gonna deploy you put the network on each interface elmo ? [10:09] You have the dhcp enable? [10:09] DHCP/DNS is enable [10:09] and in the commisioning part you can access to the machine? [10:10] ssh -i cert -l user ip [10:10] yes [10:10] the problem return when the machine is in a deployed state? [10:11] I have eno0 and eno1 aggregated as Bond0 with untagged VLAN and unset subnet then Bond0.101 as VLAN 101 and Subnet CIDR: 10.0.1.0/24 and Bond0.42 as VLAN 42 with Subnet CIDR: 10.0.42.0/24 [10:11] yes everything is fine when on commissioning mode or rescue mode [10:12] except that in rescue mode instead of setting the network as requested into the dashboard, the ephemeral is raising ENO1 with DHCP on VLAN101 without honoring the requested Network topology from the dashboard [10:13] Our network being what it is, I'm so able to connect on the machine in rescue mode. [10:16] Just looked at the node installation networking file by mounting the LVM Volume into rescue mode, the /etc/network/interfaces file is just fine :'( really doesn't get it. [10:49] OK, nevermind, I think it's an issue on my own. I'll deal with my networking team. [12:43] Is it normal that MAAS Rescue mode image doesn't mount the vlan module? [14:21] elmo: i believe so. Since the ephemeral envinronment is rescue mode is just like commissioning, I dont think we specifically tell it to mount non-default/standard modules [14:43] the issue here is that I can't even mount it manually as it is not even installed on the /lib/ path. [14:45] even if the apt package is :'( [14:46] a modprobe for 8021q is so complaining about the module not being installed on /lib/blabla which is true as when I'm looking for the waited location (Using locate 8021q) it is empty. [14:52] I really can't get why my bonds nic are not retrieving IPs through DHPC and all declared as Enslaving enoX as a backup interface with a down link. [15:17] Bug #1712096 opened: [2.x] Ephemeral environment lacks modules: modprobe: FATAL: Module 8021q not found in directory /lib/modules/4.10.0-32-generic

[15:33] thanks a lot mup [15:33] elmo: mup is just a bot [15:33] :) [15:33] ah ah ah just read the bug report, thanks a lot Andres ;-) [15:33] wherever you are :D [15:34] roaksoax: oh, ok :D [15:34] that's me [15:36] roaksoax: Nice thank for having created it. [15:38] ok guys, it's been a pleasure, I've got to go :D see you tomorrow. [15:47] Bug #1712106 opened: [2.2] builtins.OSError: [Errno 24] Too many open files: '/var/lib/maas/secret' [15:56] Bug #1712106 changed: [2.2] builtins.OSError: [Errno 24] Too many open files: '/var/lib/maas/secret' [15:59] Bug #1712106 opened: [2.2] builtins.OSError: [Errno 24] Too many open files: '/var/lib/maas/secret' [16:29] Bug #1712115 opened: Sorting by RAM only sorts on first digit, not actual amount === frankban is now known as frankban|afk [19:17] Bug #1711794 changed: To bridge interfaces with Openvswitch(OVS) [19:30] 5 [19:41] 6 [20:12] roaksoax: the new update fixes the images issues i had. but the resolv.conf is still a problem [20:13] roaksoax: now the gui shows synced for the image and downloads new updates [20:13] thanks [20:13] 2.3.0~alpha2-6193-g59011ef-0ubuntu1~16.04.1 this version [20:29] Bug #1709850 changed: Can't enlist Huawei node with MaaS 2.2.1 [21:56] Bug #1712205 opened: [2.2] MAAS should batch multiple DNS changes into a single reload request