[07:23] <LocutusOfBorg> rbasak, thanks for the ping!
[07:23] <LocutusOfBorg> doko, I got the two fixes for nm wrong output and crashes on 32bit... PR25018 and PR25031... any planned binutils update?
[08:22] <cpaelzer> jamespage: coreycb: thedac: rbasak: does https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/c/cinder/20190924_202508_cfe07@/log.gz ring any bells?
[08:22] <cpaelzer> the qemu upload that triggered the test should have zero impact on this area of your test
[08:22] <cpaelzer> and it seems like some cinder/mysql disagreement
[08:52] <rbasak> cpaelzer: no, but I think we did touch that package during the transition. Is this a missing dependency that has surfaced due to some other change?
[08:53] <rbasak> https://launchpad.net/ubuntu/+source/python%2Dmysqldb is the source package needed I think.
[08:53] <rbasak> And python-mysqldb or python3-mysqldb are the binary packages.
[08:53] <rbasak> Also, this is Disco?
[09:11] <cpaelzer> rbasak: this is disco
[09:11] <cpaelzer> rbasak: not mysql 8
[09:12] <cpaelzer> it is triggered by a qemu SRU which changes nothing that seems related to me (WSL behavior with binfmt)
[09:12] <cpaelzer> you were mostly on "CC" in the highlight above for mysql, I was more waiting on the openstack people if they know anything
[09:19] <rbasak> ack
[09:40] <cpaelzer> rbalint: since systemd 243 is gone from proposed I can't continue all tests
[09:40] <cpaelzer> rbalint: xnox: do you have an eoan PPA with 243 somewhere?
[09:48] <rbalint> cpaelzer, yes. please use https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3801/+packages
[10:06] <rbalint> cpaelzer, when i got 242 migrated i'll also set up one with upstream master snapshot
[10:17] <cpaelzer> thanks rbalint
[10:33] <rafaeldtinoco> good morning all o/
[10:58] <santa_> morning
[10:59] <santa_> rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container)
[11:01] <santa_> I have an explanation and a possible patch for that, let me retest and find all my stuff...
[11:02] <rbalint> santa_, thanks I've opened LP: #1845314 to track that
[11:02] <rbalint> please attach your patch there
[11:03] <santa_> rbalint: cool, I will explain the thing there
[12:04] <coreycb> cpaelzer: is it failing for all architectures? it doesn't ring a bell if it's for disco.
[12:06] <coreycb> cpaelzer: nm that does ring a bell, No module named 'MySQLdb'
[12:12] <coreycb> cpaelzer: i'm not quite sure how we didn't hit that until now but in disco sqlalchemy was updated to default to mysqldb so changes were required to override the driver to use pymysql
[12:12] <coreycb> cpaelzer: so debian/tests/cinder-daemons needs to use mysql+pymysql:// rather than mysql://
[12:15] <coreycb> jamespage: fyi ^
[12:15] <coreycb> sahid: fyi ^
[12:16] <jamespage> yes that's quite astonishing as to why we've not tripped over this already
[12:20] <coreycb> cpaelzer: do you already have a bug open for this?
[12:22] <cpaelzer> coreycb: not yet, I wanted to open it once I hear back from you
[12:23] <cpaelzer> and yes it fails for all arch
[12:23] <cpaelzer> coreycb: I can open a bug for you if you want ...
[12:24] <coreycb> cpaelzer: no worries, i'll get it
[12:24] <coreycb> cpaelzer: will paste here once in progress
[12:24] <cpaelzer> ok, thanks
[12:44] <coreycb> cpaelzer: bug 1845321
[12:46] <cpaelzer> coreycb: thanks
[12:47] <cpaelzer> If there is a blocker that prevents this from being solved soon let me know, we can then force-badtest it for now
[13:00] <coreycb> cpaelzer: i'll get it uploaded today to the disco queue but we are somewhat blocked by current SRUs in proposed
[13:01] <coreycb> sahid: we'll need to get bug 1837905 verified for disco-proposed
[13:08] <coreycb> cpaelzer: once that clears, i will combine the autopkgtest SRU with the SRU for bug 1834845
[13:08] <cpaelzer> ok, thanks for the info coreycb
[13:09] <coreycb> cpaelzer: i'm working on it at https://bileto.ubuntu.com/#/ticket/3813
[13:09] <cpaelzer> I'll copy that to the bug as I know I'll forget ...
[13:24] <sahid> coreycb: the problem is we still do not have that patched merged https://review.opendev.org/#/c/683057/
[13:24] <sahid> so tempest tests are still failling
[13:25] <coreycb> sahid: ok i think we can make an exception for the 2 failing tests since we know why they are failing and it's unrelated to the SRU
[13:25] <coreycb> sahid: we can just note that in the bug when putting [Test Case] results in it
[13:26] <sahid> coreycb: for stein-proposed it's verified, no?
[13:26] <coreycb> sahid: yes but disco-proposed needs verification
[13:27] <sahid> but stein is disco, right?
[13:27] <sahid> i verified for stein (disco) and stein-bionic
[13:28] <sahid> coreycb: ^
[13:28] <coreycb> sahid: maybe it just needs tagging then. disco-proposed and stein-proposed (bionic) need testing
[13:30] <sahid> coreycb: verification-done-bionic (bionic-stein-proposed), verification-done-stein (disco-stein-proposed)
[13:31] <sahid> i updated the bug
[13:32] <coreycb> sahid: cool thanks
[13:35] <tdaitx> Laney: juliank: does autopkgtest infra support the newer restrictions (as in "flaky")? (see https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst)
[13:35] <juliank> hmm
[13:35] <juliank> I'll leave that to Laney
[13:35] <tdaitx> I remember skippable required an infra update
[13:36] <ahasenack> I'm using skippable in ubuntu packages for eoan
[13:36]  * ahasenack just jumped into the channel and saw skippable being mentioned, nothing else
[13:36] <tdaitx> so am I, I am wondering about the newer ones
[13:36] <tdaitx> =)
[13:38] <Laney> yes
[13:38] <Laney> for some value of support
[13:38] <Laney> we need a newer britney to have 'neutral' results properly represented
[13:39] <tdaitx> yeah, there's that
[13:57] <cpaelzer> klebers: I see you retrying http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf recently
[13:57] <cpaelzer> klebers: have you looked deeper into it or filed a bug already?
[13:57] <cpaelzer> otherwise I'd give it a shot myself
[14:11] <klebers> cpaelzer, I have not looked deeper into it. That test is being run on a container, it's not running on the raspi2 kernel, so I did not put effort into investigating it
[14:12] <klebers> cpaelzer, so feel free to give a shot
[14:12] <cpaelzer> ok
[14:16] <cpaelzer> ahasenack: have you found the bug status that we can use along update-excuse tag that still makes clear that it is no bug in that package ?
[14:16] <ahasenack> cpaelzer: no, I haven't experimented with it. What I know is that "new" works. I filed a bug about it, though
[14:16] <cpaelzer> ok, keeping new then for now ...
[14:17] <cpaelzer> let me know if your bug shows any progress
[14:17] <ahasenack> ...which I'm trying to find now (the bug)
[14:19] <ahasenack> hm, lp times out when trying to list bugs I reported
[14:20] <cpaelzer> times out for my bug attachment as well
[14:21] <ahasenack> ok, found it
[14:21] <ahasenack> cpaelzer: https://bugs.launchpad.net/ubuntu-archive-scripts/+bug/1844774
[14:26] <cpaelzer> thanks
[20:29] <bdmurray> tsimonq2: Do you have any plans to fix bug 1822672?
[20:35] <bdmurray> xnox: Is the d-i task in bug 1838525 valid?
[21:18] <infinity> bdmurray: No.
[21:18] <infinity> bdmurray: grub-installer isn't in any d-i initrds.
[21:21] <bdmurray> infinity: thanks, closing