/srv/irclogs.ubuntu.com/2012/11/21/#maas.txt

bigjoolsroaksoax: I approved your packaging change00:52
bigjoolscan I land it as-is?00:53
=== rnbrady_ is now known as rnbrady
roaksoaxbigjools: cool thanks01:10
bigjoolsroaksoax: actually01:10
bigjoolsroaksoax: wait01:10
bigjoolsI have got so many branches I am getting them mixed up01:11
roaksoaxbigjools: so I created a packaging.precise.sru which is what was in quantal at the time, plus your merges01:11
roaksoaxbigjools: or your change to the upstart job01:11
roaksoaxbigjools: i'll get that updated :)01:11
bigjoolswe have not backported the celery import-pxe-files01:11
roaksoaxbigjools: ok, no harm since it was only a 1 line addition01:12
roaksoaxto the sudoers file for maas01:12
bigjoolsroaksoax: no I mean your https://code.launchpad.net/~andreserl/maas/quantal_packaging_updates/+merge/13526401:12
bigjoolsit was more than that, 167 lines of diff :)01:12
roaksoaxbigjools: the change for that is: debian/extras/99-maas-sudoers01:12
roaksoaxbigjools: the rest, is for maas-cluster-controller shipping maas-import-pxe-files and storing the images01:13
bigjoolsroaksoax: none of it is needed01:14
bigjoolsI think01:14
bigjoolsgrar, let me check again01:15
roaksoaxbigjools: hold on, isn't bug #1068843 the one one which the cluster controller has to have the images?01:15
ubot5Launchpad bug 1068843 in maas (Ubuntu Raring) "maas-cluster-controller doesn't have images for provisioning" [High,Triaged] https://launchpad.net/bugs/106884301:15
roaksoaxbigjools: so that bug,which i see was backported to the stabilkization branch is where the images are no longer on the region controller and are on the cluster controller01:16
bigjoolsroaksoax: right right01:16
bigjoolsI am getting two changes mixed up01:16
roaksoaxbigjools: the thing for celery to work, was simply adding permission for the maas user to run maas-import-pxe-files01:16
roaksoaxbigjools: which is a 1 line change01:16
bigjoolsroaksoax: yup :)01:17
roaksoaxbigjools: ok, so now01:18
roaksoaxbigjools: i have updated it01:18
roaksoax:)01:18
roaksoaxbigjools: now, I had to rebase the python-django package because a securoity fix landed in archives01:18
roaksoaxbigjools: and your changes needed to be applied on top of that package01:18
roaksoaxbigjools: now, It would be great if you could open a bug report for each of those patches01:19
bigjoolsroaksoax: you already did it? I was about to do it01:19
bigjools:)01:19
roaksoaxso i can reference the changelog and SRU the package01:19
bigjoolsI will file01:19
bigjoolswhere is your precise packaging branch?  I made a bunch of changes just in the PPA01:20
bigjools(for maas)01:20
roaksoaxbigjools: awesome, assign them to me and I'll take care of the rest01:20
bigjoolscoolio01:20
roaksoaxbigjools: lp:~maas-maintainers/maas/packaging.precise.sru01:21
roaksoaxbigjools: this is the only change i made of top for the packaging: http://bazaar.launchpad.net/~maas-maintainers/maas/packaging.precise.sru/revision/14601:22
roaksoaxin comparison to the quantal one01:22
roaksoaxbigjools: in terms on packaging I didn't see any other change01:23
bigjoolsroaksoax: ok I have a *bunch* of changes, it might be best if I just blow your branch away and replace it with mine01:24
* bigjools diffs01:24
roaksoaxbigjools: sure, branch the quantal with the recent changes you just approved and put them on top01:24
roaksoaxbigjools: that way I can make sure what differs from quantal01:24
bigjoolsI branched the old precise packaging and changed on top of that01:25
bigjoolssince that is the branch that we really want to use, right?01:25
roaksoaxbigjools: uhmmm nope01:25
bigjoolswhut?01:25
roaksoaxbigjools:  the quantal branch updates precise -> quantal right?01:26
roaksoaxbigjools: the quantal version is going to be the same as precise01:26
bigjoolsthe code is the same, the packaging is a fair bit different now01:26
roaksoaxbigjools: it shouldn't be01:26
bigjoolsbut I see why you're approaching it this way01:26
bigjoolslet me diff them, hang on01:27
roaksoaxbigjools: note that when you backport, you use the same package as ubuntu+1, + any singularities that you need to do in that particula release01:28
roaksoaxbigjools: in our case, we are SRU'ing a whole release01:28
bigjoolsok01:28
roaksoaxso the packaging should be the same + changes for precise01:28
roaksoaxbigjools: cause the upgrade path is going to be the same01:28
bigjoolswell for reference, here's the diff from my your sru packaging to my sru packaging http://pastebin.ubuntu.com/1373861/01:29
roaksoaxbigjools: yeah, too much complication :)01:30
roaksoaxs/too much complication/too complicated/01:30
bigjoolsI have an equally big diff to the quantal branch01:30
bigjoolslet's see what I can do01:30
roaksoaxbigjools: the one iuploaded in the PPA, only seemed to have the upstart changes as packaging changes01:31
bigjoolsI have changelog and upstart01:32
roaksoaxbigjools: right, I merged your changelog entry for the upstart change01:32
roaksoaxbigjools: and i added all the biuglist we are closing01:32
roaksoaxbigjools: which you partially had01:32
roaksoaxbigjools: there should not be any more changes AFAIK01:32
bigjoolsindeed01:32
roaksoaxbigjools: ok so I will rebase packaging.precise.sru with latest fixes01:33
bigjoolsroaksoax: looks like your branch is up to date then01:33
bigjoolsexcellenbt01:35
bigjoolsroaksoax: did you rebase the django package already?01:35
roaksoaxbigjools: yes01:35
bigjoolsroaksoax: awesome01:35
roaksoax:)01:36
roaksoaxbigjools: alright, I hope that tomorrow i can at least upload yui3, python-tx-tftp, and django01:36
bigjools\o/01:36
bigjoolsto quantal and precise?01:36
roaksoaxyui3, django to precise01:36
roaksoaxand python-tx-tftp to quantal, and once accepted to precise01:37
bigjoolsnice!01:37
* bigjools files bugs01:37
bigjoolsroaksoax: 1st one https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/108138801:42
ubot5Ubuntu bug 1081388 in python-django (Ubuntu) "Backport prefetch_related from 1.4" [Undecided,New]01:42
roaksoaxbigjools: could you also please explain what it does, or "fixes" maas problem01:43
bigjoolsroaksoax: any better?01:47
bigjoolsroaksoax: 2nd https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/108139101:49
bigjoolsone more to go01:49
ubot5Ubuntu bug 1081391 in python-django (Ubuntu) "Backport GenericIPAddressfield from 1.4" [Undecided,New]01:49
bigjoolsroaksoax: https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/108139201:52
ubot5Ubuntu bug 1081392 in python-django (Ubuntu) "Include upstream bug 15496" [Undecided,New]01:52
bigjoolsI can attach patches for reference if you need01:52
roaksoaxbigjools: cool thanks01:52
roaksoaxbigjools: no not really01:52
bigjoolsok01:52
roaksoaxi'll take care of them tomorrow01:53
roaksoaxnow, I'm off01:53
roaksoaxhave a good day :)01:53
bigjoolsroaksoax: excellent, thank you.  Have a good evening!01:55
AskUbuntuAdding nodes to MAAS server | http://askubuntu.com/q/22004904:49
Nafallohi09:43
Nafallowhere in maas can I define my own preseeds? :-)09:43
NafalloI need to specify an http proxy for apt in my environment.09:43
bigjoolsNafallo: yes, /etc/maas/09:52
bigjoolsedit existing one09:52
Nafallocan't see one in there?09:56
NafalloI'm using Ubuntu 12.10 btw.09:56
Nafalloso maas=0.1+bzr1269+dfsg-0ubuntu109:56
bigjoolsNafallo: I have to dash, rvba should be able to point you to the right place09:57
bigjoolsbut 12.10 already points a proxy at the squid-deb-proxy on the region controller09:57
* bigjools outta here09:58
rvbaNafallo: the preseeds are in /usr/share/maas/preseeds/09:58
rvbaNafallo: like bigjools said, you'll see that /usr/share/maas/preseeds/generic already sets the proxy to be the squid-deb-proxy on the region controller09:59
Nafallohmm. I guess the alternative is to point squid-deb-proxy to use a proxy then? :-P09:59
Nafallocause my maas is on rfc1918 space, and I'm not planning to NAT it.09:59
rvbaYeah, you can configure that proxy to use a parent proxy.10:00
NafalloI think that will be the best option then, cause currently the machines just time out :-)10:01
Nafallothanks. I'll test that :-)10:01
=== pcarrier_ is now known as pcarrier
=== matsubara-afk is now known as matsubara
=== allenap` is now known as allenap
=== matsubara is now known as matsubara-lunch
rvbaroaksoax: Hi Andres.  Quick question for you, what is the format of the generated /etc/maas/maas_cluster.conf file?  Right now we have only one value in there (MAAS_URL=http://10.98.0.90/MAAS).  Is that guaranteed that it will be key=value\nkey2=value2?16:23
roaksoaxrvba: if you make it so yes16:25
rvbaroaksoax: ok, apparently we simply populate this file manually in the packaging so I've got my answer.16:26
roaksoaxrvba: yep, so you'd need to add a new /sed/ in order to replace the second key=value16:26
rvbaroaksoax: ok, got it,ta16:26
roaksoaxrvba: but that file already comes with one key value, and the value for that key is being replaced16:26
rvbaroaksoax: can you please triage this (pretty critical if you ask me)?  https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1081212 allenap or I will work on a fix for it.17:01
ubot5Ubuntu bug 1081212 in maas (Ubuntu) "The address of the API in pserv.conf (tftp/generator) is http://localhost/MAAS/api/1.0/pxeconfig/" [Undecided,New]17:02
roaksoaxrvba: is this bug present in the archives?17:03
rvbaroaksoax: yes17:03
roaksoaxdone17:04
rvbata17:04
=== matsubara-lunch is now known as matsubara
allenaproaksoax: Could you do the same for bug 1081660 please?17:16
ubot5Launchpad bug 1081660 in maas-enlist (Ubuntu) "If maas-enlist fails to reach a DNS server, the node will be named ";; connection timed out; no servers could be reached"" [Undecided,New] https://launchpad.net/bugs/108166017:16
roaksoaxallenap: sure thing17:16
allenapTa.17:16
roaksoaxallenap: weird, that bug didn't happen before17:17
=== andreas__ is now known as ahasenack
roaksoaxbigjools: howdy! is bug #1081392 not fixed in 1.4/quantal?22:36
ubot5Launchpad bug 1081392 in python-django (Ubuntu) "Include upstream fix for bug 15496" [Undecided,New] https://launchpad.net/bugs/108139222:36
bigjoolsroaksoax: hi22:45
bigjoolsroaksoax: it's already in quantal22:45
bigjoolsI only noticed the bug on precise22:45
roaksoaxbigjools: ok cool22:49
bigjoolsroaksoax: note that this particular fix is already in upstream 1.3, but I did a patch as that saves worrying about bringing in many changes if upstream is refreshed22:53
roaksoaxbigjools: ok cool22:54
roaksoaxbigjools: yeah we shouldn't have issues for this22:54
bigjoolsroaksoax: did you see https://bugs.launchpad.net/bugs/108166023:18
ubot5Ubuntu bug 1081660 in maas-enlist (Ubuntu) "If maas-enlist fails to reach a DNS server, the node will be named ";; connection timed out; no servers could be reached"" [Critical,Triaged]23:19
bigjoolsah you did, you triaged it :)23:19
roaksoaxbigjools: yeah, which i found pretty werid23:28
roaksoaxcause that error never appeared before23:29
roaksoaxso unless someone changed something23:29
roaksoaxbigjools: this is how it handles it: ip=$(ifconfig eth0 | awk '$1 == "inet" { sub("addr:","",$2); print $2; }') && [ -n "${ip}" ] && host=$(dig +short -x $ip)  && host=${host%.}23:30
* bigjools blinks23:31
bigjoolsroaksoax: I expect it's a genuine timeout and dig is returning that string23:32
* bigjools reconnecting23:32
roaksoaxbigjools: yeah that might indeed be the issue, though I've never seen it before :/23:35
roaksoaxi can't reproduce it23:36
bigjoolsroaksoax: sigstop the dns server?23:42
bigjoolsbtw I copied all the packages from experimental to testing23:44

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!