[00:03] <ikonia> what's up now dolphin-man ?
[00:03] <dolphin-man> oops
[00:03] <dolphin-man> sorry i meant to join #ubuntu-irc
[00:03] <ikonia> no problem
[10:12] <reisio> bazinga!
[10:13] <k1l> hi reisio
[10:13] <reisio> hiyo
[10:15] <k1l> how can we help you?
[10:16] <reisio> meeting bazhang
[10:16] <ikonia> reisio: do you have a moment ?
[10:17] <reisio> yup
[10:17] <ikonia> I just wanted to clarify something after you've been ranting about being banned for saying clamav is an anti-virtus
[10:17] <ikonia> I think you know that wasn't the case, but I wanted to clarify
[10:17] <reisio> you wanted to clarify that you thought that, or something else?
[10:18] <ikonia> you where banned because you where not offering help - the guy in question wanted to scan his system for linux virus's - you kept telling him clamAV - which wasn't what he needed or wasn't going to solve his problem
[10:18] <reisio> I could get my log, but IIRC the guy sent a smiley face? He was quite satisfied
[10:18] <ikonia> yes, he was, with the wrong information
[10:18] <reisio> wrong? :)
[10:19] <ikonia> that was the point
[10:19] <reisio> did he not ask for an antivirus application?
[10:19] <ikonia> yes, but it wouldn't help him
[10:19] <reisio> why wouldn't it?
[10:19] <reisio> it's what he asked for
[10:19] <ikonia> how is clamav going to help him scan his linux system for linux virus ?
[10:19] <reisio> by using it
[10:19] <reisio> it's an antivirus, you see
[10:19] <reisio> that's what it does
[10:20] <ikonia> and this is the problem
[10:20] <reisio> what is?
[10:20] <ikonia> I think you know exactly what you are doing
[10:20] <reisio> I think you know exactly what I'm doing, too
[10:20] <reisio> because it's obvious
[10:20] <reisio> because I'm being perfectly rational
[10:20] <reisio> :D
[10:21] <reisio> or at least 99% perfectly
[10:24] <k1l> reisio: i think idleone made it quite clear that your ban will stand for at least 3 month now.
[10:24] <ikonia> hang on
[10:24] <ikonia> (today)
[10:24] <ikonia> bazhang: said he'd pick it up with him
[10:24] <reisio> k1l: he did make that quite clear
[10:24] <reisio> and also what ikonia said
[10:24] <k1l> ikonia: ok
[10:26] <k1l> bazhang: seems afk for now. please come back some time later. we will inform bazhang that you were here and tell him to pm you if he is back on
[10:27] <reisio> I can wait
[10:28] <k1l> please dont idle in this channel here. come back in some time or wait untill bazhang messages you that he is available to solve that issue here in this channel. thank you
[10:31] <reisio> presumably that will serve some codified purpose? Presumably one that is being applied to others here even though it seems not the case?
[10:32] <ikonia> reisio: it's just a simple rule of not idling so that others can use the channel if need be
[10:32] <k1l> reisio: do you have a problem with following rules?
[10:32] <ikonia> reisio: the only guys idling are on the ops team, nothing hidden or coded,
[10:32] <ikonia> it's in the topic,
[10:33] <k1l> because showing you have a problem with following rules will not convince the ops team to lift a ban for a user in the support channel.
[10:33] <ikonia> reisio: it's only to keep the channel clear, nothing else,
[10:33] <reisio> k1l: well I can hardly attempt to prove otherwise now that you've said all that, can I?
[10:33] <reisio> asked a question and got an answer, catch you later
[13:05] <Myrtti> did someone remove the ban then?
[13:05] <ikonia> yes
[13:07] <Myrtti> ok, my brain is shortcircuiting quite badly so I can't see anything
[13:07] <ikonia> there is a comment in BT explaining that I'd removed it
[13:08] <ikonia> (and obviously BT logs me removing it too)
[13:08] <Myrtti> oh yeah, I could've looked from there
[13:08] <Myrtti> silly me
[13:09] <ikonia> (also put a comment in the secret channel explaining this)
  ban removed so soon ikonia ?
