/srv/irclogs.ubuntu.com/2012/10/09/#maas.txt

flacostebigjools: i'm in the hang out00:01
bigjoolsflacoste: hi - I don't see an invitation00:02
bigjoolsnow I do00:02
flacostebigjools: it was the hang out linked to the event00:02
roaksoaxbigjools: right, but my point was that when you only install maas-cluster-controller you need to tell the MAAS URL too right?00:03
=== matsubara is now known as matsubara-afk
bigjoolshi jam05:00
jamhi bigjools06:41
jam(I was around earlier, but had to run some errands) anything you need?06:41
bigjoolsjam: no, just saying hi :)06:42
bigjoolswell cool, commissioning a new and I see hardware info appearing :)06:56
bigjoolsnew node*{06:56
jambigjools: yay06:59
bigjoolssadly the ipmi detection is not so good, it thinks the BMC has an ip address of  0.0.0.007:11
jambigjools: that just means it is accessible from everywhere, right? :)07:20
bigjoolsjam: that's *one* way of looking at it07:21
allenapMorning.08:24
rvbaMorning allenap.08:24
jambigjools: I think I might know how we've had test suite failures in Jenkins.09:01
jamIt appears that if you submit a branch, and it fails the test suite09:01
jamSubmitting it again just accepts it (without running the tests)09:02
bigjools!09:02
bigjoolsI have done that in the past and it didn't land though09:02
jamI could be wrong, but I just resubmitted to MAAS lander, and I think I can show it failing here.09:02
jambigjools: https://code.launchpad.net/~jameinel/maas/allow-json/+merge/12851209:02
jamthe first failure gave me the 40409:02
jamso I just resubmit hoping to get an actual error I can work on.09:02
jamBut this time, magic it succeeded.09:03
bigjoolshummm09:03
jammgz: http://stackoverflow.com/questions/5907575/how-do-i-use-pagination-with-django-class-based-generic-listviews09:06
allenapjam: Gah, can't import django in provisioningserver :-/09:16
jamallenap: I have a fix re-submitted for it.09:17
jambut see above09:17
allenapI nearly added "because Django is an nearly unmitigated pos", but I bit my tongue.09:17
jamMaas decided to land my branch again, when I retried because the first time gave me just a 40409:17
mgzjam: I have fled upstairs, can mumble from here if we want though09:17
jammgz: well, I'll be chewing for a bit longer, then I'll poke you for mumble :)09:18
mgz^and I followed your bad example and told the lander to shut up and try again09:18
bigjoolsallenap: lol09:19
jamallenap: so if you check my latest 'lp:~jameinel/maas/allow-json' I should have fixed the import issues. However, Maas just rejected my change again, and I can't get the context because 40409:21
allenapGah.09:21
jamI'm running a full make check to be sure09:21
jamI can just land on trunk, and see if that resolves things?09:22
jam(and why is it that console output used to work, but is now just always giving 404...)09:22
allenapThis is annoying. I guess land on trunk. rvba, do you know if/how we can turn off the gated landings in Tarmac, for a while at least?09:23
rvbaallenap: no idea, maybe Diogo documented that somewhere but I doubt it.09:24
allenapWe just walk round the back then.09:24
jamallenap: it is possible that it was passing for me because I didn't have the latest trunk. I'll make sure to grab it and check one more time.09:25
allenapjam: I'm running it too.09:25
bigjoolsit'll be in the tarmac conf09:25
rvbajam: the "Private Jenkins URL" works.09:26
* bigjools putting kids to bed, back in 2009:26
jamrvba: I can get to the public jenkins, it just doesn't have the new job (172) that claims to be failing.09:26
jamAnd I can't get to the private jenkins09:26
jamallenap: I do see 2 failures in trunk this time, so maybe I can squash them.09:27
allenapjam: You need the test lab VPN config to get to the private URL, see https://wiki.canonical.com/Launchpad/QA/MAASLenovoLab09:27
rvbajam: like Gavin said :)09:28
jamallenap, rvba: Technically, vpn's are illegal in Dubai, because they get around the content restrictions. but I'll probably give it a shot.09:28
jamallenap: so the tests failing in trunk are the 'maascli' ones.09:29
jamnot mine.09:29
jamso I'll land my patch to fix my own broken bits.09:29
jamand then we can look to fix the maascli ones.09:29
mgzdon't get yourself hauled off to sit in content prison...09:30
jamallenap: 'bin/test.maas maascli.tests.test_integration' has 2 failing tests for me.09:30
jammgz: is that 'conTENT' or 'CONtent' ?09:31
jam:)09:31
rvbajam: can you try moving away ~/.maascli.db and run the tests?09:32
rvbajam: we have a bug about the tests using that file…09:32
jamallenap: the maascli tests are failing because of 'resources=description['resources']' not existing.09:32
jamrbasak: confirmed09:33
jamLooks like it might be happening in Jenkins as  well?09:33
rvbajam: yeah, that's bug 1063721.09:33
ubot5Launchpad bug 1063721 in MAAS "The CLI tests depend on the content of ~/.maascli.db." [Low,Triaged] https://launchpad.net/bugs/106372109:33
allenapjam: Yeah, the ~/.maascli.db is probably causing that. Also, maascli tests should be run with bin/test.maascli.09:46
jamallenap: they still fail, but I see them being run with both09:47
jamas in running 'make check' they run under bin/test.maas from what I can tell, and they fail here.09:47
jamallenap: if they shouldn't run under 'bin/test.maas' I think you need an --exclude=maascli in bin/test.maas09:48
jam(which comes from buildout somehow)09:48
allenapjam: I'll fix that later.09:49
allenapjam: I get a clean run here, for make check with allow-json.09:49
jamallenap: yeah, other than the maascli stuff, I have a clean run. So I landed it on trunk.09:51
jammgz: poke for great mumbling10:07
jamallenap: maas lander is still failing follow up branches without any context10:07
mgzthird time lucky10:08
mgzmaas lander let the search change through10:09
jammgz: https://jenkins.qa.ubuntu.com/job/maas-merger-quantal/ only shows up to 169, not 170-175 which are the ones that are failing.10:09
jammgz: make harness10:27
jamfrom maasserver.models import NodeGroup10:28
jamng = NodeGroup.objects.ensure_master()10:28
jamfrom maasserver.testing.factory import factory10:28
jamfor i in range(?): factory.make_node(nodegroup10:28
jam=ng)10:28
jamallenap: I'm getting "twistd.pserv Unknown command: maas-pserv" any idea how to fix that?10:41
allenapjam: What are you trying to do?10:55
jamallenap: 'make run'10:56
jamhowever, I think it is because I still had cruft leftover from failing to uninstall maas10:56
jamSo maas-txlongpoll was running in the background10:56
jamrather than just the dev one.10:56
allenapjam: Have you moved the directory or anything that might confuse buildout? Check bin/twistd.pserv to see if there's anything obviously wrong there.10:58
jamallenap: still getting the same error after stopping the other.10:58
jamallenap: Also, this is after doing 'make distclean' which should rebuild those things, right?10:59
allenapjam: Yeah, it ought to. The maas-pserv plugin is picked up from twisted/plugins/maasps.py, so make sure that the root of the tree is mentioned in bin/twisted.pserv.11:05
allenaps/twisted/twistd/11:05
jamallenap: it is.11:06
allenapBugger.11:06
jamroot, etc, src, contrib/python-tx-tftp11:06
jamallenap: so the actual failure is probably 'no module named tftp.backend'11:07
jamthe massps.py is suppressing the other import failure11:07
allenapjam: That should be in contrib/python-tx-tftp.11:07
jamwhich is in the twistd.pserv path11:08
allenapjam: Can you run through twistd.pserv statement-by-statement and then try importing tftp.backend?11:10
jamallenap: if I insert a PDB at the __name__ == '__main__' portion, I can manually import twisted.plugins.maasps and see that it has the ProvisioningServerMaker class in the namespace11:16
jamallenap: however it still tells me 'unknown command maas-pserv'11:16
jamavailabe commands are ampq-longpoll, conch, dns, ftp inetd, mail, manhole, news, portforward, procmon, socks, telnet, tftp, txlongpoll, web, words, xmpp-router.11:17
jamI *do* see 171 unhandled messages in the 'celery' queue... :(11:19
allenapjam: I can't think of another reason why it wouldn't work, but that's obviously a failure of my imagination. I'll keep thinking. If you discover the reason, let me know?11:25
jtvAnybody up for a review of some shell code?  It's not much: https://code.launchpad.net/~jtv/maas/bug-1050033/+merge/12868511:29
bigjoolsjtv: sure11:31
jtvThanks.11:31
bigjoolsjtv: just one point - the args are the wrong way around compared to the more traditional order :)11:34
jtvDepends on the example you pick!  Unix tradition is: if one positional argument takes just one value, and another may be given multiple times, the one argument goes first.11:35
jtvInsert long discussion here about whether ln's argument order is intuitive.  :)11:35
jtvBut yes, cp and mv do put the destination last.11:35
jtvI'll change it.11:38
rbasakMost of the time I use ln, I specify the destination only. It'd be confusing if ln were the other way round11:38
bigjoolsdepends on how you think about which is the destination11:40
jtvExactly.  That's what I hate about it.11:40
jtvNow you don't just have to remember argument order, you have to remember which of several obvious ways to think about the whole thing!11:41
bigjoolsI just remember original file :)11:41
* jtv wishes once again he'd pushed his openssh patch upstream half a decade ago, so he could stop it complaining about host keys for dynamic IP addresses changing all the time11:48
bigjoolsthe 99-temporary-fix-constraints.patch in packaging now needs removing11:58
bigjoolspackage is ftbfs11:58
allenapmgz: Got time for a 1 minute review of https://code.launchpad.net/~allenap/maas/maas-cli-explain-after-login/+merge/128693?11:59
mgzallenap: sure12:01
allenapTa.12:01
mgzprint() is weird12:05
allenapmgz: Why?12:06
mgzputting a bare print before and after is not how I'd do it, but I tend to the (equally weird) print s.join("\n\n")12:08
allenapmgz: It's irrelevant here, because the target is Ubuntu only, but I avoid that so that line-endings are sorted out by Python, but in that I may be misguided.12:11
mgzyou're pretty much always printing to a file opened in text mode, so they get translated12:12
mgz(redirecting stdout to something that has been opened as binary or hacking the stream properties is uncommon)12:13
smoserjtv, you should not care about the extension of a initrd.  it never should have been changed.12:51
smoserthe 'gzip' executable is not at all involved in decompression of an initramfs.12:51
smoserso, dont worry about it. rename it as you need.12:52
allenaprvba, jtv: Anything in flight that needs to be landed today?13:13
rvbaallenap: no.13:15
jamallenap: as near as I can tell, twisted/plugins/maasps.py is just not getting imported. Is there a way to tell what is going on? I guess just stepping from the startup?13:38
jammgz: poke13:49
flacosteroaksoax: latest daily builds is uninstallable for smoser: http://paste.ubuntu.com/1269262/13:50
rvbaflacoste: for me too :/.  I just tested it on a branch new canonistack instance.13:50
rvbabrand*13:50
smoserroaksoax, seems rooted in this: http://paste.ubuntu.com/1269276/13:51
rbasaksmoser: I have the bug reproduced and ready for a patch, based on my morning's daily (0.1+bzr1226+dfsg-0+1226+124~ppa0~quantal1) rather than current.13:51
jamallenap: I think I found the problem... after uninstalling the package 'maas' it left a *stale* /usr/lib/python2.7/dist-packages/twisted/plugins/maasps.pyc file13:52
smoserso, i would suggest that right now, archive install of freeipmi-tools is uninstallable13:53
Davieysmoser: I did an upload earlier13:54
DavieyMaybe it's still being published13:54
allenapjam: Ach, that's bad. I guess that's a dpkg bug?13:54
Davieycheck which version is apt-cache policy13:54
jamallenap: well, I had to manually mess things up because 'apt-get remove maas' was failing.13:54
jamit was *starting* the services it was trying to remove.13:54
jamand then, failing to remove them.13:54
jamso I might have some things a bit broken here13:54
jamhowever, after fixing *that*, I now have problems wiwth 'maasserver_config' does not exist.13:55
allenapjam: Right. For now we assume it's an anomaly.13:55
allenapOh no :-/13:55
jamthat and 'response.getcode()' tuple object has no attribute 'getcode'13:55
roaksoaxsmoser msybe relsted to being promoted to msin¿13:55
roaksoaxsmoser doko promoted it this morning13:55
jamah, I need to 'make syncdb' to get the db, right?13:58
roaksoaxsmoser is the bug relsted to not being able to commission with console=ttyS0 still present¿14:00
roaksoax?14:00
jamallenap: and it would appear I might have broken start_cluster_controller by changing the return value of MAASClient.post() checking14:00
smoserroaksoax, probably.14:01
smoserhttps://bugs.launchpad.net/maas/+bug/106197714:01
ubot5Ubuntu bug 1061977 in MAAS "Machine fails to commission when console=ttyS0 is present on kernel opts" [Critical,Triaged]14:01
smoseri'm not *totally* opposed to dropping console=ttyS0 from the cmdline14:01
roaksoaxsmoser ok.. so we still need to be able to modify that then in an easy manner14:02
smoseras i have no other work around.14:02
mgzjam: wiggle?14:02
jammgz: just checking how things are going, want to mumble?14:02
mgzsure14:02
roaksoaxsmoser i think we should be able to have an attribute on the node for that14:02
roaksoaxsmoser shouldnt be that hard to hack14:03
bigjoolsroaksoax: yes my machines failed to commission with console=ttyS0 today14:03
bigjoolsalso see the comment above about stale .pyc files left around?14:03
smoserroaksoax, well, the one thing we can fix right now is to remove console=ttyS0.14:04
smoserand i'm not completely opposed to that.14:04
smoseri just think it sucks.14:04
roaksoaxsmoser i think it is important to make it configurable14:04
bigjoolshow does a bmc get at console output?14:05
roaksoaxadding a paramtet shold be a problem really14:05
smoserit all depends.14:05
smoser(how a bmc gets console output)14:05
smosersome bmc will have serial console "SOL"14:05
roaksoaxbidjools you have to configure the bmc and then configure maas to tell what parameters to send14:05
smoserwhich i would think is most common14:05
bigjoolsalso my BMCs are all failing to get a dhcp address, no idea why.  they ignore the dhcpoffer from the server14:05
jamallenap: yay, it wasn't me who broke start_cluster_controller. Someone else changed the dispatcher from using urllib2.urlopen to httplib2.Http()14:05
smoserbut i really have not enough experience on server hardware to make broad generalizations on such a thing.14:06
jamallenap: start_cluster_controller seems to be the only thing that is using 'response' directly after post14:06
roaksoaxbigjools those pyc files .. idk but its definiteky related to the package split as they werent present before the split but i cant figure out whats wrong14:06
bigjoolsroaksoax: bug in postrm not pulling in debhelper?14:07
roaksoaxsmoser in sabdfls cluster i had to odify to ttyS1 but he said he configured that on the bios14:07
smoserso...14:07
roaksoaxbigjools i thought you merged that and it would have taken cre of it14:07
smosermy personal feeling on this right now is to just drop all 'console=' params from the cmdline on intel14:08
smoserunless bigjools or someone says "i can make that configurable via file in /etc/ "right now"'14:08
bigjoolsthere's an open bug about it14:08
jamallenap: so your change to using httplib2.Http so that you could set the insecure flag14:08
roaksoaxi would go for addint the attribute for the node for custom kernel params14:08
jambroke actually all users of dispatch_query14:08
smoserso unless that happens, i think we live with "configurable" meaning 'change .py files'14:08
jambecause it used to return a urllib2 file-like object14:09
smoserbigjools, yes, there is.14:09
jamand it now returns a tuple14:09
jamof response_headers, conte14:09
jamcontent14:09
smoserbug 104450314:09
jamwe don't have tests that exercise the code14:09
ubot5Launchpad bug 1044503 in MAAS "kernel command line is not easily customizable" [High,Triaged] https://launchpad.net/bugs/104450314:09
jambecause all the tests mock out the connection.14:09
jambecause we never run an actuall HTTP server to query against.14:09
jamall of the tags stuff would also show up broken, if we could actually get it running (but we are failing early during startup)14:10
bigjoolsexcept in the test he added for that change... the irony ...14:10
jambigjools: :)14:10
bigjoolsok it's past midnight, I need to sleep14:10
bigjoolsnight all, good luck14:10
jambigjools: sleep well.14:10
* bigjools intends to :)14:10
rvbajam: how could that change break things?  It's just a tiny encapsulation, and http_request still returns the result of http.request()…?14:11
jamrvba: we used to return urllib2.open()14:11
jamwhicgh is a file-like object14:11
jamwith an attribute '.getcode()'14:11
jamrvba: httplib2.Http.request() returns a very different object.14:11
jamnamely, a tuple14:11
rvbaI see.14:11
jamof ({headers}, content)14:11
jamrvba: it only shows up during 'make run' because that is the only time we actually connect to a real server.14:12
jamrvba: so, do we try to update all clients to a new api? try to wrap it in something that looks like a urllib object?14:12
jamrevert the insecure=False change?14:12
rvbaI don't think we can revert that change just like that.14:13
allenapjam: Revert I think.14:13
allenapI only just made the change this morning.14:13
allenapI'll do it.14:13
rvbaAlso, sorry for being thick, but here is the change in question14:13
rvbahttp://paste.ubuntu.com/1269307/14:13
jamallenap: thanks14:13
rvbaWe were using httplib2.Http.request() all along.14:14
jamrvba: wrong code14:14
jamthis is the one allenap did14:14
rvbaOh, you're talking about a different change I guess.14:14
allenaprvba: apiclient, not maascli.14:14
rvbaOk,14:14
rvbak14:14
jamallenap: yeah, I think we can revert it for now, and land it after tomorrow and think about what we want to do with the changes. Long term, you like httplib2 more?14:15
jam(it at least lets you allow self-signed certs, I guess)14:16
allenapjam: I was trying to "upstream" the changes in maascli to apiclient so that the former can properly use the latter. There's an impedance mismatch between apiclient and our Pistonesque API that's been mostly figured out in maascli.14:17
jamallenap: yeah, I think it would be nice to update to something closer14:18
jamand I don't think we need to have incremental reads from urllib214:18
jam(i don't know if we even have incremental there, but it pretends we do)14:18
allenapjam: Care to rubberstamp? https://code.launchpad.net/~allenap/maas/revert-change-to-httplib2-in-apiclient/+merge/12872614:22
jamallenap: done14:23
allenapThanks.14:23
jamallenap: I'm glad I updated to trunk to test stuff today.14:23
allenapjam: Me too :)14:24
=== flacoste changed the topic of #maas to: Final Freeze is today: waiting on upstream fixes for bug 978127| Discussion of upstream development of Ubuntu's Metal as a Service (MAAS) tool | MAAS jenkins: https://jenkins.qa.ubuntu.com/job/maas-trunk/
flacosteroaksoax: any way i can be a bug supervisor for the maas package? so that i can set priority14:30
roaksoaxflacoste: being member of the bugsquad or being a core dev :)14:31
flacostepff14:31
flacostesmoser, roaksoax, Daviey: i'm just going to use a tag to highlight the bug fixed in upstream that aren't in the archive14:33
flacostetoo much hassle to create tasks when i cannot set the priority on it14:33
allenapjam: I've filed bug 1064437 about it.14:33
ubot5Launchpad bug 1064437 in MAAS "The expectations of MAASDispatcher.dispatch_query are not tested" [High,Triaged] https://launchpad.net/bugs/106443714:33
jamallenap: thanks14:33
smoserflacoste, fair enough14:37
roaksoaxflacoste: what trunk rev are we looking to have in the archives today?14:39
jammgz: Vq2fSMwMvLXFuGJJyp:fZE7P5qGvgPSudZ8Hh:ZNqct3Pm8pFGh8mT5DVy8Py8JCtg4NaG14:40
flacosteroaksoax: 1238 is the latest, but we are missing a few bug fixes still14:40
flacosteroaksoax: so something like 1241 probably14:40
roaksoaxflacoste: ok I think we have until 21:00 UTC so we still have a few hours, but i'd require to do some testing first14:41
flacosteroaksoax: 1239 -> revert of allenap revision breaking start_maas_cluster14:41
roaksoaxi'll check back in 1 hr14:41
flacoste1240 -> smoser fix for oauth in maas-enlist14:41
flacoste1241 -> IPMI auto-config in maas-enlist (optional really)14:42
flacosteroaksoax, Daviey, smoser: https://bugs.launchpad.net/maas/+bugs?field.tag=missing-in-quantal14:44
smoserflacoste, thanks14:44
roaksoaxflacoste: 1241 i'll try to make it happen, but this needs support from maas-enlist too14:45
roaksoaxflacoste: so there might not be time to finish it14:45
flacosteroaksoax: right, fwiw, the API changes are available14:45
roaksoaxflacoste: yes I saw.. I'll be working on it todayt14:46
roaksoaxallenap: ping14:54
flacostejam, allenap: the reversal in 1239 does that mean that self-signed certificate cannot work with the maas-cli anymore?14:54
allenapflacoste: No, it means it wont' work for users of apiclient. maascli doesn't use apiclient; before reverting this was an attempt to "upstream" the remote code in maascli to apiclient.14:55
flacosteallenap: got it14:55
roaksoaxallenap: what am I doing wrong?14:56
roaksoaxcurl --data "op=new&mac_addresses=e4:11:5b:13:81:9d&hostname=&architecture=amd64&subarchitecture=generic&after_commissioning_action=0&power_type=ipmi&power_parameters={"power_address":"test", "power_user":"test", "power_pass":"test"}" http://localhost/MAAS/api/1.0/nodes/14:56
roaksoaxFailed to parse JSON power_parameters14:56
rvbaroaksoax: power_parameters='{"power_address":"test"}'14:57
rvbaNote the quotes.14:57
rvbajson.dumps({"power_address":"test"})14:57
rvba'{"power_address": "test"}'14:57
rvbaYou have to pass a json string.14:58
roaksoaxrvba: got it :)14:58
allenaproaksoax: Try: curl --data "op=new&mac_addresses=e4:11:5b:13:81:9d&hostname=&architecture=amd64&subarchitecture=generic&after_commissioning_action=0&power_type=ipmi" --data-urlencode="power_parameters={"power_address":"test", "power_user":"test", "power_pass":"test"}" http://localhost/MAAS/api/1.0/nodes/14:58
roaksoaxit was the quotes14:58
mgzso, it seems django can't do internal redirects...15:06
rvbamgz: you mean redirects to an address created with reverse('view-name')?15:16
mgzrvba: I was just going to make /favicon.ico serve the same result as /static/img/favicon.ico ...but that turned out to be non-trivial15:17
mgzI'd just use apache directives ideally, but don't want to upset django15:18
rvbamgz: why do you want to do that?  Also, you cannot assume that the homepage of MAAS is '/'.15:18
mgzbecause currently requesting /favicon.ico is a 404 and it wouldn't hurt to serve it instead15:20
rvbamgz: src/maasserver/templates/maasserver/base.html:    <link rel="shortcut icon" href="{{ STATIC_URL }}img/favicon.ico"/>15:21
mgzbrowsers tend to request that regardless of html giving a different path15:21
allenaproaksoax: Ah right, yes, the quotes. From looking at --trace-ascii output, http://pastebin.ubuntu.com/1269411/ looks to be the correct way to do this. (You could s/--data-urlencode/--form/g I think too).15:21
rvbamgz: really?15:21
allenaproaksoax: --data is a recipe for failures and/or data corruption, because it assumes that the value is already URL encoded.15:21
mgzyes, what if you're not fetching an html page? (not a common case here, but if was easy to fix I'd just fix it)15:22
roaksoaxallenap: cool, I;ll test that15:22
rvbamgz: right.  Looks very minor to me… but in production, we have the prefix /MAAS in front of all the urls, so if the browser requests /favicon.ico, it won't get anything back and there is not much we can do about it.15:31
rbasakrvba: could we redirect /favicon.ico to /MAAS/favicon.ico in packaging perhaps? Just an idea.15:32
rbasakNot sure what implications that would have though15:33
rvbarbasak: and what if you install another service in /AnotherService… it will get a wrong favicon.15:33
rbasakYeah exactly15:33
rvbaI don't think we want to hijack /favicon.ico.15:33
mgzwhy are we trying to support serving multiple different things from one hostname exactly?15:34
rbasakIt'd be nice to have it on servers that are dedicated to MAAS15:34
rbasak(by default)15:34
rbasakBut the only way I can think of doing it cleanly in packaging is perhaps not the best thing to do for today15:34
rbasakI'm thinking of a separate maas-favicon recommends that conflicts with other services in some way15:34
mgzthe other magic top level name has a url mapping at the django level, but I guess just sits harmlessly at /MAAS/robots.txt in deployment15:36
mgzanyway, put up a branch with the fix I was actually aiming at15:36
smoserhttps://code.launchpad.net/~smoser/maas/drop-ttyS0-kernel-opt/+merge/12874715:46
matsubararvba, ping15:46
rvbamatsubara: pong15:47
matsubararvba, so, I just tried maas - 0.1+bzr1226+dfsg-0+1229+124~ppa0~quantal1 on a pristine quantal vm and maas-pserv is not started15:47
allenapmgz: Mark said something about having to use an ico for full browser compatibility. Obviously you're still generating an ico, but perhaps he meant something else by it?15:48
rvbamatsubara: anything in the upstart log?15:48
rvbamgz: I was about to ask the same question :)15:48
matsubararvba, just a bunch of lines like this: Removing stale pidfile /run/maas-pserv.pid15:49
rvbamatsubara: I'm trying to install the package from the daily ppa right now…15:49
matsubararvba, and apt/term.log shows this: maas-pserv start/running, process 1015615:50
matsubaraso I think it started but for some reason it failed15:50
mgzallenap: I interpret what he said as assuming he'd generated an ico containing png files, but if fact he didn't15:50
rvbamatsubara: pserv not started here :/15:51
allenapmgz: Right, cool.15:51
matsubararvba, aha!15:51
mgzthe larger sizes won't stop old (pre-vista internet explorer (do we even care..)) from picking out the 16x16 bitmap15:52
matsubararvba, so on a upgrade it keeps running fine but not on a new install15:52
smosersomeone want to ack that for me? i really hate this change. but i think its a requirement at this point in time.15:52
matsubararvba, do you know of any other logs that might be relevant?15:52
rvbamatsubara: yesterday it was fine :/15:52
allenapmatsubara: You'll need at least bzr 1239 to fix the pserv not starting issue, sorry.15:52
matsubaradoes your upstart log show anything?15:52
rvbaallenap: what was the issue again?15:52
matsubaraallenap, ah so you knew about it all along15:53
allenaprvba, matsubara: bug 106443715:53
ubot5Launchpad bug 1064437 in MAAS "The expectations of MAASDispatcher.dispatch_query are not tested" [High,Triaged] https://launchpad.net/bugs/106443715:53
rvbamgz: what's the benefit of having all but one of the image as a *raw* png?15:53
allenapmatsubara: Ha, I only just saw you having problems.15:53
matsubarahmm I can't build new packages. LP is failing to build packages in the daily builds PPA due to a bzr error15:54
matsubaraallenap, no worries, just kidding :-)15:54
allenapPhew :)15:54
matsubarathanks for the pointer15:54
mgzrvba: the 'raw' is a little confusing, but, in short, size15:54
matsubaraallenap, where do you see logs for this?15:54
matsubaras/this/this error/?15:54
mgzpng is a compressed image format, bmp is not15:55
mgzico was originally a sort of container for bitmaps15:55
allenapmatsubara: I don't; jam told me it was broken.15:55
mgzwith recent format revisions it can also be a container for pngs15:55
mgzso, storing the larger images as 'raw' png rather than exploding them to bitmaps saves space15:56
rvbaallenap: in this bug, you say is breaks start_cluster_controller, but in the package I'm testing, the cluster worker is started ok.15:56
rvbamgz: I see, I got confused by the world 'raw' indeed :)15:57
allenaprvba: What rev are you on? It was only a problem for revision 1234 to 1238 inclusive.15:57
matsubararvba, allenap: I got the log line in apt/term.log saying maas-pserv was started but after the package install finishes, the process is not running. Maybe it's failing and reporting a success?15:58
rvbabzr122615:58
rvbaThe revision from the package in the daily ppa.15:58
allenapAh, so that bug isn't the problem.15:58
allenapFor matsubara either.15:58
rvbaYep, there is a real problem then.15:59
matsubaraI'm using: 0.1+bzr1226+dfsg-0+1229+124~ppa0~quantal115:59
matsubaraallenap, btw, this two revision numbers are confusing. when you say 1234..1238 do you mean trunk right?16:00
rvbamatsubara: if I start the service manually it seems to be started all right.16:04
matsubararvba, yep16:06
rvbamatsubara:trying one more time on another instance.16:07
rvbamatsubara: this time it worker :/16:09
matsubara!16:09
rvbaworked*16:09
matsubarahow weird16:09
rvba/var/log/upstart/maas-pserv.log is still full of "Removing stale pidfile /run/maas-pserv.pid"16:10
matsubarayep, just like mine16:10
matsubaraI'm trying again as well16:10
matsubararvba, how are you starting a new pristine env?16:10
rvbaI just start a new canonistack instance, add the daily ppa, and then install maas.16:11
matsubaraok16:11
matsubaraallenap, rvba have you seen the last package build failure: https://launchpadlibrarian.net/119221274/buildlog.txt.gz ?16:13
allenapmatsubara: Yeah, trunk.16:13
matsubaraallenap, is this because of your change?16:13
* allenap looks16:13
allenapmatsubara: Nope, I haven't been near the files in 99-temporary-fix-constraints.patch. I think that this has probably been fixed in trunk, so the patch can be removed. rbasak, can you help confirm?16:16
smoserDaviey, roaksoax it seems to me that adding maas-ipmi-autodetect to commissioning broke kvm (and possibly anything that doesn't have such a device)16:17
smoseris there a /dev/ entry that we could expect to be present to know whether or not we should go looking ? or some way to tell freeipmi to time out ?16:17
mgzright, seems that patch just needs removing from the packaging branch16:17
smoserit does seem to timeout eventually, but i'd say its in the 2 minute time frame.16:18
matsubaradoes anyone know how I could install maas without having to answer the package installation questions? I tried to use a debconf seed file (maas.seed: https://pastebin.canonical.com/76135/) but it doesn't seem to work. Well, I get no questions asked but the default-maas-url value is not set to the one in the seed file.16:20
smoserand then on failure, it still tries to call maas-signal with the power params.16:20
matsubarasmoser, roaksoax: maybe one of you know ^?16:20
smoserhttp://bazaar.launchpad.net/~smoser/maas/maas-pkg-test/view/head:/maas-ephemeral-test-quantal.txt16:21
smosermatsubara, ^16:21
smosersee line 90. set DEBIAN_FRONTEND=noninteractive and for good measure set stdin from /dev/null16:21
matsubarasmoser, ah thanks16:22
Davieysmoser: we *need* to silently fail, i think16:23
matsubarasmoser, you also change the string in the seed passed to debconf?16:23
rvbaI think that the pserv service depends on something that is installed by the region cluster.16:23
smosermatsubara, i dont follow16:23
smoserDaviey, it should not attempt to call maas-signal if the probe for ipmi fails.16:23
smoserso we need to handle that bettter16:24
smoserbut we also need to not add 2 minutes to enlistment if ipmi is not present16:24
matsubarasmoser, lines 82 to 8516:24
matsubarasmoser, ah no, that's just setting the seed file, correct?16:24
smosermatsubara, i'm setting the answer to that question16:26
smoserDaviey, is ipmi a device ?16:26
smoserthat i can look for in /dev ?16:26
matsubararight, thanks smoser16:27
matsubaraI'll give it a try16:27
matsubararvba, tried again and pserv is down16:27
smoserawesome. strace on bmc-config shows that it reads /etc/freeipmi//freeipmi.conf 1 byte at a time.16:29
rvbamatsubara:  if I manually remove all the region stuff, then pserv refuses to be restarted.16:32
roaksoaxsmoser: ok I see where it dies16:32
rvba/usr/bin/twistd -n --uid=maas --gid=maas --pidfile=/run/maas-pserv.pid --logfile=/tmp/zz maas-pserv --config-file=/etc/maas/pserv.yaml16:32
rvbausr/bin/twistd: Unknown command: maas-pserv16:32
smoserroaksoax, do you know what devices it wants?16:33
roaksoaxsmoser: smoser FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-31-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device16:33
smoserroaksoax, but that doesnt mean anything in and of itself16:33
smoserthe driver could fail to load because it was already loaded16:33
smoseror because it was built into a kernel16:33
matsubararvba, what does the log say? I restarted my environment and got the same problem.16:34
roaksoaxsmoser: "No such device" --> this caould be 2 things 1. ipmi-locate might be erroneously detecting IPMI and continues, and bc-config gets stuck somewhere16:34
roaksoaxor 2. that causes ipmi-locate to get stuck16:34
smoserfrom strance, it looks like it wants /dev/ipmi0 or /dev/bmc but then it goes looking in /dev/mem also before sleeping16:34
roaksoaxsmoser: but after a while, it continues16:34
rvbamatsubara: the logs says nothing.16:35
smoserroaksoax, yes, it times out after like 2 minutes-ish16:35
roaksoaxsmoser: yeah.. such a PITA16:36
smoserif i knew what it was looking for in /dev/mem, then i'd just do a udevadm settle after module load16:36
smoserand hten if no /dev/ipmi* or /dev/bmc* then i would skip that.16:36
roaksoaxDaviey: so I need to upload maas-enlist source and add a maas-commission binary package16:37
smoserbut i'm afraid it might be looking in /dev/mem for some ipmi device that does not have a device driver but is a /dev/mem interface16:37
matsubararvba, I'm building a new package and we can test allenap fix deals with the issue16:38
roaksoaxsmoser: http://paste.ubuntu.com/1269561/16:43
roaksoaxsmoser: ok, so that will return an output in the way of {"power_address"="X", "power_user"="Y", "power_pass"="Z"}16:44
roaksoaxsmoser: but I need to pass that to maas-enlist between single quotes, how can I do that?16:44
smoseryou actuall do not have to.16:45
smoser$ output=$(echo '{"power_address"="X", "power_user"="Y", "power_pass"="Z"}')16:46
smoser$ sh -c 'echo "1=^$1$"' -- "$output"16:46
smoser1=^{"power_address"="X", "power_user"="Y", "power_pass"="Z"}$16:46
smoserie, get the output, and quote the variable with doble quotes and you're fine.16:46
smoserroaksoax, http://paste.ubuntu.com/1269572/16:49
smoserthats in a kvm node.16:49
smoserso there is 10 minutes of builtin sleep by that program by default. meaning enlistment of anything without ipmi is delayed 10 minutes.16:49
roaksoaxsmoser: right...  but it order for it to get there, ipmi-locate must have succeeded16:50
smoserunlikely.16:50
smoserthere is no ipmi.16:50
roaksoaxso maybe it is getting stuck in ipmi-locate16:50
roaksoaxunles it "detects" it16:51
smoserhttps://bugs.launchpad.net/maas/+bug/106452716:52
ubot5Ubuntu bug 1064527 in MAAS "ipmi detection takes 10 minutes if no ipmi present" [Undecided,New]16:52
roaksoaxsmoser: in my case it didn't take 10 mins16:53
roaksoax:)16:53
rvbamatsubara: I think allenap and I found the problem,16:53
smoserroaksoax, http://paste.ubuntu.com/1269579/16:53
smoserreally? did you try in a kvm instance?16:53
matsubararvba, what is it?16:53
rvbaProblems* I should say.16:53
roaksoaxsmoser: yes I tried the kvm instance, it took like 1 min or so16:54
smoseri dont know tha ti believe you, roaksoax16:54
smoser10m0.X seconds for the whole command, that I straced elsewhere and watched to 'nanosleep' repeatedly16:54
smoseris a very suspicious time16:55
rvbamatsubara: 2 things: a) the cluster controller misses some of the required dependencies (txamqp at least) b) it tries to write its log to /var/log/maas which does not exist before the region is also installed.16:55
smoserbut none the less.16:55
rvbaIt works sometimes because (I guess) the region gets installed right after the cluster.16:55
rvbaSo the dependencies are there and /var/log/maas is created.16:55
rvbaI'm guessing the upstart script retries to start the service a few times.16:55
rvbaI the installation of the region is quick enough, it manages to start the pserv service.16:56
matsubaraI see16:56
roaksoaxrvba: if you pressume is because the /var/log/maas dir is not create, please file a bug , assign it to me, and explain which package should also create the log dir16:56
rvbaroaksoax: that's one of the 2 problems indeed.16:57
rvbaroaksoax: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/106453917:04
ubot5Ubuntu bug 1064539 in maas (Ubuntu) "The pserv service logs to /var/log/maas/pserv.log and that directory (/var/log/maas/) is not created but the cluster controller package" [Critical,Triaged]17:04
rvbas/but/by/17:05
allenaproaksoax: I have to go, but can I bring https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1064542 to your attention? I can't mark it critical, but I think it is.17:10
ubot5Ubuntu bug 1064542 in maas (Ubuntu) "python-maas-provisioningserver is missing several dependencies" [Undecided,New]17:10
roaksoaxallenap: ack17:11
roaksoaxthanks17:11
=== flacoste changed the topic of #maas to: Final Freeze is today: waiting on upstream fixes for bug 978127; packaging fixes: bugs 1064542 and 1064539| Discussion of upstream development of Ubuntu's Metal as a Service (MAAS) tool | MAAS jenkins: https://jenkins.qa.ubuntu.com/job/maas-trunk/
roaksoaxallenap: so other packages no longer depend in those then17:11
allenaproaksoax: They may do, so don't change other packages yet. I'll try to check their deps later.17:12
roaksoaxalright thanks17:13
smoserroaksoax, more data for you. https://bugs.launchpad.net/maas/+bug/106452717:14
ubot5Ubuntu bug 1064527 in MAAS "detect_ipmi needs improvement. detects non-existant device in nested kvm" [Undecided,New]17:14
rvbamatsubara: I've documented the results of our findings on bug 1064020.17:16
ubot5Launchpad bug 1064437 in MAAS "duplicate for #1064020 The expectations of MAASDispatcher.dispatch_query are not tested" [High,Triaged] https://launchpad.net/bugs/106443717:16
matsubararvba, thanks17:17
rvbamatsubara: but basically, it all boils down to 2 packaging bugs.17:17
rvbaBugs that roaksoax will be fixing soon ;)17:18
roaksoaxsmoser: err passing the json format is a PITA17:18
roaksoaxsmoser: i can't get to pass the full json string needed17:18
smosershow me what you're doing ?17:18
smoserit should'nt be bad.17:18
roaksoaxsmoser: this is maas-ipmi-autodetect which returns in json format: http://paste.ubuntu.com/1269631/17:19
roaksoaxsmoser: this is maas-enlist = http://bazaar.launchpad.net/~andreserl/maas/test/revision/3217:20
roaksoaxsmoser: which would require to pass --power-params '{"test": "test", "test2", "test2"}'17:21
roaksoaxsmoser: but every way I do it, maas-enlist doesn't get the whole json string it just get partial lilke {"test": "test",17:22
matsubararvba, so, this has nothing to do with bug 1064020?17:25
ubot5Launchpad bug 1064437 in MAAS "duplicate for #1064020 The expectations of MAASDispatcher.dispatch_query are not tested" [High,Triaged] https://launchpad.net/bugs/106443717:25
smoserroaksoax, what is calling maas-enlist ?17:26
matsubararvba, because I dupe 1064020 against that one17:26
matsubaraerr17:26
roaksoaxsmoser: shell script17:26
smoserwhat is taking output of maas-ipmi-autodetect and feeding it to maas-enlist17:26
smoserwhere is that. that is your issue.17:26
roaksoaxsmoser: it should go on maas enlist metadata17:26
matsubaraoh, wait17:26
matsubaraI got confused by the bot17:26
rvbamatsubara: no, nothing to do with that one.17:26
matsubaraok, I'll undupe and close 1064020 as invalid since it's reported on the package17:27
matsubararvba, question for you, when I install maas-dns, shouldn't it ask for the config information to put in /etc/bind/named.conf.options? After every install in the QA lab I have to run this: https://pastebin.canonical.com/76145/17:34
smoserroaksoax, what do you have there. thats where your sissue is.17:35
rvbamatsubara: not really sure why you had to do that.  What is the 'forwarders' stuff all about?17:37
matsubararvba, that's the only way I got dns to work in the lab. I got that change from Julian.17:38
rvbamatsubara: hum, I don't know about that.  Could you please file a bug?  Let's see what Julian has to say about that.17:39
matsubararvba, will do17:39
roaksoaxsmoser: ubuntu@node2:~$ ./ipmi.sh17:48
roaksoax^{"power_address": "192.168.2.111", "power_pass": "6o9TuzEvY9fQ", "power_user": "maas-commissioning"}$17:48
roaksoaxFailed to parse JSON power_paramete17:48
roaksoaxsmoser: http://paste.ubuntu.com/1269688/17:48
smoserwhat does sudo ./maas-ipmi-autodetect --enlist output17:49
smosersudo ./maas-ipmi-autodetect --enlist17:49
roaksoaxsmoser: prints the json string we need {"test": "test", "test":"test"}17:50
smoserthat'd be fine17:50
smoserjust quote "$var" then17:50
smoser./maas-enlist --serverurl localhost --power-type ipmi --power-params "${var}"17:50
roaksoaxsmoser: ahhhh that;s was it "${var}"17:51
roaksoaxthanks17:51
roaksoaxlol :)17:51
roaksoaxnever ocurred to me17:51
roaksoaxsmoser: i'm including maas-signal in maas-commission binary package if that's ok with you18:02
smoserroaksoax, well we need a fix there.18:04
smoserstill for this oauth bit18:04
smoseri'm ok with that, but i'm working on that now.18:05
roaksoaxsmoser: alright!18:05
roaksoaxsmoser: ideally i think this should probably end up in maas-utils package or similar18:05
roaksoaxsmoser: within the maas source18:05
roaksoaxDaviey: ping18:06
roaksoaxDaviey: is it too late for me to introduce this new binary package as part of maas-enlist source?18:06
matsubarasmoser, I set the debconf database with my seed file but when I installed the package it overrode the value. Is there anything I need to do so apt-get uses the value I supply in the seed file?18:24
matsubarasmoser, I installed the package with sudo apt-get install -y maas maas-dhcp maas-dns18:24
matsubaraand my seed file has: maas-region-controller  maas/default-maas-url   string  192.168.21.518:24
smoserprobably just that maas-cluster-controller is the package that prompts you18:25
smosermaas-cluster-controllermaas-cluster-controller/maas-urlstringhttp://localhost/MAAS18:26
smosermatsubara, ^18:30
matsubarasmoser, I normally run sudo dpkg-reconfigure maas-region-controller to change that18:31
matsubaraso, maas-region-controller maas-region-controller/default-maas-url string 192.168.21.518:31
smoserwell that seems wrong.18:31
matsubara?18:31
matsubarait's what the package tells me to run after the package install :-)18:32
smoserwell, whats above works for me.18:40
smoserwhat you're using doesn't work for you.18:40
smoseri'm not able to spend time on why at the moment.18:40
smoserbut i'd suggest using what works for me/18:40
matsubaraok18:42
matsubarasounds good to me. trying that. thanks!18:42
smoserrbasak, https://code.launchpad.net/~smoser/maas/trunk.maas-signal-clockskew/+merge/12879419:01
smoseryou can give that a sniff. i'm guessing it works.19:01
smoserit does not ever set the hardware clock though.19:01
rbasaksmoser: looking19:01
smoserit works for me. output at http://paste.ubuntu.com/1269818/19:02
smoserrbasak, it works for me, testing when i apply this patch19:03
smoserhttp://paste.ubuntu.com/1269821/19:03
smoserwhich basically breaks the clock19:03
rbasaksmoser: looks good. https://pastebin.canonical.com/76152/ has enlistment and then commissioning19:11
rbasaksmoser: seeing multiple corrections but I presume that's juts multiple calls to maas-signal19:12
rbasaksmoser: RTC doesn't change during commissioning. Trying the install step now to see if that fixes it, which I think it does.19:12
smoserrbasak, right. since it does not ever actually set the clock, each invocation of maas-signal has to re-discover bad clock.19:13
smoserrbasak, do you know where install gets its clock from?19:14
rbasaksmoser: ntp I presume19:14
smoserntp.ubuntu.com19:14
smoser?19:14
rbasakI assume so19:14
rbasakI don't actually know19:14
rbasaksmoser: looks like yes - it's preseeded19:16
rbasaksmoser: /usr/share/maas/preseeds/preseed_master19:16
roaksoaxsmoser: if in misc_bucket i define:19:18
roaksoax- &maas_ipmi_detect |19:18
roaksoax- &maas_enlist |19:18
roaksoaxetc etc19:18
roaksoaxeach is run as a script?19:18
smoserrbasak, ok. for now i think we just ship this.19:20
smoserbut for later, i think we hav a "ntp" setting in maas. and feed that to ephemeral environment.19:21
smoserif it was set to something other than 'disabled' then set it based on that remote clock.19:21
smoserroaksoax, where are you seeing that/19:25
roaksoaxsmoser: enlist_userdata, and i'm asking if that's the case19:26
smoserah. contrib/preseeds_v2/enlist_userdata19:26
smoserright.19:26
smosersee19:26
smoserruncmd:19:26
smoser - [ sh, -c, *maas_enlist ]19:26
smoserthat references the text in maas_enlist19:26
smoserso just add another entry in that list for maas_ipmi_detect19:26
rbasaksmoser: tested and I've approved the MP19:28
rbasaksmoser: thanks!19:28
roaksoaxsmoser: ok cool thanks19:30
roaksoaxsmoser: and that's what i was doing just watned to make sure :)19:30
flacosteroaksoax: upstream 1241 should be good to upload19:34
flacosteroaksoax: unless you want your changes in as well which mean we'd ship 124219:34
flacosteroaksoax: but we have 25 minutes before the freeze happens19:35
roaksoaxflacoste: isn't it at 21 UTC?19:35
flacosteindeed!19:36
flacostethat's 60 more minutes!19:36
roaksoaxflacoste: indeed :)19:36
roaksoaxflacoste: i'm half way done19:36
flacostetriple the time!19:36
roaksoaxso lets cross fingers :)19:36
smoserhttps://code.launchpad.net/~smoser/maas/trunk.maas-signal-clockskew/+merge/12879419:36
smoseris ready, not piced up yet19:36
=== flacoste changed the topic of #maas to: Final Freeze is today: upstream RC revision: 1241; packaging fixes: bugs 1064542 and 1064539| Discussion of upstream development of Ubuntu's Metal as a Service (MAAS) tool | MAAS jenkins: https://jenkins.qa.ubuntu.com/job/maas-trunk/
flacostesmoser: i received a merged message already19:36
smoserreally? Approved by: Scott Moser 1 minute ago19:37
flacosteweird19:38
flacostesmoser: actually, it wasn't the oauth fix, but the console fix19:39
flacoste124119:39
flacoste1242 will contain the oauth fix19:39
=== flacoste changed the topic of #maas to: Final Freeze is today: upstream RC revision: 1242; packaging fixes: bugs 1064542 and 1064539| Discussion of upstream development of Ubuntu's Metal as a Service (MAAS) tool | MAAS jenkins: https://jenkins.qa.ubuntu.com/job/maas-trunk/
rbasaksmoser: I understand that it might work, but it's still hard to read as it isn't obviously correct!19:42
smoserit is obviously correct19:45
smoseras the demonstrating script shows.19:45
smoserit may not be obvious to you.19:45
smoserbut it is to python19:45
smoserand in cases where the 2 differ, i agree with python.19:45
smoserwhy would:19:46
smoser except Exception as X19:46
smoserhave any different scoping rules than19:46
smoser Y = X19:46
smoserthat would be confusing.19:46
flacosteroaksoax: 1242 is in19:58
roaksoaxflacoste: ok, i'm almost there with the enlistment19:58
roaksoaxflacoste: if it doesn'y work withing the next 20 mins19:59
roaksoaxi'll give up19:59
roaksoaxand prepare an upload19:59
flacosteroaksoax: perfect, am i right in that you already fixed the two packaging bugs mentioned in the topic?19:59
roaksoaxflacoste: yep i blieve they are fixed now20:00
Davieyroaksoax: it is not too late to do that, no20:01
roaksoaxDaviey: the maas-nelist thing?20:02
Davieyroaksoax: can we do it soon tho :)20:02
Davieyroaksoax: not too late to introduce a new bin deb20:02
roaksoaxDaviey: ok cool20:03
Davieyroaksoax: ETA?20:03
ppetrakiso I get this backtrace when I add a  node via mac address: http://paste.ubuntu.com/1269952/20:04
roaksoaxDaviey: i made a maas-enlist upload fixing a bug20:04
roaksoaxDaviey: so you could reject that and Ill upload the other thing now20:04
Davieyok20:05
roaksoaxDaviey: iuploaded20:11
Davieyroaksoax: so here is the thing... i don't think i rejected it20:12
Daviey20:45 -queuebot:#ubuntu-release- Unapproved: accepted maas-enlist [source] (quantal-release) [0.4+bzr32-0ubuntu1]20:12
Davieysomeone else accepted it20:12
roaksoaxDaviey: alright, I;ll just prepare a different changelog20:13
roaksoaxDaviey: could you please reject maas-enlist-0.4+bzr3520:15
roaksoaxDaviey: i'll upload a new one20:15
Davieyrejected20:16
flacostesmoser: is bug 1006966 still relevant?%20:16
ubot5Launchpad bug 1006966 in cloud-init (Ubuntu) "maas mirror values are overwritten by cloud-init" [High,Triaged] https://launchpad.net/bugs/100696620:16
roaksoaxDaviey: ok uploaded a new one20:16
flacosteppetraki: everybody is heads down trying to hit feature freeze20:17
flacosteppetraki: and that's with the MAAS version still using cobbler20:17
Davieyin a relaxed and orderly manner, due to our smooth planning and quality control20:18
flacoste ppetraki: and that's with the MAAS version still using cobbler20:18
smoserflacoste, its fixed. i'll update with comment how.20:18
ppetrakiflacoste, I had duplicate cobbler entries, once I deleted them, it added correctly20:18
flacosteDaviey: :-)20:18
ppetrakiflacoste, thanks20:18
flacostesmoser: similary, is bug 1028501 fixed?20:22
ubot5Launchpad bug 1028501 in cloud-init (Ubuntu Precise) "cloud-init selects wrong mirrors for arm" [High,Triaged] https://launchpad.net/bugs/102850120:22
roaksoaxsmoser: http://paste.ubuntu.com/1269987/20:25
smoserflacoste, i put comments in them. you put the maas in the right state.20:26
roaksoaxflacoste: ok so I think the enlist stuff is finished... however, we still need publishing of the newer maas-enlist recently uploaded for it to work20:26
flacosteroaksoax: is that a problem? would it prevent a new upload?20:27
roaksoaxflacoste: so, it could get merged, and later we file a bug saying "autodetection on enlistment is not enabled"20:27
flacosteand upload as part of the 0-day updates next week?20:28
Daviey0-day if essential, right?20:29
Davieywe are not currently planning a 0-day, right? :)20:29
flacostewe are not20:29
flacostejust would be nice to send a couple bug fixes more to users :-)20:29
flacosteand autodetection only working during commissioning is not that interesting20:30
flacosteroaksoax: can you merge it and make it part of the upload, or will it be rejected because maas-enlist hasn't been published yet20:36
roaksoaxflacoste: no it wont20:36
flacosteroaksoax: if it can be accepted, but really will only work once maas-enlist is published, i think it'd be fine20:36
roaksoaxflacoste: ok, i'm running one more test20:37
smoserroaksoax, so we're copying that whole commissining script basically?20:39
smoserthat sucks. :-(20:39
smoser(i dont have a better way, but it sucks)20:39
roaksoaxsmoser: yes, and no20:39
roaksoaxsmoser: Daviey just accepted maas-enlist20:39
smoserfyi, http://bazaar.launchpad.net/~smoser/+junk/backdoor-image/view/head:/backdoor-image20:39
roaksoaxsmoser: with the new binary package20:39
roaksoaxsmoser: but to be safe i'm copying it20:40
smoserthat takes care of your "remove this section"20:40
roaksoaxsmoser: ok so we should be able to drop it as SRU20:40
roaksoaxsmoser: is that ok with you?20:40
roaksoaxsmoser: we temporarily merge all the copying of the script, and then we drop it, once the package hits the archive and I can test it works20:41
flacostesmoser: how is bug 1044503  different than bug 1045390 ?20:41
ubot5Launchpad bug 1044503 in MAAS "kernel command line is not easily customizable" [High,Triaged] https://launchpad.net/bugs/104450320:41
ubot5Launchpad bug 1045390 in MAAS "There's no way to add kernel parameters to a system read" [High,Triaged] https://launchpad.net/bugs/104539020:41
smoserflacoste, probably not. roaksoax ^ you have thoughts ?20:42
flacosteroaksoax: that question can wait until the upload is done :-)20:43
smoserroaksoax, i think your plan is fine.20:43
smoserjust make sure you get the latest version of maas-signal20:43
roaksoaxsmoser: i did20:45
roaksoaxok this is almost here20:46
flacostesmoser: is bug 1053190 fixed?20:46
ubot5Launchpad bug 1053190 in MAAS "multiple NICs could cause cloud-init nonet timeout" [High,Triaged] https://launchpad.net/bugs/105319020:46
smoserk. i'm going afk for a few hours.20:46
roaksoaxsmoser: i get this20:46
roaksoax}sh: 191: --power-params: not found20:46
roaksoaxsmoser: https://pastebin.canonical.com/76160/20:46
Davieymatsubara: Hey, what is your QA plan from now?20:47
matsubaraDaviey, currently I'm working on deploying with juju in the QA lab (which has 7 nodes arm and amd64)20:47
roaksoaxsmoser: any idea?20:48
smoserwhitespace after \20:50
roaksoaxok cool20:51
roaksoaxsmoser: https://code.launchpad.net/~andreserl/maas/enlistment_ipmi_autodiscovery/+merge/12881920:54
roaksoaxflacoste: https://code.launchpad.net/~andreserl/maas/enlistment_ipmi_autodiscovery/+merge/12881920:54
roaksoaxplease review20:54
flacostesmoser: does bug 1034116 still need changes in MAAS?20:55
ubot5Error: Launchpad bug 1034116 could not be found20:55
flacosteroaksoax: line 17: it should be commented out :-)20:56
Davieymatsubara: cool.  Do you have plans to try a cd image?20:57
roaksoaxflacoste: done20:57
matsubaraDaviey, nope20:59
roaksoaxflacoste: crap something failed in another test I just run21:00
flacosteroaksoax: why the all-caps variable name at line 147?21:00
roaksoaxflacoste: "globals"21:01
flacosteroaksoax: but they aren't globals?21:01
roaksoaxflacoste: I know :) I didn't have the time to update that21:01
roaksoaxflacoste: that's why the quotes :)21:02
flacosteroaksoax: looks ok to me, but i'm not a shell expert21:03
roaksoaxsmoser: could you please?21:03
roaksoaxsmoser: https://code.launchpad.net/~andreserl/maas/enlistment_ipmi_autodiscovery/+merge/12881921:03
* roaksoax waiting for it to land21:07
roaksoaxto package it up21:07
roaksoaxflacoste: so maas-lander is taking forever to land the branch21:19
roaksoaxthat's the only thing i'm waiting on to get the package read21:19
roaksoaxDaviey: just uploaded MAAS could you please take care of it?21:27
Davieyyes21:28
roaksoaxDaviey: thank you!!21:29
flacostethanks roaksoax, Daviey and smoser!21:33
* roaksoax can now rest in peace :)21:37
roaksoaxsmoser the bug you came across in nested kvm... is this canonistack?22:59
Davieyroaksoax: it is23:00
Davieyroaksoax: As IS use ksplice to patch the running kernel... i think smoser wasn't confident it was a regression on it's own23:01
DavieyMaybe I miss understood23:01
roaksoaxso that means that it could have been related to the fact that that particular hardware does have ipmi hence the instances detect it?23:01
Davieyroaksoax: No, i don't think that is passed through.23:02
DavieyIt's only the cpu23:02
DavieyIf that IS passed through, it's a massive security concern23:02
roaksoaxindeed23:02
roaksoaxi will look into it23:02
Davieyroaksoax: you see, https://launchpadlibrarian.net/96102740/qemu_1.0%2Bnoroms-0ubuntu7.debdiff .. It only exposes the VMX feature, as an addition23:03
roaksoaxrigh23:04
Davieyand on that note.. nn23:05
roaksoaxDaviey: night!!23:05
=== matsubara is now known as matsubara-afk
smoserroaksoax, no.23:15
smoserthe issue is not t hat there actually is ipmi in play23:15
smoserits just the way ipmi-detect works23:15
smoserit looks like it randomly walks through memory23:15
smoserand i think is getting false positives.23:15
smoserit opens /dev/mem and looks for stuff.23:16
roaksoaxsmoser: right23:16
smoseri'm surprised that it was so bad, and i could have just been being unlucky.23:16
smoseras other times it did return nothing23:17
roaksoaxheh right23:17
smoseri wondered if we could just limit it to the /dev/ipmi* and /dev/bmc*23:17
smoserand disable its searches for /dev/mem23:17
smosergreat work on bug 1032004, roaksoax23:18
ubot5Launchpad bug 1032004 in Indicator Remindor "Indicator-remindor don't start on Ubuntu 12.04" [Critical,Fix released] https://launchpad.net/bugs/103200423:18
smosererr... 104200423:18
smoserbug 104200423:18
ubot5Launchpad bug 1042004 in MAAS "Enlistment does not do BMC discovery" [Critical,Fix released] https://launchpad.net/bugs/104200423:18
roaksoaxthanks... it was pretty straightforward though :)23:18
roaksoaxsmoser: ok, I got it23:23
roaksoaxsmoser: sudo bmc-config --disable-auto-probe --checkout23:23
smoser?23:23
smoserbut is that somethign thats going to mean we do not support "in band" cards?23:23
smosermaybe we should make that a default and allow it to be configed overridden.23:24
smoseranyway.23:24
smoseragain, good job. i'm on my way out. probably check back in.23:24
roaksoaxsmoser: i'm assuming that if it works, it means we have local access to the IPMI card right?23:24
smoseri dont know what it means really.23:24
roaksoaxsmoser: that it doesn't probe for several IPMI interfaces23:25
smoserif it means "don't crawl through /dev/mem", that sounds good at first.23:25
smoserbut if 75% of the existing cards would be found that way, that does *not* sound good.23:25
smoseri really dont have enough information to make even a guess23:25
smoserlater.23:26
roaksoaxlater23:26
bigjoolshi guys23:35
roaksoaxbigjools: good morning sir23:37
bigjoolsroaksoax: hey there! how are we doing?23:38
roaksoaxbigjools: good, maas is in archives23:40
bigjoolsgood news!23:40
roaksoaxindeed23:41
bigjoolsroaksoax: I see enistment is poking things in the BMC now ...23:41
bigjoolsenlistment*23:41
roaksoaxbigjools: it is indeed :)23:41
bigjoolsroaksoax: not sure it's a great idea to be changing parameters on enlistment :/23:41
roaksoaxsudo apt-get dist-upgrade23:41
roaksoaxerr23:42
roaksoaxbigjools: you mean power parameters?23:42
bigjoolsyeah23:42
bigjoolserr no23:42
bigjoolsI mean, setting user/pass on the bmcx23:42
roaksoaxbigjools: oh it is just a temporary one23:42
bigjoolsor does it add a new one?23:42
roaksoaxbigjools: commissioning overrides it23:42
bigjoolsdoes the old one still work or does it blow that away?23:42
bigjoolsat enlistment I mean23:43
roaksoaxbigjools: blown away23:43
bigjools:(23:43
roaksoaxbigjools: so ipmi basically manages user as User3, User4, etc etc23:43
bigjoolsthis means accidental pxe boots destroy BMC creds23:43
roaksoaxbigjools: well during enlistment we create maas-commissioning, which is then replaced by 'maas' during commissioning23:44
roaksoaxbigjools: but that's only for User323:44
bigjoolsroaksoax: did you see my bug about the 0.0.0.0 address?23:44
roaksoaxbigjools: nope, bug #?23:45
bigjoolshttps://bugs.launchpad.net/maas/+bug/106422423:46
ubot5Ubuntu bug 1064224 in MAAS "IPMI detection ends up with power_address of 0.0.0.0" [Critical,Incomplete]23:46
* bigjools brb23:47
roaksoaxbigjools: uhmm was it originally set to Static? if so, and the script changed it to DHCP then it might be due to it didn't wait enough time23:48
roaksoaxotherwise, it seems to not be getting an IP address of time23:49
bigjoolsroaksoax: no it was always DHCP - it recently stopped getting an address23:54
bigjoolsand now I can't access it at all of course23:54
bigjoolsthe dhcp server does a DHCPOFFER and the BMC just keeps doing DHCPDISCOVER23:54
roaksoaxbigjools: are these the MicroServer robbie had?23:54
bigjoolsyeah23:55
bigjoolswas working fine last week :/23:55
roaksoax bigjools did you delete the admin/password?23:55
roaksoaxthe user admin with password password?23:55
bigjoolsthe commissioning code may have, I don't know23:55
roaksoaxbigjools: nope, it doesn't23:55
bigjoolswell that's good :)23:55
roaksoaxthe commissioning code uses User3 while the MicroServer were configured on User2 i think23:56
bigjoolsroaksoax: how does this help me make it get an IP? :)23:57
roaksoaxbigjools: you might wanna try doing this: sudo bmc-config --commit --key-pair "Lan_Conf:IP_Address_Source=Static"23:57
roaksoaxand then23:58
roaksoaxsudo bmc-config --commit --key-pair "Lan_Conf:IP_Address_Source=Use_DHCP"23:58
roaksoaxthat should reset the card and should try to DHCP again23:58
roaksoaxbigjools: if the card is already DHCP the cscript wont mess with it23:58
bigjoolsokay, let me try23:58
bigjoolsit is dhcp for sure, I can see it discovering23:59

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