[17:43] <newell_> When running the development code using "make run" and then subsequently creating and saving a new managed interface for a cluster controller, I don't see where dhcpd.conf is being written.  It is not put in /etc/maas/dhcpd.conf and I also cannot find it in my local repository.
[17:43] <newell_> Does anyone know where this is written?
[17:46] <newell_> I was manually trying to reduplicate bug #1283106
[17:48] <newell_> I am new to MAAS so apologizes if my question seem rudimentary
[17:49] <newell_> s/seem/seems
[23:02] <bigjools> newell_: still there?
[23:03] <bigjools> newell_: people are sprinting this week so will be unresponsive
[23:04] <newell_> bigjools, I am here
[23:04] <newell_> Okay do you think that anyone would be able to help or more likely that I will need to wait?
[23:05] <bigjools> newell_: I can help
[23:05] <bigjools> I can't remember where it writes the file in dev mode, so let's have a look
[23:05] <newell_> k, thanks
[23:05] <bigjools> it might get written under the local etc/
[23:06] <newell_> I did a 'find' but couldn't find it
[23:06] <bigjools> but check the celery log file to see if the job is getting kicked off
[23:07] <newell_> I guess one of the main things I am confused on is that the bug just says two managed interfaces that have the same subnet
[23:08] <newell_> so that would imply that 10.0.1.0/255.255.255.0 and 192.168.3.0/255.255.255.0 would cause this error.  Maybe I am inferring this incorrectly.
[23:09] <newell_> but I would think that the two subnet ranges I just wrote above shouldn't conflict with one another
[23:09] <newell_> I guess I could ping the bug writer but was hoping to figure it out on my own
[23:15] <newell_> bigjools, I will take a look at celery logs when I get a chance
[23:16] <bigjools> newell_: it's overlapping address ranges I think, remind me of the bug again?
[23:17] <newell_> #1283106
[23:17] <newell_> bug #1283106
[23:17] <bigjools> bug 1283106
[23:17] <bigjools> heh
[23:18] <bigjools> newell_: right, that is what it is, overlapping ranges, which makes dhcpd barf
[23:18] <bigjools> it's a trivial piece of validation in the form
[23:18] <newell_> bigjools, well there is already a bunch of code in forms.py and test_forms.py
[23:18] <newell_> that do just this
[23:18] <bigjools> yeah they will be validating related stuff
[23:18] <bigjools> so maybe there is a bug or maybe it is not doing it
[23:19] <newell_> okay whomever submitted the bug... used the language of two managed interfaces with the same subnet masks
[23:19] <newell_> so didn't know if we should look for just that or if it has to be overlapping ranges
[23:19] <bigjools> yeah, he's French :)
[23:20]  * bigjools waves at rvba
[23:20] <newell_> I am just trying to understand exactly what needs to be executed
[23:20] <bigjools> I'll summarise:
[23:21] <bigjools> when submitting the form to add/edit an interface it needs to iterate over the existing interfaces and check that the defined range does not overlap with each
[23:22] <newell_> Okay I am very familiar with that code
[23:22] <newell_> I will have to see why it is failing then
[23:24]  * newell_ was just confused by what was said 
[23:24] <newell_> in the report ;)
[23:27] <bigjools> ok
[23:27] <bigjools> well my suggestion is to first write a test that re-creates the problem
[23:27] <bigjools> then it becomes easier to debug
[23:27] <bigjools> and passes when you fixed the bug
[23:32] <newell_> bigjools, yeah I actually wrote my own forms class and test code that was doing it just for the subnet masks (a way for me to play around with everything etc.)  So it shouldn't be an issue now that I know it is just for overlapping ranges.