/srv/irclogs.ubuntu.com/2016/10/07/#ubuntu-devel.txt

bluesabrebacklight00:08
bluesabrewoops00:08
rbasaknacc: yes00:17
naccrbasak: ack, will do00:17
rbasakThanks!00:17
naccrbasak: and actally, i'm going to delete the vivid/wily tasks for mysql-5.7, as it doesn't exist there, if that's ok with you? i've never been quite sure on that policy00:19
rbasakDeleting tasks is a little dangerous, as they can't be recreated (Launchpad bug)00:19
rbasakSo I usually use Invalid instead, since I found out about that.00:19
naccrbasak: oh i didn't realize that, as i thought i had recreated them in the past00:19
naccwill just leave at don't fix00:19
nacc*won't00:20
rbasakSure00:20
naccrbasak: if you have the time, i would like to still chat tmrw to talk about the UOS session00:39
rbasaknacc: sure01:04
naccrbasak: thanks01:05
=== JanC is now known as Guest21552
=== JanC_ is now known as JanC
=== salem_ is now known as _salem
pittiGood morning05:02
cpaelzer_good morning05:37
=== cpaelzer_ is now known as cpaelzer
LocutusOfBorgnacc, probably  yes06:13
LocutusOfBorgcoreycb, pandas sync?06:15
LocutusOfBorgnot sure BTW06:15
smbnacc, we could. or are you on that libvirt apparmor one already cpaelzer ?07:15
smbnacc, cpaelzer for xenial the question is whether we want to push things over the current proposed to limit the number of releases07:15
smberm and morning07:16
cpaelzersmb: morning :-)07:26
cpaelzersmb: no deep in qemu atm - no touch on libvirt by me07:26
* smb hands cpaelzer a snorkel07:27
smbcpaelzer, ack, then I will have a look as time permits07:27
cpaelzersmb: if the fix is easy and the current xenial hasn't passed proposed I'm for your suggestion of pushing over the current one07:27
cpaelzersmb: the current one is only the preventive fix for the service names07:27
cpaelzersmb: that one surely can take a sibling I think07:27
cpaelzersmb: otherwise if bigger I'm for "one change at a time"07:28
* cpaelzer is known as snorkler07:28
smbcpaelzer, right, the not shutting down all guests is more annoying that that and the fix is rather simple07:28
LocutusOfBorgnacc, llvm-toolchain-3.7 fixed for powerpc10:20
LocutusOfBorgcaribou, ^^ feel free to steal the patch for 3.610:21
caribouLocutusOfBorg: ok, will look at it10:21
LocutusOfBorglet me know if you upload please10:24
caribounacc: rbasak: LocutusOfBorg has a fix for the powerpc FTBS on 3.7 that I can backport to 3.611:23
caribounacc: rbasak: then Debian has just removed llvm usage from the package until upstream fixes things to use LLVM 3.811:25
caribouhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=83985011:25
ubottuDebian bug 839850 in src:clamav "clamav: FTBFS with LLVM 3.8" [Serious,Fixed]11:25
caribouSo either I upload a new LLVM 3.6, or we just disable LLVM in clamav, & forget about 3.611:25
caribounacc: rbasak: not sure what's the best option now that we're in Final Freeze11:26
=== hikiko is now known as hikiko|ln
rbasakcaribou: thanks! Maybe best to ask the release team?12:06
rbasakcaribou: maybe from an SRU perspective, if it's just the binary name, it'd be better to add a workaround to clamav for that for Yakkety only (and not copy that forward to Z)?12:09
rbasakI don't know what mechanism we might use exactly, but what I mean is the principle that we do the minimal thing for Yakkety now and then fix llvm in Z.12:09
rbasakAnd that minimal thing could be in clamav so as not to risk other packages.12:10
caribourbasak: imho, minimal for Y is to add LocutusOfBorg's two line patch to llvm3.6 to fix the powerpc's FTBS12:10
=== _salem is now known as salem_
caribouclamav remains untouched12:11
rbasakcaribou: is that minimal though? It could impact every SRU as dependent packages are rebuilt.12:11
cariboullvm-toolchain-3.6 builds for all architectures12:11
caribourbasak: according to nacc & my check, only clamav depends on llvm3.612:11
rbasakOh, OK. That's fine then I guess :)12:12
caribourbasak: that being the reason to get rid of it, but now is a bit too late12:12
rbasakYeah.12:12
rbasakIt sounds fine to me then if the release team agree.12:12
caribourbasak: I'll fix that for Z12:12
caribouok, I'll check with them12:12
rbasakThanks again for handling this!12:12
caribouLocutusOfBorg's fix is already in 3.712:13
=== hikiko|ln is now known as hikiko
jamespagepitti, hey - need some help on bug 163132812:38
ubottubug 1631328 in systemd (Ubuntu) "ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"" [Undecided,New] https://launchpad.net/bugs/163132812:38
jamespagewhat's the right way to install a new udev rules file that relies on a user/group that the package maintainer script has not yet created12:38
jamespageit appears the yakkety udev drops that part of the rule when loading them?12:39
pittijamespage: such rules shouldn't be a problem -- we install those all the time, as long as the postinst actually addgroups them12:43
jamespagepitti, it does12:43
rcjX on yakkety with two displays is giving me an area that acts like a hall of mirrors12:43
jamespagepitti, but I'm def seeing the behaviour I think I am12:44
jamespagepitti, udev complains about the missing user/group12:44
jamespageabout 2 seconds before they are created12:44
jamespageand then block devices don't get the correct perms (ceph/ceph) until I do a restart or reload of udev12:44
pittijamespage: yes, I figure it picks up the new rule during unpack via inotify12:44
jamespagethat was my guess12:45
pittijamespage: your postinst needs to udevadm trigger those after group cretion12:45
pittibut it seems it already does?12:45
* jamespage looks12:45
jamespageI don't think so12:45
pittijamespage: merely installing an udev rule also doesn't actually do anything -- in order for them to get active the device needs to get removed/added or udevadm triggered12:46
pittijamespage: oh, I thought because you said so in #812:46
jamespagepitti, yeah I know that - the charm does that bit once its configured with block devices etc...12:46
jamespagethe charm does a udevadm trigger to make udev pickup disks its just prepared for use12:46
jamespagethe trigger is firing, but the perms are not applied12:46
jamespageso its kinda like an incomplete rule application12:47
jamespagepitti, I guess a fix is to reload the udev daemon in the postinst script12:47
pittijamespage: udevadm control --reload?12:48
pittijamespage: could work, yes, if that's a race condition12:48
pittiit only auto-updates via inotify every 5 seconds or so, to avoid bursts12:48
jamespagepitti, its def a race condition12:49
jamespageits a shame that when udev does not detect a user/group, it just sets up the rules partially12:50
jamespagethat feels a bit odd12:50
pittijamespage: it's actually odd that it runs the rules at all during package installation12:53
jamespagepitti, its not12:54
pittinormally that doesn't wiggle devices12:54
jamespagepkgs installed, charm configures block devices, then triggers the udevadm trigger12:54
jamespagepitti, my issue is that the rule gets partially loaded due to the race with user/group setup12:55
jamespagepitti, http://paste.ubuntu.com/23288779/ look ok?12:56
pittijamespage: that's after the addgroup?12:56
jamespagepitti, addgroup is done in ceph-common, rule is installed in ceph-osd12:56
jamespageceph-osd -> ceph-base -> ceph-common12:57
pittijamespage: well, still needs to be "after" -- if ceph-osd depends: ceph-common that's also fine12:57
jamespageso it should happen that way12:57
coreycbLocutusOfBorg, looking at pandas13:15
coreycbLocutusOfBorg, synced, thanks for the nudge13:20
LocutusOfBorgthanks13:29
=== jgrimm is now known as jgrimm-out
naccsmb: cpaelzer: yeah, i trust your judgment(s)14:42
naccLocutusOfBorg: ack (re: powerpc fix)14:43
nacccaribou: ack on fixing powerpc for now and removing the dep in Z14:43
caribounacc: I'm on it; will upload early monday morning unless the release team tells me otherwise14:44
caribou(or before eod if they ping me)14:44
nacccaribou: great, thanks for following up on it!14:44
cpaelzernacc: it is scary you trust me and I don't even remember what I wrote14:51
* cpaelzer reading back14:51
nacccpaelzer: re: libvirt fixes and whether to combine more into -proposed14:51
cpaelzernacc: ah yeah, I already discussed on this and more with smb - good for now14:52
nacccpaelzer: thanks!14:52
cpaelzernacc: I debugged and triaged a bug we had, but we decided to postpone until after release14:52
cpaelzernacc: so it got to the backlog with some extra info14:52
smbnacc, cpaelzer yeah ... actually its alrady uploaded now14:52
cpaelzersmb: thanks14:52
naccsmb: thanks!14:52
smbcpaelzer, Oh to clarify, nacc mentioned different messages of apparmor which I could not reproduce at all. For those I asked in the bug report for confirmation they are not gone for other reasons. The one we looked at are new to yakkety while the other ones were in Xenial14:57
nacccpaelzer: it was just another libvirt bug in the server-next queue14:58
pitticyphermox: do you have some time or know someone to verify bug 1592721?15:41
ubottubug 1592721 in network-manager (Ubuntu Xenial) "Don't write search domains to resolv.conf in the case of split DNS" [Medium,Fix committed] https://launchpad.net/bugs/159272115:41
cyphermoxok15:41
pittiit's otherwise ready to release15:41
cyphermoxyep15:41
=== frickler_ is now known as frickler
tsimonq2pitti: you mentioned a quote in the last foundations meeting (yes I read those :P) stating something like "if it17:21
tsimonq2argh I hate this enter key placement!17:21
tsimonq2"if it's hard, do it more often"17:21
tsimonq2pitti: where did you find that? :P17:21
tsimonq2pitti: or is that your quote? I was just wondering because it was in quotation marks17:22
chilukcyphermox: looks like a regression on your most recent update to initramfs-tools..https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/163147418:53
ubottuLaunchpad bug 1631474 in initramfs-tools (Ubuntu) "No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option" [Undecided,New]18:53
pittitsimonq2: I think it's a Google motto19:22
pittitsimonq2: but I really like it19:22
=== xclaesse` is now known as xclaesse
=== zigo is now known as Guest10079
slangasekchiluk: LP: #1631474 : you may want to also sync with lamont on this19:34
ubottuLaunchpad bug 1631474 in initramfs-tools (Ubuntu) "No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option" [Undecided,In progress] https://launchpad.net/bugs/163147419:34
chilukslangasek ok .. at the moment, I'm just tryign to understand what the user is attempting to accomplish with ip=dhcp ... perhaps they are using a nfs root?19:34
chilukI don't know just yet.19:34
chilukslangasek I'll drive it for the time being.. it looks like a fairly straightforward bash change.19:35
slangasekchiluk: ok19:35
chilukI just need to figure out what's not exactly working19:35
pittibdmurray: can http://launchpadlibrarian.net/275354292/update-manager_1%3A16.10.2_1%3A16.10.3.diff.gz be changed to not pull in the whole python3-launchpadlib stack into standard? (http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt)19:35
slangasekchiluk: there's mention in the bug of AWS, which is a particularly strange place to be doing nfs or iscsi root, I would think19:36
cyphermoxwell, it's really broken anyway19:36
chilukyeah that's my thought as well. and that is correct it is in aws19:36
pittibdmurray: like, dropping it to a Suggests: and gracefully not doing PPA changelogs if the module doesn't exist, or doing REST calls with urllib?19:36
slangasekcyphermox: what's really broken?19:36
cyphermoxthat logic there in initramfs -- I see exactly what's wrong19:36
cyphermoxwe don't skip on, all, and dhcp when parsing IP19:37
chilukyeah the device isn't getting declared explicitly?19:37
cyphermoxchiluk: well, klibc had a mess of different options differently configured19:37
pittiinfinity: ah, perl is being dragged in by the new  "rename" -- that seems awfully heavy too19:38
cyphermoxdo basically the if there that looks if ip= contains BOOTIF needs to not run if ip = (dhcp|all|on)19:38
cyphermoxs/all/any/19:38
chilukah ok.19:39
pittiinfinity: which is not seeded and purges without issue in a VM, and is by itself just a recommends of perl -- WTH19:39
chilukcyphermox: want me to punt it back to you?19:39
cyphermoxchiluk: well if you want to do it, feel free, or I can fix it myself19:40
cyphermoxit needs a fix in both xenial and yakkety19:40
chilukcyphermox you would likely end up sponsoring the upload anyways.19:40
cyphermoxwell, you could get one more sponsored upload I can vouch for ;)19:41
cyphermoxI don't mind either way19:41
chilukalrighty.. I'll do the legwork then.19:41
chilukI really could use the uploads ..19:41
chilukit might take me a little longer than you to fully wrap my head around what this awesome bash script is doing.. but this is a good opportunity to spread the expertise.19:46
=== Guest99384 is now known as Zic
=== wendar_ is now known as wendar
tsimonq2pitti: cool :)20:04
=== giraffe is now known as Guest34241
smosercyphermox, around ?20:07
smoserpokign aroudn with open-iscsi and such.20:07
smoseri launch a vm with a nick on a lxdbr0 and then run20:08
smoserhttp://paste.ubuntu.com/23290520/20:08
=== beisner- is now known as beisner
cyphermoxsmoser: seems to me like a badly configured dhcp server?20:13
smoseris it expected that dhclient use 'ip' from busybox ?20:15
cyphermoxyes, that's fine20:15
smoserwell, dhcp server is configured by lxd20:17
smoserhttp://paste.ubuntu.com/23290551/20:17
smoserand stgraber says it should work20:17
cyphermoxare there free IPs?20:18
cyphermoxwhat packets go through?20:18
cyphermoxtbh there is nowhere near enough information there to know what is wrong, but it's not likely because of which /bin/ip we use20:18
=== sunweave1 is now known as sunweaver
smoseri'm trying to do ipv6 dhcp20:20
smoserso probably20:20
smoserand there are 2 hosts on that network20:20
cyphermoxsmoser: well, we do exactly that to deploy maas instances in an ipv6 only network and it works20:21
cyphermoxlamont: ideas?20:21
smosercyphermox, well, "works" is a bit of a strong word. :)20:22
cyphermoxit *works*20:22
smoserlamont has been strugging with it for quite a while20:22
cyphermoxyeah, there's various pieces into that, not just dhcp.20:22
lamontsmoser: initramfs-works.20:22
lamontshutdown later doesn't20:22
=== arlen_ is now known as arlen
=== xnox_ is now known as xnox
lamontin that it shuts down the interface whjere the root disk lives20:23
=== Darcy is now known as Spydar007
lamontwhich could ultimately be an initramfs-tools bug, but it's not a configuration bug20:23
=== balkamos_ is now known as balkamos
lamonthaving said that, bridges and ivp6 address diescovery have their moments... since they "optimized" the bridge code to not forward multicast packets taht weren't "needed", and having that on has caused great pain with ipv6 address discovery for me.20:24
lamontsmoser: packet traces are a very good start for figuring out what is happening with dhcp20:25
smoser http://paste.ubuntu.com/23290593/20:26
lamontsmoser: . /lib/functions (or such) and run configure_networking() ?20:27
smoseryeah, i can try.20:28
smoserso fyi, i run: dhclient -6 -d -v eth020:28
smoserit errors like in20:28
smoserhttp://paste.ubuntu.com/23290520/20:28
smosersecond time, it actually tries to do something20:28
smoserbut still fails20:28
smoserso it surely seems to me that the 'ip' that is causing garbage was bringing the interface up20:29
smoserwhich seems important.20:29
lamontsmoser: the code that actually runs in the initramfs is: . /scripts/functions; configure_networking20:31
lamontand that code works20:31
smoserwell, that fails the same way for me.20:32
lamontand what do the packet traces look like?20:32
smoser message status code NoAddrsAvail: "no addresses available"20:32
smoserstgraber, ^20:32
smoser"NoAddrsAvail:"  ?20:32
lamonttcpdump -ni any por5 54720:32
lamontonly without the typo20:33
jderosecyphermox: bah, your initramfs-tools update for xenial broke some of my PXE boot related tooling :P still digging into the details, not yet sure if it's fragile assumptions on my end or a bug on your end... will let you know21:08
jderosebut the symptom is a kernel panic when trying to PXE boot21:08
cyphermoxjderose: there is a bug21:11
cyphermoxI bet your PXE deployments pass ip=dhcp21:11
jderosecyphermox: have the # or link handy?21:11
jderosecyphermox: yes, indeed it does21:11
=== kitterma is now known as ScottK
cyphermoxhttps://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/163147421:12
ubottuLaunchpad bug 1631474 in initramfs-tools (Ubuntu) "No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option" [Undecided,In progress]21:12
cyphermoxentirely my fault, I derped there adding the logic to parse BOOTIF.21:12
cyphermoxchiluk is working on the fix and I'll sponsor it as soon as it's ready21:12
jderosecyphermox: happens to everyone, no worries :)21:13
cyphermoxit's kind of crippling ;)21:13
chilukyeah I'm finding some other issues as well while I look through the code.21:13
jderosecyphermox: also, if you ever have a proposed package with PXE boot related changes... i'm always happy to test, feel free to ping me anytime :)21:13
chilukjderose can you add your /proc/cmdline to the bug and paste it here as well21:14
chilukso I know how people are using this.21:14
chilukthanks.21:14
chilukI'm trying to make sure all cases get covered.21:14
jderosechiluk: yup, will do21:14
jderosechiluk: done21:17
chilukcyphermox: for example if ! echo "${IP}" | grep -qc 'BOOTIF'; then  will always return true regardless21:17
chilukjderose: would you be willing to test an updated initramfs-tools for me shortly?21:28
jderosechiluk: yup, absolutely! prefer a ppa, but i can manage a deb too, will just take a bit more hacking around (my tooling doesn't make debs especially easy)21:32
chiluksure I'll create a ppa ..21:32
chilukone sec.. I'm trying to test it myself and the deb is failing to install ..21:32
chilukwhich is strange.21:32
jderosechiluk: awesome, easy peasy then21:32
cyphermoxchiluk: what?21:36
jderosechiluk: oh, for completeness here and not just in the bug, my current cmdline is something like: initrd=initrd.img-4.4.0-36-generic root=/dev/nfs nfsroot=10.17.76.1:/var/lib/tribble/ephemeral ip=dhcp ro nomodeset net.ifnames=021:36
chilukcyphermox: the IP variable should never contain BOOTIF21:37
chilukso the grep will always fail so the if will always be true21:37
cyphermoxthat's not true21:37
cyphermoxthe IP variable totally can and does contain BOOTIF sometimes21:38
cyphermoxBOOTIF == whatever interface teh system used to boot with21:38
chilukcyphermox does dash support ;& fall-through syntax?21:39
cyphermoxI do not know21:39
chilukit looks like a no.. which pisses me off21:40
chilukwhy aren't we just using bash..21:40
jderosechiluk: not sure if it will be helpful, but i rather recently discovered https://www.shellcheck.net/ and it's kinda badass :)21:41
cyphermoxchiluk: http://paste.ubuntu.com/23290876/21:43
cyphermoxshould be sufficient afaik21:43
chilukcrap cyphermox that's finding a world of bugs on just this one area.21:44
cyphermoxoh, looking for on should be strict, in case we ever have devices that start in on ;)21:44
cyphermoxI'm going to have to come back later, I have a dinner planned tonight21:45
jderosecyphermox: enjoy, thanks for the quick response!21:46
chilukok cyphermox... I'll put together a patch and ppa and get that out to folks as soon as I'm happy21:46
=== ochosi_ is now known as ochosi
chilukmy kingdom for full bash interpretter instead of fricking dash.22:02
chilukI'm trying to make things pretty here.22:02
ScottKinfinity: Kubuntu would like to get a security fix in before release:   https://anonscm.debian.org/git/pkg-kde/frameworks/kcoreaddons.git/commit/?id=ab7258dd8a87668ba63c585a69f41f291254aa4322:18
infinityScottK: Security fixes welcome.22:19
ScottKK. Thanks.22:19
=== bdmurray_ is now known as bdmurray

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