[16:20] <ikonia> changed to account based
[16:20] <bazhang> ok thanks
[16:21] <ikonia> he always identified but the BT ip range he uses is huge and changes
[16:21] <ikonia> just seemed a simpler approach
[16:23] <DJones> I'm not sure if that was a script, looked like they joined, did /me is back & lewq lewq and then quit
[16:23] <ikonia> DJones: he knows not to do it now though
[16:25] <DJones> Thats true, the same nick does have a 12 month old entry in BT using a Sky broadband ip for spamming the channel
[17:13] <DJones> Hah. Abolfazl_Olaf Hello everyone, I'm here and ready to DDos..   Is that why his connection was reset by peer a few seconds later
[17:52] <IdleOne> never mind
[17:59] <jrib> can we just get the bots to auto-ban the i am here to ddos phrase...?
[18:00] <IdleOne> idoru can do it
[18:00] <IdleOne> but idoru is not in #ubuntu
[18:01] <IdleOne> floodbots could do it also but LjL is in the mountains, probably not caring about PHP
[20:32] <IdleOne> googanger: you said you wanted to speak to the ops. Please go ahead.
[21:15] <k1l_> AndresSM: hi, can we help you?
[21:15] <AndresSM> oh sorry was just checking if the channel did exist
[21:15] <AndresSM> I'll leave
[21:15] <k1l_> alright :)


[06:01] <menyesg> hi... i understand it's a development channel, therefore I won't ask my very important question :P
[06:01] <menyesg> but do you have any information where should I get help about mdadm on Ubuntu Server 6.10?
[06:04] <spike> menyesg: #ubuntu
[06:04] <spike> there are no difference between mdadm shipped with ubuntu-server or ubuntu
[06:04] <spike> or kubuntu and any other version for what it matters
[06:05] <menyesg> hm, okay thanks... btw, in #ubuntu I did not get answers, but I keep trying
[06:05] <menyesg> thanks anyway
[06:06] <menyesg> have a nice day
[06:06] <menyesg> bye


