[01:07] <cmd_pancakes> is it possible to create encrypted LVMs in the MAAS? this question was asked before but not yet answered: http://askubuntu.com/questions/899480/is-it-possible-to-encrypt-with-maas
[01:11] <mup> Bug #1680286 opened: MAAS DNS doesn't handle non /24 subnets well <canonical-bootstack> <maas (Ubuntu):New> <https://launchpad.net/bugs/1680286>
[01:59] <mup> Bug #1680286 changed: MAAS DNS doesn't handle non /24 subnets well <canonical-bootstack> <maas (Ubuntu):Won't Fix> <https://launchpad.net/bugs/1680286>
[07:35] <kklimonda> how can I debug MAAS not assigning "automatic" IPs to nodes after allocating them?
[07:36] <kklimonda> it's doing that for 3 of them, interfaces are defined but in the logs I can see MAAS assigning only one of 3 IPs, and node never transitions from ALLOCATED to DEPLOYING
[07:51] <mup> Bug #1666097 changed: update maas from 2.0 to 2.1 <MAAS:Won't Fix> <https://launchpad.net/bugs/1666097>
[08:09] <mup> Bug #1659538 changed: juju deploy fails, unable to contact charm store <MAAS:Fix Released> <https://launchpad.net/bugs/1659538>
[08:09] <mup> Bug #1659694 changed: Cannot set min kernel to hwe-x <MAAS:Invalid> <https://launchpad.net/bugs/1659694>
[09:34] <kiko> kklimonda, sounds like a networking issue on the nodes themselves
[09:34] <kiko> kklimonda, you can check the DHCP logs to see if the requests are coming in
[09:35] <kiko> there's nothing very magical about the IP allocation -- we choose an IP, tell DHCP to deliver it, and the node picks it up
[10:42] <mup> Bug #1680398 opened: Improper separator used when parsing OAuth Authorization Header <MAAS:New> <https://launchpad.net/bugs/1680398>
[11:27] <mup> Bug #1680409 opened: [2.1.5] Deployment failure with bcache devices <MAAS:New> <https://launchpad.net/bugs/1680409>
[11:39] <mup> Bug #1680409 changed: [2.1.5] Deployment failure with bcache devices <serverstack> <MAAS:New> <https://launchpad.net/bugs/1680409>
[11:42] <mup> Bug #1680409 opened: [2.1.5] Deployment failure with bcache devices <serverstack> <MAAS:New> <https://launchpad.net/bugs/1680409>
[12:57] <mup> Bug #1644856 changed: Issue with changing device naming of boot disk between commissioning and deployment <curtin:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1644856>
[13:27] <mup> Bug #1680409 changed: [2.1.5] Deployment failure on reprovisioned systems with bcache devices <serverstack> <curtin:New> <MAAS:Invalid> <https://launchpad.net/bugs/1680409>
[13:42] <mup> Bug #1680409 opened: [2.1.5] Deployment failure on reprovisioned systems with bcache devices <serverstack> <curtin:New> <MAAS:Invalid> <https://launchpad.net/bugs/1680409>
[13:48] <mup> Bug #1680409 changed: [2.1.5] Deployment failure on reprovisioned systems with bcache devices <serverstack> <curtin:New> <MAAS:Invalid> <https://launchpad.net/bugs/1680409>
[14:18] <mup> Bug #1659694 opened: Cannot set min kernel to hwe-x <MAAS:New> <https://launchpad.net/bugs/1659694>
[14:48] <mup> Bug #1659694 changed: Cannot set min kernel to hwe-x <MAAS:Invalid> <https://launchpad.net/bugs/1659694>
[14:48] <mup> Bug #1680487 opened: [2.2 UI] Machine actions menu is truncated <MAAS:New> <https://launchpad.net/bugs/1680487>
[15:16] <roaksoax> zeestrat: can you please provide the info on: https://bugs.launchpad.net/maas/+bug/1644856/comments/6
[15:16] <roaksoax> zeestrat: for the deployed machine you are having the issue with
[15:18] <mup> Bug #1679222 changed: ISCSI target validation fails when target name includes a ':' <iscsi> <rsd> <curtin:Fix Committed by nacc> <MAAS:Invalid> <MAAS RSD :Invalid> <curtin (Ubuntu):Fix Released> <curtin (Ubuntu Xenial):New> <curtin (Ubuntu Yakkety):New> <https://launchpad.net/bugs/1679222>
[15:25] <roaksoax> zeestrat: nevermind, i see now, you already have attached it
[15:25] <roaksoax> zeestrat: the only thing missing would be fstab
[16:37] <zeestrat> roaksoax: Out of office for a couple of days. I'll see if I can get you the fstab.
[16:55] <mup> Bug #1595755 changed: [2.0b8] MTU does not get set on bonded interfaces <MAAS:Incomplete> <https://launchpad.net/bugs/1595755>
[16:55] <mup> Bug #1680537 opened: Cannot specify additional nameservers for reverse zones <MAAS:New> <https://launchpad.net/bugs/1680537>
[17:09] <cmd_pancakes> is it possible to create encrypted LVMs in the MAAS? this question was asked before but not yet answered: http://askubuntu.com/questions/899480/is-it-possible-to-encrypt-with-maas
[18:04] <roaksoax> cnewcomer: it is not possible
[18:04] <roaksoax> err
[18:04] <roaksoax> sorry
[18:04] <roaksoax> cmd_pancakes: not, it is not possible to create encrypted LVM's via MAAS
[18:05] <xygnal> it seems static ips cannot be used for custom non ububtu images.  is that correct?
[18:05] <cnewcomer> ;)
[18:05] <xygnal> ubuntu*
[18:05] <cmd_pancakes> roaksoax: ok great, thanks...just making sure i wasn't overlooking something
[18:12] <roaksoax> xygnal: maas doesn't configure /e/n/i for custom images *yet*, it will do soon
[18:12] <roaksoax> xygnal: *but* it does create static hostmaps
[18:13] <roaksoax> xygnal: i.e. the same ip that would be configured in e/n/i, is also provided to the DHCP as a hostmap as fallback
[19:10] <mup> Bug #1680567 opened: [2.0] PTR RR is incorrectly placed in parent DNS zone when MAAS controls both. <dns> <MAAS:Incomplete> <https://launchpad.net/bugs/1680567>
[19:50] <xygnal> roaksoax:  we plan to convert the "static" dhcp addresses to local static entries for now.  ie. grab the dhcp ip it gets and convert to local ifcfg- files.   any concerns with how maas will interact?
[19:51] <xygnal> roaksoax: also what is your ball park estimate for custom images having e/n/i?
[20:28] <kiko> xygnal, I think that will work just fine -- once deployed and the IP is handed over MAAS more or less leaves the machine alone
[20:28] <kiko> xygnal, not sure about custom images, but CentOS and Windows are next
[20:29] <roaksoax> xygnal: it is on our roadmap for next 6 months
[20:40] <mup> Bug #1680487 changed: [2.2 UI] Machine actions menu is truncated <MAAS:Invalid> <https://launchpad.net/bugs/1680487>
[23:43] <mup> Bug #1680632 opened: [2.1+] Discovery dashboard should allow filtering by last seen time <MAAS:New> <https://launchpad.net/bugs/1680632>