/srv/irclogs.ubuntu.com/2019/03/19/#ubuntu-server.txt

tinoco.00:48
=== ykarel is now known as ykarel|afk
=== ykarel|afk is now known as ykarel
cpaelzerkstenerud: ping me for your build issues when you are arund06:10
cpaelzerkstenerud: they are odd to be sure, but we need to get them unblocked so give me a ping to talk about them06:11
lordievaderGood morning07:23
kstenerudcpaelzer: ok. This build got stuck. I left it overnight and now it's a repeat of the other build07:45
kstenerudsuccessful build yesterday with only i386 and amd64 enabled: https://launchpad.net/~kstenerud/+archive/ubuntu/disco-php7.2-testing/+build/1650809807:46
kstenerudlater build of the same thing (different version in changelog but no other changes), with all archs enabled: https://launchpad.net/~kstenerud/+archive/ubuntu/disco-php7.2-support-new-libicu/+build/1650893307:46
kstenerudI don't know how the lp build system works internally, but from the log comparison, they're doing what looks like the same thing right up until that one test hangs07:48
kstenerudso something is interfering between parallell running tests?07:48
cpaelzerkstenerud: there is nothing interefering between the different arches08:01
cpaelzerkstenerud: they are on different VMs which are on different hosts - they only get together again when their results are collected08:02
cpaelzerkstenerud: I'd think it was a red herring that it worked when not having the other architectures enabled08:02
kstenerudOK, I've queued up exactly the same .changes file that failed yesterday, to a new ppa: https://launchpad.net/~kstenerud/+archive/ubuntu/support-new-icu-amdonly08:05
cpaelzerkstenerud: not for now but please do note that even in the "good" case there are 301 failed unexpectedly08:08
cpaelzerit seems not to gate on those tests (probably because they failed all the time)08:08
cpaelzerbut then it is even more painful that a failing test now kills your build08:09
cpaelzerat some point those should be cleared to either work or be masked out from testing - and then those tests should be made gating IMHO08:09
cpaelzermaybe nacc has looked at that in the past and can share some thoughts on that with you kstenerud08:09
cpaelzerkstenerud: I see no tests at all in https://buildd.debian.org/status/fetch.php?pkg=php7.3&arch=all&ver=7.3.3-1&stamp=1551993939&raw=0 - do you happyn to know why?08:10
kstenerudno08:11
cpaelzerah that was arch all08:13
cpaelzerkstenerud: it is failing there "to the same amount" https://buildd.debian.org/status/fetch.php?pkg=php7.3&arch=amd64&ver=7.3.3-1&stamp=1551996189&raw=008:14
cpaelzerok that aside, I don't know enough about it to discuss why it is that way08:14
cpaelzerkstenerud: but back to your case08:14
cpaelzerkstenerud: do you have a second failing build log please?08:14
kstenerudhttps://launchpad.net/~kstenerud/+archive/ubuntu/disco-php7.2-fix-005008:16
kstenerudWith what I'm building now, it fails at test 3443. That other log gets well past that08:19
cpaelzerkstenerud: yep I've seen it08:19
cpaelzerkstenerud: the test is an intentional crash "Crash when file pointers passed to curl are closed before calling curl_multi_exec"08:20
cpaelzerkstenerud: my assumption is that there is a race that this kills the test runner instead of the epected test binary or so08:20
cpaelzerkstenerud: I'm reading through d/rules and the source how the tests work in general08:20
cpaelzerif you have 2.4k skipped tests and ignore 310 really failing ones we can as well eliminate this problematic single case and be good with it08:21
kstenerudyeah. Also that test isn't intentionally crashing. It's testing that PHP handles it by falling back to stdout08:23
kstenerudA test from 2009: https://bugs.php.net/bug.php?id=4820308:24
kstenerudThe test itself looks pretty benign. Unless maybe the broken pipe is stalling the entire process?08:25
cpaelzerkstenerud: it would be nice to resolve this for real, but that might be better with your php7.3 work next cycle08:27
cpaelzerkstenerud: for now lets cut that test out and see if it makes the build reliable - as it works "sometimes" we at least know it is not generally failing08:27
* cpaelzer sigh08:27
cpaelzerkstenerud: in d/rules they skip whole modules, but I'd not want to skip all other 227 tests of curl (even though sicne the build ignores failures the worth is to debate)08:28
cpaelzerkstenerud: instead you could just patch our the ext/curl/tests/bug48203_multi.phpt file08:28
kstenerudyeah, looks like it just blindly runs whatever's in the dir08:28
kstenerudso we'd have to patch it out08:28
cpaelzerexactly08:28
cpaelzerkstenerud: once you have done that throw it in three PPAs at once, if 3/3 build fine lets review and upload that before freezes hit us08:29
kstenerudok08:29
cpaelzerkstenerud: for 7.3 I'd ask you to NOT retain this change on the Merge and have a look again there08:29
kstenerudIt'll be a separate patch file that we can just drop08:29
cpaelzeryes08:30
cpaelzerkstenerud: mention that it is supposed to be dropped int he dep3 header please08:30
kstenerudok08:30
cpaelzernice, I filed a Debian bug and someone subscribed to the package has a https://bitbounce.com/?ref=bitbounce blocker set up08:33
cpaelzer0.90$ to deliver the email, no thanks08:33
kstenerudYup, the test hung again: https://launchpad.net/~kstenerud/+archive/ubuntu/support-new-icu-amdonly/+build/1651171208:50
kstenerudOK, starting 3 new builds with the test disabled...08:50
=== Wryhder is now known as Lucas_Gray
rbasakcpaelzer: I'm not sure if I pinged you about this previously. I'm just clearing out an old card left over from an old triage session. Bug 1817027 needs a response I think, because the reporter did what you said and changed the bug status back to New.11:29
ubottubug 1817027 in samba (Ubuntu) "samba crashes when uploading files" [Undecided,New] https://launchpad.net/bugs/181702711:29
rbasakBut I'm not sure quite how to respond.11:30
=== Wryhder is now known as Lucas_Gray
cpaelzerrbasak: reading ...11:35
rbasakSorry I should have followed up on this earlier11:36
rbasakNo rush now though11:36
cpaelzerrbasak: I need a brain break from MIRs anyway I'll take a look11:44
cpaelzeralso doko was so kind to suggest others might take over some MIRs, so I'm living in hope for ~3h that I don't have to do them all11:44
cpaelzerhi lagarcia, are you around enough that I might ask you some ppc kvm questions?11:48
cpaelzerrbasak: bug 1817027 is answered, it was straight forward debugging but ended up in too special samba-foo12:37
ubottubug 1817027 in samba (Ubuntu) "samba crashes when uploading files" [Undecided,New] https://launchpad.net/bugs/181702712:37
cpaelzerrbasak: but I think I got the case one step further and we can wait if the reporter is willing to move it to an upstream bug discussion12:37
cpaelzerahasenack: ^^ if you want to take a look as well if it is a known case to you12:38
ahasenackdoesn't ring a bell12:40
ahasenacksamba 4.10.0 final was released today, btw12:40
ahasenackI need to update disco12:40
ahasenackstrlen on a null pointer?12:42
ahasenackwhich happens to be a password12:42
rbasakcpaelzer: thank you for taking care of it!12:55
rbasakI closed my Trello card. If he responds it should come up in triage again12:55
ahasenackcpaelzer: I reopened the zeromq ftbfs mp, and with some questions at the end13:00
cpaelzerahasenack: reading the zmq MP after I completed some tests on a qemu case I'm on13:03
ahasenackok13:04
kstenerudwoohoo! php7.2 works!!! MP submitted13:20
cpaelzerkstenerud: could you abandon the old MP pelase13:23
kstenerudsure13:24
ahasenackrbasak: samba 4.10.0 final is out, what should I call our version/tarball: 4.10.0+dfsg (what debian would call it), 4.10.0~dfsg (so we can "upgrade" to 4.10.0+dfsg when debian releases it?), or something else?13:25
cpaelzerahasenack: last time you had a dfsk-ubuntu something version (I remember because I complained about it being so long)13:26
cpaelzerahasenack: what became of that string for the tarball?13:26
ahasenackcpaelzer: yeah, I dropped that, it became 4.10.0~rc4+dfsg13:26
ahasenackI thought the risk of conflicting with debian was minimal at that stage, and I new a final release would still come13:27
ahasenackso I postponed that question to now :)13:27
ahasenackwhat will happen in LP when we create a 4.10.0+dfsg orig tarball, and debian creates one slightly different (diff md5), and launchpad tries to ingest it?13:27
ahasenackwould it reject it, like it does when we upload a tarball with same name but different content?13:28
cpaelzerinteresting thought, I don't want to find out as that smells like trouble13:28
ahasenackwith 4.7.6, the last time we went ahead of debian, I used samba_4.7.6+dfsg~ubuntu.orig.tar.gz13:29
cpaelzeryeah why not that again13:30
ahasenackI assumed you wouldn't like the long name :)13:30
cpaelzeras I said, I dislike that it has ubuntu in the version twice then eventually13:30
cpaelzerbut not knowing a better solution I'd at least stay consistent to last time then13:31
ahasenackwhat about ~dfsg? I haven't seen that before, I just made that up13:31
ahasenackor +dfsg~113:31
ahasenackno ubuntu13:32
cpaelzerand shorter13:32
cpaelzerI don't know, we need people to chime in that did such things more often13:32
ahasenackhm13:33
ahasenackii  ghostscript                                9.26~dfsg+0-0ubuntu0.18.04.7                 amd64        interpreter for the PostScript language and for PDF13:33
* ahasenack checks that one13:33
ahasenacknah, came from debian already (the ~dfsg)13:34
fricklerjamespage: coreycb: I'm still seeing messages in syslog like in this bug, not only for designate but also other services. the reason seems to be that the dh_systemd helper actually generates pretty messed up service definitions https://bugs.launchpad.net/charm-designate/+bug/1782644 http://paste.openstack.org/show/748022/13:41
ubottuLaunchpad bug 1782644 in OpenStack Designate Charm "Charm blocked on designate services with Runtime directory is not valid reported in syslog" [Medium,Fix released]13:41
coreycbfrickler: is the package in need of permissions changes?14:20
fricklercoreycb: no, this has nothing to do with permission IIUC, the "*Directory" stanzas in the systemd .service file are just bogus, see the paste14:21
coreycbfrickler: ok yeah RuntimeDirectory doesn't look valid. it's possible that's an issue with openstack-pkg-tools.14:27
fricklercoreycb: actually this is valid, but I had to look up the docs, too. arguments is "a whitespace-separated list of directory names" https://www.freedesktop.org/software/systemd/man/systemd.exec.html14:28
frickleralso the service manager should create these dirs if they don't exist14:29
fricklerso actually I'm back to not being sure yet what's wrong with it14:30
coreycbfrickler: ok i'll target that at the designate package for now as well14:30
fricklercoreycb: hmm, I'm now assuming that systemd on xenial is too old and doesn't support these features14:44
lordcirthfrickler, coreycb Added RuntimeDirectory was added in systemd 211 https://github.com/systemd/systemd/blob/master/NEWS#L615714:46
lordcirthMy xenial container here is 22914:46
lordcirthHowever, more features were added to it later14:46
fricklerlordcirth: thanks, I've been trying to find that. the version in xenial seems to support RuntimeDirectory, but only a single one, and also no CacheDirectory14:47
fricklerthe latter comes in with 23514:51
lordcirthfrickler, indeed. What do you need cachedirectory for?14:52
fricklerlordcirth: I don't necessarily need it, the systemd helper writes it into the service definition, causing errors in syslog on daemon-reload. this is for openstack packages, but probably others14:54
jamespagecoreycb: flooding stein-proposed from stein-staging14:55
lordcirthfrickler, ah, I see. This is a new system just for openstack? Why not run 18.04?14:55
jamespagecoreycb: last few snapshots are working their way through - octavia and networking-ovn will block until we get octavia-lib14:55
jamespageI might wedge that into stein-staging for now14:55
fricklerlordcirth: we are migrating to that, but UCA packages are intended to run fine on 16.04, too14:55
fricklerjamespage: coreycb: actually the tool in question is pkgos-gen-systemd-unit from openstack-pkg-tools , so that's a pure openstack-internal problem probably14:58
jamespagefrickler: so that issue is from xenial-queens?14:59
* jamespage reads backscroll to catchup15:00
fricklerjamespage: yes, the tools generates service definitions that would need systemd >=235, but xenial has 22915:01
=== dpawlik is now known as dpawlik_
=== lotuspsychje_ is now known as lotuspsychje
jamespagecoreycb: have you seen a tempest failure on tempest.api.identity.v3.test_domains.DefaultDomainTestJSON.test_default_domain_exists ?17:11
jamespagepermission denied - I think its a change in tempest which requires a cloud level admin permission17:11
coreycbjamespage: yes but have not dug into it yet. i think admcleod may have.17:12
coreycbjamespage: i'll look today. i'm going to test rocky sru's.17:12
jamespagecoreycb: okies17:12
jamespagecoreycb: was doing some bionic/queens catchup for ceph17:12
jamespagecoreycb: documented the failure here - https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1813807 but detailed it was unrelated to ceph17:13
coreycbjamespage: ok great17:13
ubottuLaunchpad bug 1813807 in Ubuntu Cloud Archive pike "[SRU] ceph 12.2.11" [Medium,Triaged]17:13
rbasakahasenack: I would just call it what Debian would call it.17:13
ahasenackrbasak: ok17:13
rbasakahasenack: but probably should check with #ubuntu-devel or the security team if there's something else special done for that case17:13
ahasenackrbasak: emailed17:19
rbasakcpaelzer: did you get any guidance on your custom maintscript handling in https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/364760 from anywhere?17:33
rbasakOr should I just review from the perspective of it having been written from scratch?17:33
ahasenackrbasak: I got this ping from him earlier: <cpaelzer> andreas-lunch: check /usr/bin/dpkg-maintscript-helper sa it is copy and modified from there17:38
rbasakahasenack: cpaelzer: https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/364760 reviewed but it looks like I ended up grabbing the ~canonical-server review slot and can't create it again.17:57
rbasak(as I'm not a member of ~ubuntu-virt)17:57
ahasenackthanks for reviewing it17:58
jamespagecoreycb: ok stein proposed is baking - I'll test first thing tomorrow17:58
jamespageI've shimmed in octavia-lib for now pending aa acceptance17:59
coreycbjamespage: great, sounds good17:59
jerichowasahoaxWhy am I getting "Fatal: Can't create directory /var/run/dovecot/login: Permission denied" even after running chmod -R 777 /var/run21:58
jerichowasahoax18.0421:58
sarnoldfirst things first, double-check that's a symlink to /run22:00
jerichowasahoaxsarnold: yes22:00
sarnoldnext, set /run back to 755.22:00
jerichowasahoaxsarnold: done. dovecot still does not start.22:01
sarnoldalright, cool. what's /run/dovecot's owner:group and permissions?22:02
jerichowasahoaxsarnold: dovecot:dovecot22:02
sarnoldsigh. why don't more programs give instructions about the owner, group, and permissions?22:13
sarnoldjerichowasahoax: what permissions does that have? I think it's supposed to be 75522:14
jerichowasahoax75522:15
sarnoldhmm. alright .. how about /run/dovecot/login ?22:16
jerichowasahoaxsarnold: doesn't exist22:16
sarnolddoes ls -ln on these directories show the same numeric userid as ps auxwn ?22:16
sarnold.. or the numeric number that *would* be used if they started? heh22:17
jerichowasahoaxsarnold: i'm *assuming* if a dovecot user exists then dovecot would be started as that user, given that this kind of work is generally handled by apt, yes?22:19
jerichowasahoaxor, rather, by the package maintainer22:19
jerichowasahoaxbecause i didn't compile this package by hand or anything22:19
sarnoldjerichowasahoax: yeah, that's my hope too. but if there's two users with the same name and different numbers, you'll get errors that are nearly impossible to track down without ls -ln :)22:21
jerichowasahoaxsarnold: grep dovecot /etc/passwd returns only one user22:22
jerichowasahoaxsarnold: who's UID matches that listed by ls -ln22:23
sarnoldjerichowasahoax: alright hmm22:32
sarnoldjerichowasahoax: how about any DENIED messages in dmesg or auditd logs?22:32
jerichowasahoaxsarnold: https://paste.ubuntu.com/p/RNZwRsNnSm/22:34
sarnoldcuuuuuuuute22:35
jerichowasahoaxsarnold: is this some new-to-bionic thing? this all happened after a dist-upgrade from xenial22:36
sarnoldjerichowasahoax: do you have any /etc/apparmor.d/usr.sbin.dovecot*dpkg* files?22:38
jerichowasahoaxsarnold: i have /etc/apparmor.d/usr.sbin.dovecot22:39
sarnoldjerichowasahoax: here's the usr.sbin.dovecot profile that I grabbed from the bionic apparmor-profiles package: http://paste.ubuntu.com/p/mn82zMsMGg/22:39
sarnoldit's got both the attach_disconnected flag that should handle the "Failed name lookup - disconnected path" messages22:39
sarnoldand the /{,var/}run/dovecot/** rw,  that should have allowed the mkdir22:40
jerichowasahoaxsarnold: existing file looks like nothing like the one you provided me, doing a complete replacement22:40
jerichowasahoaxsarnold: dovecot still does not start, same error22:41
sarnoldjerichowasahoax: be sure to copy over any local changes to /etc/apparmor.d/local/usr.sbin.dovecot22:42
sarnoldjerichowasahoax: did you reload the profile?22:42
jerichowasahoaxsarnold: why does it have to be in local22:43
sarnoldjerichowasahoax: be sure to run apparmor_parser --replace /etc/apparmor.d/usr.sbin.dovecot22:43
jerichowasahoaxi don't like apparmor22:43
jerichowasahoaxcan i disable it22:43
sarnoldjerichowasahoax: if you edit this file in place, then it probably won't be upgraded in the future22:43
sarnoldwould you mind a half-way step of just apt-get  purge apparmor-profiles? those profiles are less well-tested than the others22:44
jerichowasahoaxsarnold: apparmor-profiles was not installed22:45
sarnoldjerichowasahoax: oh curious. that means the profile came from somewhere else, perhaps someone else on site?22:45
jerichowasahoaxsarnold: only me on site, seems like a remnant from something else22:46
jerichowasahoaxsarnold: apparmor stopped and disabled in systemd. dovecot still does not start.22:47
jerichowasahoaxshould i reformat22:47
sarnoldno22:47
jerichowasahoaxi think the dist-upgrade broke my bo\x22:47
sarnoldapparmor_parser --remove /etc/apparmor.d/usr.sbin.dovecot may help22:47
sarnoldit's possible but most of the rough edges on the upgrades should have been fixed by now22:48
jerichowasahoaxsarnold: apparmor_parser [...] ran. dovecot starts.22:49
jerichowasahoaxi'm kind of distrustful that apparmor profiles are enforced even after stopping apparmor in systemd, but maybe the "start/stop" verbs aren't being used in the way i expect them to be.22:50
sarnoldindeed, 'stop' doesn't unload profiles, because 'start' can't confine already running processes22:52

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