[15:02] <rvba> roaksoax: Hi Andres… I need to test quite a few things before I can fix bug 1130232.  Do you have the precise django package that we intend to SRU (i.e. the one *without* the genericipaddressfield.diff patch)?  If you don't have it handy, could you please create it… that would help me a great deal.
[15:06] <roaksoax> rvba: howdy!! sure give me a sec
[15:09] <roaksoax> rvba: and re on the comments, yeah I was looking this as a patch because this should only apply to precise, and not quantal :)
[15:09] <roaksoax> but i guess that's clear now
[15:10] <rvba> roaksoax: it is clear.  I'm still a bit unsure what's the best solution… but what's sure is that we will have to carry this damn field one way or another.  I mean in MAAS' code and not as a patch on Django.
[15:10] <roaksoax> rvba: yeah!! it is a blocker for sure! but something needed to be done to satisfy the tech board.
[15:12] <roaksoax> rvba: ok just uploaded to ppa:maas-maintainers/experimental
[15:12] <rvba> roaksoax: thanks a lot
[15:12] <roaksoax> should take a while till it gets accepted, built and released (~20mins)
[15:18] <melmoth> hey http://jujucharms.com/charms/precise/nova-cloud-controller/config does not mention vlanmanager mode for the network
[15:19] <melmoth> does it mean it s not possible to use vlanmanager mode with a maas installed openstack ?
[18:23] <racedo> roaksoax: we are hitting https://bugs.launchpad.net/maas/+bug/1116700
[18:24] <racedo> btw I hope you feel better :)
[18:25] <racedo> any clue what's best if we wanted to stick to maas-developers/stable
[19:17] <roaksoax> racedo: i could make a new release
[19:17] <roaksoax> so you guys using an interface which is different from eth0?
[19:17] <roaksoax> for the PXE booting and it is not generating the CNAME's"?
[19:26] <racedo> roaksoax: yes, thats the problem
[19:26] <roaksoax> racedo: are you hitting this with a costumer?
[19:26] <racedo> we see a name in the maas web ui but it never gets added to the bind zone file
[19:27] <racedo> roaksoax: yes
[19:27] <racedo> we are onsite
[19:27] <roaksoax> racedo: s/costumer/customer
[19:27] <roaksoax> racedo: ok, so I think I can prepare a package with the fix included, but it will take me a few to test it
[19:27] <racedo> so all the nodes that pxe boot from eth0 get added to the dns file after enlisting
[19:28] <racedo> and the node (just 1) that boots from eth1 is not added but we get a name created and shown in the web ui
[19:29] <racedo> roaksoax: ok, thanks for that
[19:29] <racedo> we'll be here (NJ) for the day
[19:29] <roaksoax> racedo: only today?
[19:30] <racedo> roaksoax: today until 6 and tomorrow all day again
[19:30] <roaksoax> racedo: ok cool, so that gives me some time :)
[19:30] <racedo> sure man, no rush :)
[19:30] <roaksoax> racedo: what else would you need? What iLO version are they using?
[19:30] <racedo> 1.33
[19:30] <roaksoax> racedo: ok so old implementation works well then
[19:31] <racedo> but we are hitting some issues with version 1.29 they fail though
[19:31] <racedo> roaksoax: we have ipmi 1.33  working fine and 3 hosts with ipmi 1.29 failing but they will try to upgrade them
[19:32] <racedo> btw we are using ppa:maas-maintainers/stable
[19:32] <roaksoax> racedo: ok, can you manually access IPMI with the maas credentials?
[19:33] <racedo> roaksoax: no, they ping and that's all we get
[19:34] <racedo> we think it's on the nodes' ipmi side
[19:34] <roaksoax> racedo: right, but can you access with admin credentials?
[19:36] <racedo> roaksoax: no, it's stuck, nothing happens, we think it's faulty i'm going to double check
[19:37] <roaksoax> racedo: ok!
[20:00] <racedo> roaksoax: ok they just upgraded the ipmi to 2.66 and this is what happens https://pastebin.canonical.com/85181/
[20:00] <racedo> BMC error
[20:00] <roaksoax> racedo: what about if you use the admin credentials?
[20:05] <racedo> roaksoax: just got the credentials
[20:05] <racedo> it works
[20:05] <racedo> roaksoax: https://pastebin.canonical.com/85182/
[20:06] <roaksoax> racedo: alright, so something is busted in the IPMI creation stuff
[20:06] <roaksoax> racedo: the new precise update should be able to fix that
[20:06] <roaksoax> (i hope
[20:06] <roaksoax> ra	unless you provide me with output of what happened during the enlistment process
[20:06] <racedo> you mean freeipmi-tools pkg?
[20:06] <roaksoax> to see if it was able to successfully detect IPMI
[20:07] <roaksoax> racedo: yeah that might be it, it might have failed
[20:07] <roaksoax> to install
[20:07] <roaksoax> racedo: are you guys using a proxy?
[20:07] <racedo> no
[20:07] <racedo> oh squid-deb-proxy
[20:08] <roaksoax> racedo: right, so you probably need to allow the enlistment/commissioning images to access a proxy
[20:08] <racedo> we got the last version apparently: https://pastebin.canonical.com/85183/
[20:08] <racedo> roaksoax: ok, what would that do?
[20:08] <roaksoax> racedo: yeah but the commissioning images also need proxy access
[20:08] <roaksoax> racedo: give me a sec!
[20:08] <racedo> sure man
[20:11] <roaksoax> racedo: do this: https://pastebin.canonical.com/85185/ and pastebinit for me please
[20:12] <racedo> https://pastebin.canonical.com/85186/
[20:13] <roaksoax> racedo: ok so it seems that the user gets added correctly, but what is not done correctly is to provide a privilege for it
[20:16] <racedo> roaksoax: ok
[20:16] <racedo> and can we set the ipmi to allow it?
[20:16] <roaksoax> racedo: can ytou do something like this? https://pastebin.canonical.com/85187/
[20:19] <roaksoax> and then try to stat the node
[20:19] <racedo> trying hold on  a sec
[20:21] <roaksoax> racedo: ok, so I have a package that I just uploaded to ppa:maas-maintainers/testing that I will test, and then release in ppa:maas-maintainers/stable
[20:24] <racedo> roaksoax: we are reenlisting it now
[20:24] <roaksoax> racedo: cool
[20:25] <racedo> roaksoax: thanks for the package too!
[20:27] <racedo> roaksoax: you fixed it!
[20:28] <roaksoax> racedo: cool!! I wonder why it didn't work out of the box as it should have!
[20:28] <roaksoax> probably due to the older ipmi version
[20:28] <racedo> oh that could be the case
[20:56] <roaksoax> racedo: ok, the package should be published really soon
[20:56] <roaksoax> ~10 mins or so
[20:56] <roaksoax> if not less
[21:04] <roaksoax> racedo: its done! you should be able to upgrade now
[21:18] <racedo> roaksoax: thats awesome!!
[21:18] <racedo> trying it now
[21:27] <racedo> roaksoax: fixed
[21:27] <racedo> roaksoax: many thanks again :)
[21:27] <racedo> roaksoax++
[21:30] <roaksoax> racedo: no probs. just confirm it upgrades and works fine :)
[21:30] <racedo> it has upgraded fine
[21:30] <racedo> and now the host can boot out of eth1
[21:30] <racedo> confirmed
[21:32] <roaksoax> cool