[00:03] <mup> Bug #1670886 changed: BIND config should include option "empty-zones-enable no" <MAAS:New> <https://launchpad.net/bugs/1670886>
[00:12] <mup> Bug #1670886 opened: BIND config should include option "empty-zones-enable no" <MAAS:New> <https://launchpad.net/bugs/1670886>
[08:05] <Hetfield> good morning. i think i have an issue with maas networking, i'm using latest 2.1.3 version
[08:05] <Hetfield> i have a machine with 2 eth ports, on different spaces
[08:06] <Hetfield> with juju i try: juju deploy ceph-osd --constraints spaces=management
[08:06] <Hetfield> where management is the primary space
[08:06] <Hetfield> in maas.log i see
[08:06] <Hetfield> Mar  8 07:57:52 maas maas.api: [info] Request from user admin to acquire a machine with constraints <QueryDict: {'interfaces': ['0:space=1'], 'zone': ['CDM'], 'agent_name': ['acc01708-cf3b-4970-826e-37422930d18f']}>
[08:07] <Hetfield> so space=1 is invoked, but i see that juju gets the public ip from the secondary interface.
[08:08] <Hetfield> which should be a private one and not accessible from juju machine. the strange thing is that machine hostname resolves to the primary "management" space, so i'm really curious why it gets the secondary address
[11:17] <mup> Bug #1671048 opened: [2.1.4]Expecting object recived tuple in get_default_dns_servers <MAAS:New> <https://launchpad.net/bugs/1671048>
[12:11] <cnf> how do i get the MAAS proxy to allow ports that are not 443?
[13:47] <kukacz> hi, I got troubles with PXE booting UEFI image from MAAS 2.1.4 - it ends in Grub commandline
[13:48] <kukacz> from Grub I can exit, confirm BIOS prompt asking for continue, then it loads and boots that discovery image correctly
[13:49] <kukacz> any first attempt after server reboot fails, however
[13:49] <kukacz> any ideas what could be wrong?
[13:55] <kiko> the last time this happened we concluded it was a problem with grub
[13:55] <kiko> does typing normal at the grub prompt boot the system?
[13:55] <kiko> are you deploying 14.04 or 16.04?
[13:55] <kukacz> kiko: deploying 16.04
[13:56] <kukacz> kiko: I haven't tried that "normal", will do
[13:56] <kiko> references:
[13:56] <kiko> https://bugs.launchpad.net/maas/+bug/1532935
[13:56] <kiko> https://bugs.launchpad.net/maas/+bug/1437353
[14:04] <kukacz> "normal" did not help, it just returned to prompt
[14:05] <kukacz> however "exit" and "continue" (BIOS menu) always successds
[14:05] <kukacz> succeeds
[14:10] <kiko> kukacz, I wonder if you could easily capture a video of that including firmware revisions etc and attach that to a bug?
[14:10] <kiko> it should always work, but there are known firmware issues that we may not yet work around
[14:25] <kukacz> I'll go through those bugs to identify which one might be related and attach that video possibly
[14:26] <kukacz> firmware - you mean NIC firmware? I may give it a try - it's intel x520 in Dell servers
[14:41] <kiko> kukacz, great I suggest putting it into a new bug as those are a bit stale -- we can easily dupe if necessary
[17:38] <tychicus> is it possible to change the maas default domain?
[17:46] <tychicus> default domain only appears on the web interface it does not appear in the CLI
[18:00] <kiko> kukacz, both NIC and system firmware if possible
[18:01] <kiko> tychicus, from ".maas" to something else?
[18:01] <kiko> tychicus, that would be a bug
[18:01] <kiko> could you file it?
[18:02] <tychicus> @kiko correct from .maas to something else
[18:03] <kiko> you can change the domain from the UI for sure
[18:04] <tychicus> it seems like you can add a domain, but not change the default
[18:07] <tychicus> ok, just verified that you can update the default domain from the cli
[18:08] <tychicus> kiko bugs should be filed here https://bugs.launchpad.net/maas
[18:08] <kiko> tychicus, yep
[18:11] <tychicus> to clarify the we ui displays something like maas (default), there is no such concept in the cli, my guess (without looking at the code) is that the default domain is inferred from the domain id of 0
[18:12] <tychicus> either way, I'll write up a bug report, thanks!
[18:31] <kiko> thanks tychicus
[18:31] <tychicus> sure, loving maas so far, glad to help out in any way I can
[19:55] <kiko> tychicus, wow, that's great to hear -- what are you using it for?
[19:56] <tychicus> kiko, currently testing openstack deployments and playing with juju
[19:57] <tychicus> I have not attempted to deploy windows using maas yet, but that is on my list of things to do
[19:59] <kiko> cool, keep me posted on your progress
[20:01] <tychicus> I really like the new features in 2.0 and 2.1 that allow you to setup networking and disk layouts, once the machine has been commissioned
[20:05] <mup> Bug #1671201 opened: juju bootstrap maas maas-controller: No available machine matches constraints <juju-core:Invalid> <MAAS:New> <https://launchpad.net/bugs/1671201>
[21:06] <mup> Bug #1671242 opened: [2.1.3] maas cli  does not indicate which domain is default <MAAS:New> <https://launchpad.net/bugs/1671242>
[23:27] <mup> Bug #1671275 opened: MAAS rescue mode cannot run snap binaries <maas (Ubuntu):New> <https://launchpad.net/bugs/1671275>
[23:30] <mup> Bug #1671274 opened: network interface doesn't come up after installation in VM <cdo-qa-blocker> <MAAS:New> <https://launchpad.net/bugs/1671274>