2012/09/06/#maas.txt

[01:17] <robotfuel> I've uninstalled maas and now I can't re-install it. I get an error message about password authentication failed for "maas" when I try.
[03:10] <jtv> smoser: would you be around for some help with omshell by any chance?
[03:37] <jtv> roaksoax maybe?
[03:38] <lifeless> bigjools: hi
[03:38] <lifeless> bigjools: shall we dance ?
[03:38] <jtv> Oh hi lifeless
[03:38] <jtv> He may still be lunching.
[03:45] <lifeless> kk
[04:21] <bigjools> lifeless: I iz back
[04:21] <lifeless> cool
[04:21] <lifeless> video ?
[04:21] <bigjools> yarp, hang on
[04:22] <bigjools> jtv, want to join?
[04:23] <jtv> ?
[04:23] <bigjools> the call
[04:23] <bigjools> about architecture
[04:23] <jtv> uh sure
[04:23] <jtv> plus?
[05:54] <jtv> bigjools: stuck again with dhcpd.  Error reporting is minimal.  I get an I/O error whenever I try a host with its IP address as the name.
[05:54] <jtv> Which could mean just about anything.  There's certainly no attempt at I/O.
[05:56] <jtv> At least, not at the level that strace would see.
[05:57] <jtv> The server receives my omshell request, and replies with an I/O error.  That's pretty much all that strace sees.
[06:02] <jtv> (Surprisingly, dhcpd checks for errors from fprintf/fputs/fputc by seeing if they set errno — but ignoring return value.  I thought those functions were allowed to set a nonzero errno on successful runs, in which case the application should ignore it.)
[06:04] <bigjools> jtv: paste session
[06:05] <jtv> bigjools: http://paste.ubuntu.com/1188377/
[06:05] <jtv> Problem is, dhcpd can decide that the leases file isn't sane.  The logging in the source doesn't look very helpful, but I might try getting at it.
[06:08] <bigjools> jtv: you need quotes around the name value
[06:08] <bigjools>                                                               
[06:08] <bigjools> > set
[06:08] <bigjools> argh
[06:08] <bigjools> set name = "192.168.35.70"
[06:08] <jtv> Grrr.  It parses an IP address quite happily.
[06:08] <bigjools> yes
[06:09] <jtv> Didn't see the quotes in the template, either.
[06:09] <bigjools> then it's buggy :/
[06:09] <jtv> So not clear where they come from in our Omshell class.
[06:09] <jtv> But then how could it possibly work?
[06:09] <jtv> Oh well, at least I managed to reproduce the problem with a quoted name.  Just not with the way we seem to do it in the Omshell code.
[06:11] <jtv> Aren't you getting Omshell errors in your Q/A setup, with manage_dhcp enabled?
[06:11] <bigjools> omshell wasn;t getting called the last time I QAed
[06:11] <bigjools> you fixed it recently
[06:12] <jtv> That'd do it.
[06:12] <jtv> Shall I just file a bug then, so that we at least check this?
[06:12] <bigjools> we also need
[06:12] <bigjools> set hardware-type = 1
[06:12] <bigjools> which is missing ATM
[06:13]  * jtv files one bug, 2 cards
[06:27] <bigjools> jtv: "it would be good to see confirmation in Q/A" What?
[06:28] <jtv> The "I/O error" I'm getting might still be something weird in my setup.  For whatever reason the omshell just accepts an IP address there, and parses & represents it in its own format.
[06:29] <jtv> Maybe it's just too generic and accepts any kind of argument though.
[06:29] <jtv> Anyway, I suspect we'd be wanting the generated hostname there, right?
[06:31] <bigjools> jtv: I recreated locally
[06:31] <bigjools> quoting fixes
[06:31] <bigjools> jtv: hostname is irrelevant actually
[06:31] <jtv> Yes, I just don't know what the reason was why we had the ip address there.
[06:32] <bigjools> jtv: it just needs to be a fixed identifier
[06:32] <jtv> If hostname is irrelevant, do we need it here at all!?
[06:32] <jtv> Ah
[06:32] <bigjools> IP address works fine
[06:32] <jtv> Puzzling stuff!
[06:32] <bigjools> omapi is shite
[06:32] <jtv> I'll note it on the bug.
[06:32] <jtv> It's from an age when getting a string all the way to the user was a job in itself.
[06:32] <bigjools> mmyes
[06:33] <jtv> But I don't see how the errno handling could have been correct or portable.
[06:33] <jtv> errno = 0;
[06:33] <jtv> fprintf(...);
[06:33] <jtv> if (errno) handle_error();
[06:33] <jtv> I've been bitten by that.  AFAIK standard-library functions can set a nonzero errno even on success.
[06:37] <jtv> Well, since we've discussed it now, I'll just write up that fix.
[11:56] <jtv> roaksoax, are you around?
[11:56] <jtv> Too early, probably -- sorry for waking you, better go back to sleep.  :)
[11:57] <jtv> Daviey, maybe you can help?  I'm creating a custom upstart job to run dhcpd with our own defaults & config, and updating HACKING.txt.  I have a few questions about it.
[11:58] <roaksoax> jtv: not yet oficially but what's up :)
[11:58] <jtv> Good morning :0
[11:58] <jtv> :)
[11:59] <roaksoax> morning :)
[11:59] <roaksoax> jtv: what are your questions about it?
[11:59] <jtv> I'm creating a custom upstart job, so that we can use custom config files that we're free to modify.
[11:59] <jtv> Questions:
[11:59] <jtv>  - Where do I put the upstart script?  In the maas package, or in the packaging branch, or elsewhere?
[12:00] <jtv>  - Where do I put the new /etc/default/maas-dhcp-server config/script file?
[12:00] <roaksoax> jtv: in the packaging branch
[12:00] <jtv> Ah OK
[12:00] <roaksoax> jtv: look at debian/maas.maas-celery.upstart
[12:00] <roaksoax> jtv: look at debian/maas.maas-*.upstart
[12:00] <jtv>  - Are we keeping the maas-dhcp package?  I'm updating HACKING.txt but just installing isc-dhcp-server won't do it any more.  You'll need the custom stuff installed.
[12:00] <roaksoax> jtv: what's custom stuff?
[12:00] <jtv> Ahh and I just add my own maas.maas-dhcp-server.upstart ?
[12:01] <jtv> The custom upstart script and the custom /etc/default/... file.
[12:01] <roaksoax> jtv: yes, well kind of. It would be: maas-dhcp.maas-dhcp-server.upstart
[12:01] <jtv> Wow :)
[12:01] <jtv> So that answers my question about the maas-dhcp package.
[12:01] <roaksoax> jtv: and about the default, i think you can also do maas-dhcp.default
[12:01] <roaksoax> and the package system will take care of installing them in the appropriate places
[12:01] <jtv> Will it all automatically be owned by maas:maas?
[12:02] <roaksoax> jtv: nope
[12:02] <jtv> For files we want to write to, I thought it'd make sense to skip the sudo dance while we're at it.
[12:02] <jtv> Say, maybe it would be good to have a quick face-to-face chat about it?
[12:02] <roaksoax> jtv: so the idea is to write files in a maas owned location
[12:02] <jtv> That way I can say I had a proper pre-imp call.  :)
[12:02] <roaksoax> and dhcp would just source from there
[12:03] <roaksoax> jtv: sure, give me 5
[12:03]  * jtv gives roaksoax 5
[12:06] <roaksoax> jtv: ready
[12:06] <jtv> See if this works... https://plus.google.com/hangouts/_/51b1cfe53b7b186ae3519d28fac1eff5b7ce2bdb?authuser=0&hl=en-GB
[13:14] <smoser> rbasak, https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1031065
[13:14] <ubot5> Ubuntu bug 1031065 in cloud-init (Ubuntu) "cloud-init-nonet runs 'start networking' explicitly" [Medium,Triaged]
[13:15] <smoser> right now i'm suspecting that you're hitting the other race condition that slangasek mentioned.
[13:15] <smoser> that you have /run but not "virtual-filesystems".
[13:15] <smoser> hm..
[13:16] <smoser> yeah. thats the issue.
[13:16] <smoser> i wonder which if th evirtual fileysstems you're not getting.
[13:16] <smoser> rbasak, can you get the same log, but with '--verbose' added to the mountall command line in /etc/init/mountall.conf ?
[13:17] <rbasak> smoser: sure. Though I'm running some tests right now - I'll need to do it a bit later
[13:17] <rbasak> smoser: you still want the upstart --verbose too?
[13:17] <smoser> yeah.
[13:17] <rbasak> OK
[14:55] <jtv> roaksoax: turns out the only real sticking point with the existing apparmor profile for dhcpd is the pidfile.  And I can't find any documentation to support having multiple profiles for the same executable...  what if we just hardlinked /usr/sbin/maas-dhcpd to /usr/sbin/dhcpd and created a new profile?
[14:56] <jtv> Oh hi there smoser — thanks for spotting the fatal flaw in our grand config-writing scheme.  Currently working around it.
[14:57] <smoser> jtv, i talked with jdstrand about the apport changes.
[14:57] <smoser> and he's fine with them.
[14:57] <jtv> s/apport/apparmor/ ?
[14:57] <smoser> ie, adding a sectoin to the apport stanza to allow maas to have well defined config.
[14:57] <smoser> yes
[14:57] <smoser> sorry
[14:57] <smoser> i also use the words 'landscape' and 'launchpad' interchangeably
[14:57] <jtv> Burn in hell!
[14:58] <jtv> You unox geeks are all the same.
[14:58] <roaksoax> lol
[14:58] <jtv> Rolix, Relix — what's the difference?
[14:58] <roaksoax> jtv maybde jdstrand knows better
[14:58] <roaksoax> smoser but that doesnt solve precise
[14:59] <smoser> we can solve that.
[14:59] <smoser> but i'm hesitent to tell you how
[14:59] <smoser> because i think you'll like the idea for quantal also
[15:00] <jtv> And that's bad?  Now I'm curious.  :)
[15:00] <smoser> hold on, collecting data
[15:01] <roaksoax> k
[15:02] <smoser> ok . so /etc/apparmor.d/usr.sbin.dhcpd is pastebinned at http://paste.ubuntu.com/1189094/
[15:02] <smoser> note lines 57 and 58
[15:03] <smoser> i believe that renders to "/etc/apparmor.d/local/usr.sbin.dhcpd" (i'm not sure of the path, but obvioysly it does *something*)
[15:03] <smoser> that file is *not* a config file, so its more ok for maas to poke at it
[15:03] <jtv> Why isn't it a config file?
[15:03] <jtv> (It exists — I looked at it earlier)
[15:04] <smoser> hm.. strange that it exists.
[15:04] <jtv> Placeholder comment, basically.
[15:04] <jtv> I guess mostly to stop the #include from breaking.
[15:04] <jtv> But yes, I had that A-HAH moment too.  :(
[15:04] <smoser> hm..
[15:04] <smoser> well jdstrand suggested it.
[15:05] <smoser> if it is a conf file, but you are explicitly expecting someone to update it, then thats broken by design
[15:05] <jtv> Or BSD, depending on your nomenclature.
[15:05] <smoser> well, maybe its not so bad.
[15:05] <smoser> the conf file prompt comes when you have local changes to a file and hte package has changes to the file
[15:06] <smoser> it would seem *very* unlikely for the package to ship a change to that header stub
[15:06] <smoser> and if it did, the package maintainer would surely be aware that they were going to force config file prompts for all users.
[15:06] <smoser> so they'd want to avoid if at all possible.
[15:06] <smoser> anyway... i'd much rather see us change that file, and would seem ok for us to do that for precise.
[15:07] <smoser> reasonable?
[15:07] <jtv> Wouldn't the hardlink solution make it all a bit easier?
[15:07] <jtv> Assuming it would even work.
[15:07] <smoser> well.
[15:07] <smoser> a.) we shouldn't just look for the easiest solution
[15:08] <smoser> b.) how would you package the hardlink?
[15:08] <jtv> Create it in postinst?
[15:08] <smoser> then you have an unpackaged file in /usr/sbin
[15:08] <smoser> which screams WHAT_THE_%*#*_IS_THIS!
[15:08] <jtv> Ship a dummy, replace with hardlink?
[15:09] <smoser> then you have a file in /usr/bin that looks like it has been modified if you check checksums of your package
[15:09] <smoser> which, again screams *#*$**
[15:09] <jtv> True, true — but it's about the most policy-compliant trick we have so far, no?
[15:10] <smoser> i think editing the local file is ok. imo.
[15:10] <smoser> with hardlink, what happens on upgrade of package?
[15:10] <jtv> Heh.
[15:10] <smoser> with upgrade of isc-dchp-server?
[15:10] <jtv> You're right.
[15:11] <smoser> so my suggestion is update apparmor profile for quantal.
[15:11] <smoser> and we can even ask security team if they're ok with that change SRU to precise
[15:11] <jtv> Just add the maas directories & pidfile?
[15:11] <smoser> yeah. basically like eucalyptus
[15:12] <smoser> at least that is seemingly a designed solution to start off of
[15:12]  * jtv was tempted, so tempted, to jam our own pidfile into /run/eucalyptus
[15:13] <jtv> Actually the pidfile looks like the only one that we really can't circumvent decently.
[15:13] <jtv> There is some wiggle room for our own leases and config files.
[15:13] <smoser> jtv, well we were still running into permission issues on those files
[15:13] <smoser> but we could work around that.
[15:14] <jtv> We could own them.
[15:14] <smoser> well, there were issues.
[15:14] <smoser> at least when i actually tried this.
[15:14] <jtv> The upstart script ensures ownership/permissions of the leases file (and backup).
[15:15] <jtv> I imagine maas installation would take care of ownership/permissions of the config file.
[15:15] <smoser> you're saying running as the isc-dhcp user?
[15:15] <jtv> I was thinking of continuing to run dhcpd as dhcp, yes.
[15:15] <jtv> Make the config file owned by maas, but group dhcp.
[15:16] <smoser> if we can separate and run our own, i really think thats the best.
[15:16] <jtv> Or maas:maas for all I care, as long as dhcpd can read it.
[15:16] <smoser> then you can know that you can just kill it
[15:16] <smoser> when the person pusshes the button "do not run dhcpd"
[15:16] <smoser> its is cleaner separation. and well known path.
[15:16] <jtv> Wait... are you saying running as dhcp is best?  Or that running as maas is best?
[15:17] <smoser> i'm saying maas running/maintaining its own dhcpd is best.
[15:17] <smoser> *not* using the isc-dhcpd
[15:17] <jtv> Oh, yes, that's what I'm coding up.
[15:17] <jtv> Well, it uses the isc-dhcpd *binary* of course.  But not its config etc.
[15:18] <smoser> right.
[15:18] <jtv> But we need at least a new pidfile in the apparmor profile, I think.  Everything else we _could_ keep as-is afaics.
[15:19] <smoser> you could use /ltsp :)
[15:20]  * jtv snarls at smoser
[15:24] <jtv> I guess I'll just add rules for /etc/maas/dhcpd.conf, /var/lib/maas/dhcpd.leases, and _something_ in /run.
=== matsubara is now known as matsubara-lunch
[16:37] <roaksoax> rvba: around?
[16:39] <roaksoax> jtv: still around?
=== matsubara-lunch is now known as matsubara
[16:50] <roaksoax> allenap: are you?
[17:25] <allenap> roaksoax: I'm just passing (it's dinner time here). Email :-/
[17:27] <roaksoax> allenap hehe just left for lunch myself im from the phone
[17:28] <roaksoax> allenap just wantwd to know how to create a db migration to be able to add distro realease support
[17:29] <roaksoax> if theres  template or what
[17:29] <rvba> roaksoax: have a look at HACKING.txt, it's a one line command once you've made the change to the model code.
[17:31] <roaksoax> rvba ok cool thanks
[19:08] <smoser> roaksoax, ok. you around
[19:08] <roaksoax> smoser: nope, this is an automated message
[19:09] <roaksoax> smoser: hehe, what's u?
[19:09] <roaksoax> up*
[19:09] <smoser> ok. so where can i get your dhcp fixed maas?
[19:10] <roaksoax> smoser: it is in the quantal archives, just not on the cd
[19:10] <smoser> ah. ok.
[19:10] <smoser> so we have generally functional dhcpd?
[19:11] <smoser> how?
[19:11] <roaksoax> smoser: maas-provision binary is the one generating the config
[19:11] <roaksoax> so we just needed sudoers access to it
[19:12] <roaksoax> not the best approach obviously, but enough for now until we have the other fixes in place
[19:12] <smoser> roaksoax, ok. i'm gonna try to walk through this, so i'll probably bother you again
[19:14] <roaksoax> alrighty
=== bjf is now known as bjf[afk]
[19:53] <smoser> roaksoax, ok.
[19:53] <smoser> so bug 1044229 is marked as fixed
[19:53] <ubot5> Launchpad bug 1044229 in MAAS "DHCP config doesn't get written unless an inhuman combination of scripts is run" [Critical,Fix released] https://launchpad.net/bugs/1044229
[19:53] <smoser> and that was a dupe of bug 1044061
[19:53] <ubot5> Launchpad bug 1044229 in MAAS "duplicate for #1044061 DHCP config doesn't get written unless an inhuman combination of scripts is run" [Critical,Fix released] https://launchpad.net/bugs/1044229
[19:53] <smoser> so, how do i enable maas dhcp ?
[19:53] <smoser> oh. fun. from the api
[19:54] <smoser> any other way than api and ui ?
[19:54] <smoser> hm..
[19:54] <smoser> and i go to my maas ui and it has 'manage dhcp' but ihave no dhcp process running
[20:03] <smoser> roaksoax, ?
[20:04] <roaksoax> smoser give me a sec plz
[20:04] <smoser> deal
[20:04] <smoser> issue is that dhcpd is not configured to listen on any interfaces
[20:09] <roaksoax> smoser you enable it by installing maad-dhcp
[20:11] <smoser> $ dpkg-query --show maas-dhcp
[20:11] <smoser> maas-dhcp       0.1+bzr971+dfsg-0ubuntu1
[20:11] <smoser> button is highlighed in maas web ui
[20:11] <smoser> maas-dhcp installed
[20:12] <smoser> no isc-dhcp process
[20:12] <smoser> http://paste.ubuntu.com/1189590/
[20:12] <smoser> that is everythign i've done so far
[20:12] <smoser> (except not added daily builds)
[20:12] <smoser> as you told me archive updates was good
[20:14] <smoser> roaksoax, what am i doing wrong?
[20:14] <roaksoax> smoser did you accept thr cresyion of the dhxp betwork
[20:14] <smoser> </dev/null
[20:14] <smoser> so, no
[20:15] <roaksoax> smoser so when you install maas-dhcp and say yes and configure the subnet then it gets enabled
[20:16] <smoser> i just dpkg-reconifgure maas-dhcp
[20:16] <smoser> and isc-dhcp-server still wont run
=== bjf[afk] is now known as bjf
[20:17] <smoser> what am i doing wrong?
[20:18] <matsubara> smoser, roaksoax: I just reproduced the same thing in the lenovo lab
[20:19] <matsubara> installed the latest package, answered the dhcp config questions but isc-dhcp-server keeps respawning saying there's not subnet declaration for eth0, eth1 or eth2
[20:19] <matsubara> and /etc/dhcp/ doesn't have any maas config
[20:20] <smoser> roaksoax, is the version i have listed above sufficient?
[20:20] <smoser> yeah. i have latest package per https://launchpad.net/ubuntu/+source/maas (44 minutes old)
[20:21] <smoser> oh wait. i have 0ubuntu1 and 0ubuntu2 is 44 minutes old
[20:23] <matsubara> I'm using 0.1+bzr971+dfsg-0+972+74~ppa0~precise1 from https://code.launchpad.net/~maas-maintainers/+archive/dailybuilds
[20:23] <matsubara> actually: 0.1+bzr971+dfsg-0+975+74~ppa0~precise1	
[20:23] <matsubara> which is the latest latest crack
[20:23] <matsubara> :-)
[20:24] <smoser> yeah, an di just by hand applied https://launchpadlibrarian.net/114878785/maas_0.1%2Bbzr971%2Bdfsg-0ubuntu1_0.1%2Bbzr971%2Bdfsg-0ubuntu2.diff.gz
[20:24] <smoser> to no avail
[20:32] <roaksoax> smoser: ok i'm back
[20:36] <smoser> k
[20:36] <smoser> i can let you in if you want to poke around, but i
[20:36] <smoser> i've basically done nothing other than that pb
[20:40] <roaksoax> smoser: ok so, the first time you install maas-dhcp, if you configure it, and dhcp is disabled, then it will be enabled
[20:40] <smoser> so what are you saying ?
[20:40] <smoser> its enabled.
[20:40] <smoser> thats fine.
[20:40] <smoser> it doesnt run
[20:40] <smoser> or do anything
[20:40] <smoser> thats not.
[20:41] <roaksoax> smoser: right, but is it enabled on the WebUI?
[20:41] <smoser> yes
[20:41] <roaksoax> smoser: and no config file in /etc/dhcp/dhcpd.conf?
[20:41] <roaksoax> smoser: have you rebooted the machine?
[20:41] <roaksoax> err
[20:41] <roaksoax> i mean, restart apache2?
[20:41] <roaksoax> or pserv or celery?
[20:42] <smoser> well, /etc/dhcp/dhcpd.conf exists. as ait always did.
[20:42] <roaksoax> smoser: right, but maas should have written a config to it
[20:42] <smoser> i did for p in celery pserv txlongpoll; do sudo restart maas-$p; done
[20:42] <smoser> and have actually rebooted since installing maas.
[20:42] <roaksoax> let me see
[20:43] <smoser> ubuntu@10.55.60.167
[20:44] <smoser> [2012-09-06 20:44:27,803: INFO/PoolWorker-3] Not sending DHCP leases to server: not all required knowledge received from server yet.  Missing: api_credentials, maas_url, nodegroup_name
[20:45] <roaksoax> smoser: Version: 0.1+bzr971+dfsg-0ubuntu1
[20:45] <roaksoax> that's the reason
[20:45] <roaksoax> it is not ubuntu2
[20:46] <matsubara> roaksoax, I get the same behaviour (not the same log entry though) on 0.1+bzr971+dfsg-0+975+74~ppa0~precise1
[20:46] <roaksoax> matsubara: the fis is on packaging, not on upstream
[20:47] <roaksoax> s/fis/fix
[20:47] <matsubara> ah ok
[20:48] <smoser> roaksoax, i manually added the sudoers
[20:48] <matsubara> what's the package revno I should be using to build with?
[20:48] <smoser> and restarted since then
[20:48] <roaksoax> smoser: that should work then
[20:48] <smoser> you can look.
[20:49] <smoser> $ sudo cat /etc/sudoers.d/99-maas-sudoers
[20:49] <smoser> maas ALL= NOPASSWD: /usr/sbin/service isc-dhcp-server restart
[20:49] <smoser> maas ALL= NOPASSWD: /usr/sbin/maas-provision
[20:49] <roaksoax> matsubara: the release ubuntu2
[20:49] <roaksoax> matsubara: 1 before last one i think
[20:50] <roaksoax> smoser: disable/enable from the web ui
[20:51] <smoser> $ ls -altr /etc/dhcp/dhcpd.conf
[20:51] <smoser> -rw-r--r-- 1 root root 3602 Jul 10 21:29 /etc/dhcp/dhcpd.conf
[20:51] <roaksoax> smoser: lket me check locally first as network is crappy
[20:51] <roaksoax> again
[20:51] <smoser> (Jul 10). no dice
[20:54] <roaksoax> smoser: is DNS enabled?
[20:55] <smoser> i have 2 nice check boxes checked
[20:55] <smoser> "Enable Dns", "Manage DHCP".  They're really pretty, and orange.
[21:01] <roaksoax> smoser:     return self.run(*args, **kwargs)
[21:01] <roaksoax>   File "/usr/lib/python2.7/dist-packages/provisioningserver/tasks.py", line 322, in restart_dhcp_server
[21:01] <roaksoax>     check_call(['sudo', 'service', 'isc-dhcp-server', 'restart'])
[21:01] <roaksoax>   File "/usr/lib/python2.7/subprocess.py", line 511, in check_call
[21:01] <roaksoax>     raise CalledProcessError(retcode, cmd)
[21:01] <roaksoax> CalledProcessError: CalledProcessError
[21:01] <roaksoax> weird
[21:02] <smoser> where do you see that?
[21:02] <smoser> duh.
[21:02] <smoser> not wierd
[21:02] <smoser> "sudo service"
[21:02] <smoser> maas can't sudo
[21:02] <roaksoax> yeah
[21:02] <roaksoax> which is weird
[21:03] <roaksoax> smoser: and magically, it now works
[21:03] <smoser> it can though
[21:04] <smoser> it is in /etc/sudoers.d/
[21:04] <smoser> for maas
[21:04] <smoser> what magically works ?
[21:04] <roaksoax> smoser:
[21:04] <roaksoax> smoser: DHCP config was written now
[21:05] <smoser> /etc/dhcp/dhcpd.conf ?
[21:05] <smoser> on my system?
[21:05] <roaksoax> smoser: http://paste.ubuntu.com/1189688/
[21:05] <roaksoax> smoser: on my test env
[21:05] <roaksoax> let me access yours
[21:05] <smoser> ubuntu@10.55.60.167
[21:07] <roaksoax> smoser: can you disable/enable dhcp config again please
[21:07] <roaksoax> from maas webui
[21:08] <smoser> sure
[21:08] <smoser> disabled
[21:09] <smoser> enabled
[21:09] <roaksoax> smoser: so just did a dpkg-reconfigure maas-dhcp and it worked
[21:10] <smoser> hm..
[21:11] <roaksoax> smoser: seems to be (wild guess) that when maas gets installed (maas-dhcp really) it tries to create the DHCP database, and enables it (that's why it is enabled on webui). However, since the creation of the dhcpd config file fails (because maas-provision not in sudoers) the dhcp client network doesn't become permanent
[21:11] <roaksoax> so when we add maas-provision to sudoers
[21:11] <roaksoax> and dpkg-reocnfigure maas-dhcp
[21:11] <roaksoax> it success on creating
[21:11] <roaksoax> hence the network is created
[21:11] <smoser> i will check your theory
[21:12] <roaksoax> cool
[21:12]  * roaksoax will try to finish the quantla support
[21:15] <smoser> hm..
[21:15] <smoser> it seems to have worked.
[21:15] <smoser> although i think i'd done that before
[21:15] <smoser> where did you see the stack trace you showed above?
[21:16] <roaksoax> smoser: celery log
[21:16] <roaksoax> /var/log/maas/celery.log
[21:17] <smoser> hm.. i never saw that htere.
[21:19] <smoser> matsubara, could you open a bug based on the above?
[21:20] <roaksoax> smoser: there's  no bug really, it is fixed
[21:20] <roaksoax> smoser: the problem ois that it has not been released
[21:20] <roaksoax> in the archives
[21:21] <roaksoax> smoser: https://launchpad.net/ubuntu/+source/maas/0.1+bzr971+dfsg-0ubuntu2
[21:22] <smoser> http://paste.ubuntu.com/1189725/
[21:22] <smoser> roaksoax, ^
[21:22] <smoser> file gets written now, but it is bad
[21:23] <roaksoax> smoser: isn't that wrong configuration
[21:24] <roaksoax> smoser: ah yes, it is badupstream side
[21:24] <smoser> http://paste.ubuntu.com/1189729/
[21:24] <matsubara> smoser, roaksoax I think there's another bug. the dhcp config is written but next-server is set to 127.0.0.1, is that correct?
[21:24] <smoser> right.
[21:24] <smoser> i was going to point that out
[21:24] <smoser> ok
[21:24]  * smoser has to go now
[21:24] <roaksoax> matsubara: *and* I think there's another issue
[21:24] <roaksoax> subnet 192.168.1.5 netmask 255.255.255.0
[21:25] <roaksoax> that should be the network address not the starting range
[21:25] <roaksoax> maas-provision asks for starting range
[21:25] <roaksoax> and should probably calculate the network address
[21:25] <matsubara> roaksoax, this is the config the package wrote for me: https://pastebin.canonical.com/73987/
[21:27] <matsubara> roaksoax, this https://code.launchpad.net/~maas-maintainers/maas/packaging.precise has the latest fix you mention that's included in ubuntu2 right? My package was built from that source
[21:27] <roaksoax> matsubara: try dpkg-reconfigure maas
[21:28] <matsubara> roaksoax, ok. it offered to change the MAAS pxe address.
[21:29] <roaksoax> matsubara: err i meant maas-dhcp
[21:29] <roaksoax> matsubara: htat's a bug for sure when it tells next-server
[21:29] <roaksoax> or mabe not as it bings to localhost
[21:29] <roaksoax> we;ll have to do some real pxde boot testing on that
[21:30] <matsubara> roaksoax, ok, reconfigured the maas-dhcp package, it asked me the same questions asked when I installed and the dhcpd.conf still have next-server as 127.0.0.1
[21:31] <roaksoax> matsubara: that's a bug for sure
[21:31] <matsubara> roaksoax, that's what I'm doing :) when I pxe boot, the node gets a TFTP open timeout
[21:31] <roaksoax> yeah
[21:32] <matsubara> roaksoax, I'm going to file it, is it in the packaging or upstream?
[21:32] <roaksoax> matsubara: upstream
[21:37] <matsubara> https://bugs.launchpad.net/maas/+bug/1047061
[21:37] <ubot5> Ubuntu bug 1047061 in MAAS "dhcpd.conf next-server set to 127.0.0.1" [Undecided,New]
[21:39] <roaksoax> cool
[21:39] <roaksoax> anyways
[21:39] <roaksoax> im off
[21:39] <roaksoax> later
[21:44] <matsubara> roaksoax, have a good one. Thanks!