[01:15] <mup> Bug #1583392 opened: Cannot disable DHCP if you remove the subnet first ("Cannot configure DHCP: At least one dynamic range is required.") <MAAS:New> <https://launchpad.net/bugs/1583392>
[01:27] <mup> Bug #1583393 opened: Web UI shows DNS server as 0.0.0.0 when it is not set <MAAS:New> <https://launchpad.net/bugs/1583393>
[01:57] <mup> Bug #1583395 opened: "Enable DHCP" on VLAN does not setup a Reserved Dynamic range for secondary (IPv6) subnets <MAAS:New> <https://launchpad.net/bugs/1583395>
[02:33] <mup> Bug #1583402 opened: Generated hostnames in 2.0 are much less friendly than 1.9 <MAAS:New> <https://launchpad.net/bugs/1583402>
[06:31] <mup> Bug #1583393 changed: Web UI shows DNS server as 0.0.0.0 when it is not set <MAAS:Invalid> <https://launchpad.net/bugs/1583393>
[06:31] <mup> Bug #1583402 changed: Generated hostnames in 2.0 are much less friendly than 1.9 <MAAS:Won't Fix> <https://launchpad.net/bugs/1583402>
[09:29] <johnny__> hello!
[09:29] <johnny__> I am trying to add some nodes to my maas server
[09:30] <johnny__> but they stack in status new
[09:30] <johnny__> they never go to commisioning
[09:30] <johnny__> do you have any idea whats going on?
[11:19] <sbv> hi everyone, with MAAS 1.9.2 is it possible to add custom A or CNAME records into zone controlled by MAAS?
[13:22] <shewless> Hi. I had a working maas server but I tried to change the networking a bit  so that it would assign an IP on the pxe interface as well as another interface. Since I've done that I can't deploy anymore. I see a message flash on the console about some network problem.. do you know if there is a console log I'd be able to view to get more info?
[13:23] <shewless> Here are the logs I can see: http://pastebin.com/Nh3880Hh
[14:18] <shewless> Since my devices are failing deployment I see this on the console on boot: Cloud-init: url_helper.py.: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id failed  Failed to establish a new connection (errno 101 Network is unreachable)
[14:18] <shewless> But I can see that PXE booting is working correctly so the pxe network must be at least partially working
[14:19] <shewless> Does my subnet which is providing DHCP HAVE to have a gateway? I removed the gateway because I wanted to add a default gateway on a different subnet after the fact - could that be causing the problem?
[14:28] <shewless> I'm trying with a gateway set on my PXE/DHCP network. I'll report progress
[16:12] <mup> Bug #1583670 opened: [2.0b5] No way to read settings, like proxy, for non-admin users <juju> <MAAS:New> <https://launchpad.net/bugs/1583670>
[16:20] <shewless> anyone happen to be around to help me figure out why I can't commission/deploy servers? I previously described my problem. After adding a gateway I still have a problem
[16:22] <roaksoax> shewless: it seems that you don't have network connectivity to the region controller
[16:22] <roaksoax> shewless: so it is unable to access the metadata
[16:22] <shewless> roaksoax: but wouldn't pxe fail if that was the case?
[16:23] <roaksoax> shewless: what do you have in /etc/maas/rackd.conf ?
[16:24] <shewless> cluster_uuid: 6137711c-bc3f-4ffd-9080-c76c26635bb3 maas_url: http://localhost:5240/MAAS
[16:24] <mup> Bug #1583685 opened: [2.0b5] Can't force the import of images per Rack COntroller <MAAS:New> <https://launchpad.net/bugs/1583685>
[16:25] <roaksoax> shewless: change localhost with the IP address of the region controller that the machine you are deploying can reach
[16:25] <roaksoax> shewless: for example, if it is a single maas server
[16:25] <roaksoax> shewless: and your DHP range is 10.10.10.0/24
[16:25] <roaksoax> shewless: put the IP address of the region under the same range
[16:26] <shewless> roaksoax: it is a single maas server. Currently I'm using 172.20.0.1/20
[16:26] <roaksoax> shewless: ok, so your maas server has an IP in 172.20.0.1/20 right ?
[16:26] <shewless> roaksoax: actually I just tried "commissioning" a server which was previously working and it does not receive an offer while PXE booting.. so that's not good
[16:27] <shewless> yes. the maas server is 172.20.0.1
[16:27] <roaksoax> shewless: so just change localhost with the IP of your maas server in that range and that should fix it
[16:27] <roaksoax> shewless: ok so do that, change localhost with 172.20.0.1
[16:27] <shewless> roaksoax: okay.  any idea how it got "messed up"?
[16:27] <roaksoax> shewless: the problem when chossing localhost is that MAAS would take all of the IP's of your region controller and chose "any"
[16:27] <roaksoax> shewless: sometimes it will chose the right one, sometimes it may not and ther emay be various resons why it may not
[16:27] <roaksoax> but I think we can look into trying to be starter
[16:28] <shewless> hmm. I also have an "external facing" IP on my maas server
[16:28] <shewless> should I put that IP in or the PXE network IP?
[16:29] <shewless> also, do I need to restart any services after changing rackd.conf?
[16:30] <roaksoax> shewless: no, the reason why it may be failing, it is because is taking the "external facing" isntead of the "internal facing"
[16:30] <roaksoax> shewless: so ensuring that /etc/maas/rackd.conf points to the "internal facing" would solve your problem
[16:30] <mup> Bug #1583685 changed: [2.0b5] Can't force the import of images per Rack COntroller <MAAS:New> <https://launchpad.net/bugs/1583685>
[16:33] <shewless> roaksoax: okay I tried that. the host still isn't pxe booting. When I tcpdump on the interface with the 172.20.0.1 IP on the maas server I see the Bootp/dhcp requests come in from the server I'm trying to commision.. but no repsonse
[16:36] <roaksoax> shewless: restart maas-rackd
[16:36] <roaksoax> shewless: and that should trigger a reconfiguration
[16:36] <roaksoax> shewless: if you have a full console log
[16:36] <roaksoax> shewless: it would be helpful as well
[16:37] <shewless> how do I restart maas-rackd? can I get the console log from the maas server somehow?
[16:38] <roaksoax> shewless: sudo service maas-rackd restart
[16:39] <roaksoax> shewless: and no, maas doesn't store console logs
[16:39] <shewless> unfortunately I don't have console logging on my servers at the moment
[16:40] <shewless> roaksoax: restarting maas-rackd seemed to help at least a little. The PXE boot worked.. we'll see how far it gets
[16:42] <mup> Bug #1583685 opened: [2.0b5] Can't force the import of images per Rack COntroller <MAAS:New> <https://launchpad.net/bugs/1583685>
[16:43] <roaksoax> shewless: if maas makes it to networking and cloud-init configures networking, you will find console logs in /var/log/maas/rsyslog/ , but only starting from 2.09
[16:43] <roaksoax> shewless: if maas makes it to networking and cloud-init configures networking, you will find console logs in /var/log/maas/rsyslog/ , but only starting from 2.0
[16:44] <shewless> roaksoax: Okay my system comissioned correctly!! So is it okay if I remove the gateway and dns settings from the network that provides PXE? What I mean is I don't want the hosts I'm deploying to have a "gateway" of 172.20.0.1.  Is that okay to do that?
[16:44] <shewless> roaksoax: I'm using 2.0.0 so I guess I could check those logs
[16:47] <dbainbri> is there a URL that can be hit in MAAS to just verify that MAAS is "up" and accepting APIs calls, w/o first authenticating? looking to use that URL in an Ansible script to determine when to move forward
[16:52] <kiko> dbainbri, good question
[16:52] <kiko> roaksoax, what of the idea of asking when the package is installed the first time what interface(s) rackd should be listening on?
[16:53] <kiko> dbainbri, GET /api/2.0/version/
[16:53] <kiko> dbainbri, I don't think that requires authentication
[16:53] <kiko> dbainbri, care to ask in askubuntu.com? I'll provide a working example too
[16:55] <dbainbri> kiko: that resulted in HTML, which looked like a redirect for login
[16:55] <kiko> hmm
[16:55] <kiko> dbainbri, could you make an askubuntu.com question so I don't lose your request?
[16:55] <dbainbri> y
[16:56] <kiko> meanwhile talking to a developer
[17:04] <dbainbri> kiko: http://askubuntu.com/questions/774792/unauthorized-maas-url-to-validate-server-is-up-and-running
[17:04] <dbainbri> kiko: right now using an unauthorized response from /api/1.0/maas/
[17:29] <kiko> dbainbri, <allenap> kiko: Ah, /MAAS/api/version/ (note no "2.0") is probably best. It ought to return HTTP 200, content-type text/plain, with the body content "2.0".
[17:29] <kiko> dbainbri, also, https://bugs.launchpad.net/maas/+bug/1583715
[17:32] <dbainbri> kiko: allenap: on a 1.9 server I get a HTTP 302, no content
[17:33] <dbainbri> kiko: allenap: also a Location redirect to login
[17:33] <kiko> bejesus
[17:35] <kiko> that's depressing
[17:35] <kiko> I will need to look at the source now
[17:36] <shewless> Hello. Thanks to roaksoax I was able to get my maas server to work again!  I have 4 servers I can commission/deploy but I have 1 server that fails to commission. Here are the console logs: http://pastebin.com/59L7Km8t
[17:36] <shewless> Looks like some modules-final thing didn't run all the way to completion.
[17:39] <kiko> shewless, is there nothing relevant prior to that?
[17:42] <shewless> kilo: I'll paste the whole thing in a minute
[17:47] <kiko> dbainbri, this is really weird.
[17:48] <kiko> the VersionHandler is marked with AnonymousOperationsHandler
[17:48] <kiko> or inherits from it
[17:49] <mup> Bug #1583715 opened: MAAS version API call should not require authentication <MAAS:New> <https://launchpad.net/bugs/1583715>
[17:59] <shewless> hmm.. it seems deleting the console log wasn't a great idea.. it's not populating at all now :)
[18:02] <kiko> indeed
[20:30] <shewless> Hello. Does anyone know if maas can be easily integrated into ansible?
[21:04] <terje> https://github.com/waldemarbautista/maansible