/srv/irclogs.ubuntu.com/2021/04/06/#snappy.txt

mupBug #1909412 changed: LazyUnmount in .mount units prevents root fs to umount cleanly <Snappy:Expired> <https://launchpad.net/bugs/1909412>04:20
mupBug #1909412 opened: LazyUnmount in .mount units prevents root fs to umount cleanly <Snappy:Expired> <https://launchpad.net/bugs/1909412>04:29
mupBug #1909412 changed: LazyUnmount in .mount units prevents root fs to umount cleanly <Snappy:Expired> <https://launchpad.net/bugs/1909412>04:32
mupBug #1909412 opened: LazyUnmount in .mount units prevents root fs to umount cleanly <Snappy:Expired> <https://launchpad.net/bugs/1909412>04:35
mupBug #1909412 changed: LazyUnmount in .mount units prevents root fs to umount cleanly <Snappy:Expired> <https://launchpad.net/bugs/1909412>04:38
mborzeckimorning06:09
zygamvo good morning :)06:43
mvogood morning zyga ! did you had a nice easter weekend too?06:43
zygamvo yes, very relaxing06:43
zygathe weather was not much fun so we stayed mostly indoors06:44
zygaspring gardening has started though06:44
zygaI've planted some seeds and I have first sprouts growing06:44
zygahow was yours?06:44
mborzeckimvo: zyga: hey06:45
zygao/06:45
zygaI need to tidy my desk, bbl06:46
mvozyga: very nice, we had a bit of good weather so I spend time in the sun. but then the weather changed and it got very cold, we even have a bit of snow this morning :)06:53
mvomborzecki: hey! how are you?06:53
mborzeckimvo: hey, still a bit sleepy 😉 time to get some coffee06:54
mborzeckimvo: i've pinged you in a couple of PRs that can land but are blocked on failing, though unrelated, spread tests06:54
mvomborzecki: sure, I'm going over my mail right now but feel free to ping me out-of-band for force-merges07:07
pstolowskimorning07:14
mborzeckipstolowski: hey07:26
pstolowskimborzecki: hey!07:27
mupPR snapd#10109 closed: interfaces/builtin/gpio_test.go: actually test the generated gpio apparmor <Simple 😃> <Skip spread> <Test Robustness> <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10109>07:59
jameshmvo: I haven't had any luck getting enough green CI check marks to allow https://github.com/snapcore/snapd/pull/9963 to merge.  I don't believe any of the problems are related to the branch contents, so could you hit the merge button?08:03
mupPR #9963: wrappers: install D-Bus service activation files for snapd session tools on core <Needs Samuele review> <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/9963>08:03
mvojamesh: sure08:03
mupPR snapd#10104 closed: many: add x-gvfs-hide option to mount units <Created by lhotari> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10104>08:04
mvomborzecki: arch looks unhappy in https://github.com/snapcore/snapd/pull/9963/checks?check_run_id=2257669181 - is that a known issue?08:04
mupPR #9963: wrappers: install D-Bus service activation files for snapd session tools on core <Needs Samuele review> <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/9963>08:04
mvomborzecki: "curl: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by curl)"08:04
mborzeckimvo: pstolowski fixed that on friday i think08:05
pstolowskimvo: yes08:05
mvocool, thanks pstolowski and mborzecki08:05
mvopstolowski: and good morning :)08:05
pstolowskii'm going to push a trivial followup with --ignore08:05
mborzeckipstolowski: btw. cgroupv2 change was introduced by systemd 24808:05
pstolowskihey :)08:05
jameshmvo: thanks08:07
mupPR snapd#9963 closed: wrappers: install D-Bus service activation files for snapd session tools on core <Needs Samuele review> <Created by jhenstridge> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9963>08:09
pstolowskimborzecki: https://github.com/snapcore/snapd/pull/1011208:15
mupPR #10112: spread: ignore linux kernel upgrade in early stages for arch preparation <Simple 😃> <Created by stolowski> <https://github.com/snapcore/snapd/pull/10112>08:15
mupPR snapd#10112 opened: spread: ignore linux kernel upgrade in early stages for arch preparation <Simple 😃> <Created by stolowski> <https://github.com/snapcore/snapd/pull/10112>08:19
mupPR # closed: snapd#10077, snapd#10079, snapd#10080, snapd#10095, snapd#1009708:39
mupPR snapd#8883 closed: packaging: stop snapd early on purge <Test Robustness> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/8883>08:44
mupPR snapd#10050 closed: tests: use snaps-state commands and remove them from the snaps helper <Created by sergiocazzolato> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10050>08:44
mborzeckipedronis is off today, isn't he?10:07
mvomborzecki: correct10:08
mborzeckithat's ok, i'm wondering a bit about extending modeenv to track 'current' gadgets10:08
mborzeckiotherwise it'd be a pain to find out the gadget snap ourselves when we mark the boot as successful10:09
pstolowskixnox: hi, maybe you would know if what i suggested in https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293 wrt waiting of zfs makes sense?11:05
mupBug #1922293: Snaps appear broken on 21.04 Beta with ZFS <hirsute> <iso-testing> <snapd (Ubuntu):Confirmed> <https://launchpad.net/bugs/1922293>11:05
jameshsnap downloads seem particularly slow today11:21
xnoxpstolowski:  yeah, we can also have zfs-mount.service have Before=snapd.service if you want it that way? or is that of no help, cause we start individual snaps .mount units without snapd.service on subsequent boots?11:22
pstolowskixnox: i'm afraid we need it on each individual mount unit11:23
ogradoes Before= even work if i uninstall snapd ?11:23
xnoxpstolowski:  i wonder if var.mount After=zfs-mount.service will suffice?11:23
ogra(which i suppose still many people do)11:24
pstolowskixnox: i guess the question is also if zfs-mount.service is the *right* one to wait for, i tried other zfs-related units (such as volumes-ready) but fwtw only this one seemed to work11:24
xnoxpstolowski:  mount units should allow ordering like that. as in before mount of /var/lib/any/parts/of/path are executed, the ordering of things of all the parent components should be good.11:24
pstolowskixnox: ah i didn't know we have var.mount, let me try that11:25
xnoxogra:  before/after are pure ordering-only hints. which can be ignored to break deadlocks. and have no affect on adding/removing dependencies and don't care if things are present or not.11:25
pstolowskiyep exactly11:26
xnoxwants/wantedby/conflicts/requires => are actuall dependencies, which can be soft or hard.11:26
ograah, good then (i sismply didnt know, thanks for educating me 🙂 )11:26
xnoxi.e wants/wantedby are optional, whereas conflicts/requires will break things =)11:26
ogragood to know !11:27
xnoxpstolowski:  there is zfs.target too.... and well zfs-mount tries to run as early as possible beofre local-fs.target....11:28
xnoxpstolowski:  i wonder if snap*.mount units should have After=local-fs.target11:28
xnoxsuch that all the things from /etc/fstab (and zfs things) are all mounted, then we go and try to mount snaps.11:29
xnoxpstolowski:  cause you do want /var & /home and so on to all be mounted before you attempt mounting snaps right?11:29
pstolowskixnox: this sounds reasonable too; nb i fail to see var.mount, where is it?11:29
xnoxpstolowski:  create it =)11:29
pstolowskiah ok :)11:29
xnoxpstolowski: when ever there is What=/path/to/anything/blah.snap => it will try to ensure that11:30
pstolowskigot it11:30
xnox/ is satisfied, and /path, and /path/to, and /path/to/anything....11:30
xnoxhopefully =011:30
xnoxor things are broken =)11:30
pstolowskixnox: var.mount with After=... broke it :/11:34
pstolowskixnox: "!!! Failed to isolate default target" and stuck11:34
xnoxpstolowski:  yes11:34
xnoxbecause there is /var in /etc/fstab11:34
xnoxpstolowski:  and it gets generated into .mount unit in /run/11:34
pstolowskiah11:35
xnoxpstolowski:  you can do drop-in i.e. /etc/systemd/system/var.mount.d/foo.conf [Service]After=11:35
xnoxpstolowski:  or i think you can edit fstab too11:35
xnoxpstolowski:  in fstab, where you have /var specify after zfs-mount.service11:36
xnoxsorry11:36
xnoxx-systemd.after=zfs-mount.service i think11:36
xnoxyeap, as an option.11:36
xnoxas per $ man systemd.mount11:36
xnoxpstolowski:  sorry that i misled you11:37
pstolowskixnox: no worries, trying11:40
pstolowskixnox: so, /etc/systemd/system/var.mount.d/foo.conf didn't help; After=local-fs.target didn't work either; only After=zfs-mount.service works11:54
pstolowskixnox: something in a single central place would be ideal obviously if we can figure it out, rather than patching all snapd units11:55
pstolowskibut maybe it's more subtle11:55
xnoxpstolowski:  after=local-fs.target on the snap units? and after=zfs-mount.service on the snap*.mount units?11:55
xnoxalso kind of odd that snap*.mounts units already don't have implicit after local-fs.target to be fair =/11:56
pstolowskixnox: yes, both tried on snap.*mount units11:56
pstolowskixnox: mhm, it's shocking we got away with it for so many years ;)11:59
mvoI think we debugged this at some point and there should be implicit rules for after=local-fs.target already, I can try t ofind the PR were we looked into this12:02
pstolowskithen maybe it's not enough for zfs12:06
mvoyeah, not against fixing it, just saying there might be more to it and it may well break more people12:07
pstolowskiyep, absolutely12:12
pstolowskilunch, bbl12:12
* pstolowski lunch12:12
mupPR snapd#10112 closed: spread: ignore linux kernel upgrade in early stages for arch preparation <Simple 😃> <Created by stolowski> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10112>12:20
pstolowskimvo: this could land https://github.com/snapcore/snapd/pull/1005213:28
mupPR #10052: features: add gate-auto-refresh-hook feature flag <Refresh control> <Simple 😃> <Created by stolowski> <https://github.com/snapcore/snapd/pull/10052>13:28
mvopstolowski: sure13:29
pstolowskithanks13:29
mupPR snapd#10052 closed: features: add gate-auto-refresh-hook feature flag <Refresh control> <Simple 😃> <Created by stolowski> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10052>13:30
xnoxmvo:  pstolowski: i would err on the side of zfs*.service units not doing something right.13:42
xnoxrather than snapd*.mount units being incomplete. We must have a tonne of people who have /var on ext4 xfs etc. and it all works for them.13:42
pstolowskixnox: do you know who is maintaining this in ubuntu?13:43
mvopstolowski: dpkg -S /lib/systemd/system/zfs-mount.service should give you the package and apt chagnelog <pkgname> the last uploader, what do you get there?13:44
pstolowskiin any case i agree it should probably be fixed elsewhere (and not by snapd)13:44
pstolowskimvo: it's Colin Ian King13:47
mvopstolowski: thanks, I have the changelog now too, let me poke a bit13:47
pstolowskimvo: sure, thanks14:00
ijohnsonmvo: do you want me to force push the final solution I ended up at to #10107 ? I think adding that kind of code to the the debian maintainer scripts should probably be for another PR14:06
mupBug #10107: pppoeconf: new changes from Debian require merging <pppoeconf (Ubuntu):Fix Released by doko> <https://launchpad.net/bugs/10107>14:06
mupPR #10107: packaging: stop snapd.{socket,service} before purging data <Precious Logs> <Test Robustness> <Created by mvo5> <https://github.com/snapcore/snapd/pull/10107>14:06
mvopstolowski: do you have that system with zfs still around? do you have sometihng when you run "find /run/systemd -name "var*.mount" ?14:25
zygamvo I have a system with zfs but not on rootfs14:32
pstolowskimvo: yes i've ,let me check14:37
pstolowskimvo: nothing14:40
mvopstolowski: hm, and "mount" will show you that there is a mount for /var ?14:42
mvopstolowski: there is a generator that should create a var.mount file it seems, no wonder if systemd is confused if non of those are generated :)14:42
pstolowskimvo: nope.. https://pastebin.ubuntu.com/p/QTfknGYY3r/14:44
pstolowskimvo: (note snaps are only mounted because of my workaround)14:45
mvopstolowski: can you pastebin "ls /run/systemd/generator" as well please14:47
pstolowskimvo: https://pastebin.ubuntu.com/p/tXxcyNhzz2/14:48
zygamvo maybe just look at all the mount units14:56
zygaat runtime14:56
mvozyga, pstolowski good idea. what does "sudo systemctl status var-lib.mount14:58
mvo" print?14:58
* zyga goes to boot up his zfs box14:58
pstolowskimvo: it's active, mounted14:59
mvopstolowski: where does it come from? there should be a line that says from where it is15:02
pstolowskimvo: https://pastebin.ubuntu.com/p/pd8N9Qg7F8/15:02
mvopstolowski: that is interessting15:05
* cachio lunch15:09
zygamvo so perhaps I can explain15:14
zygamvo zfs pool has some configured volumes15:14
zygamvo they just get mounted by the kerenl15:14
zyga*kernel15:14
zygamvo system noticed and creates the (virtual) mount unit15:15
zygaso they don't have to be spelled out in any place other than zfs pool configuration15:15
zygamvo similarly to how you can mount a thing from command line, by hand15:15
zygaand immediately ask systemd about the .mount unit it corresponds to15:15
mvozyga: right, I summarized this in https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293/comments/14 I hope, I wonder what the right fix is - probably a geneator?15:17
mupBug #1922293: Snaps appear broken on 21.04 Beta with ZFS <hirsute> <iso-testing> <snapd (Ubuntu):Confirmed> <zfs-linux (Ubuntu):Confirmed> <https://launchpad.net/bugs/1922293>15:17
zygamvo I think this is a good explanation15:19
zygawhat I wonder if the systemd special automatic dependency is working or not15:19
zygathose described by systemd.mount(5) "AUTOMATIC DEPENDENCIES"15:20
zygato quote:15:20
zyga       •   If a mount unit is beneath another mount unit in the file system15:20
zyga           hierarchy, both a requirement dependency and an ordering dependency15:20
zyga           between both units are created automatically.15:20
mvozyga: yeah, was wondering the same if this is a systemd bug maybe15:28
zygamvo I doubt that but let's see15:29
pstolowskimvo: thanks for this!15:33
mvopstolowski: no worries, thank *you* for all the hard work finding the details16:05
pstolowskimvo: i saw the comment from didrocks; opened https://github.com/snapcore/snapd/pull/1011316:26
mupPR #10113: systemd: wait for zfs mounts <Bug> <Created by stolowski> <https://github.com/snapcore/snapd/pull/10113>16:26
pstolowskieod16:28
mupPR snapd#10113 opened: systemd: wait for zfs mounts <Bug> <Created by stolowski> <https://github.com/snapcore/snapd/pull/10113>16:30
zygamvo uh, changing all the mount units will be painful16:31
zygacan a generator drop an override to all the snapd mount units that injects the new dependency?16:32
ijohnsonI think generators can do that16:32
ijohnsonI think we do that for lxd containers to fix some bug recently16:32
ijohnsonmaybe that was slightly different though16:33
ijohnsonbut also we will need to rewrite service units *soon* anyways for other features so probably not a big deal if we need to implement that feature too16:33
zygaI think so as well, but I don't recall details16:34
mvozyga, ijohnson yeah, I think it's okay if this is not perfect, this is new installs anyway16:47
ijohnsonthat's fair16:47
=== ijohnson is now known as ijohnson|lunch
mupPR snapd#10111 closed: tests: update "spread: disable Go modules support in environment" <Squash-merge> <Created by sergiocazzolato> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10111>17:35
* cachio afk19:07
=== ijohnson|lunch is now known as ijohnson
mupPR snapd#10114 opened: tests/lib/prepare-restore.sh: clean out snapd changes and snaps before purging <Test Robustness> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/10114>19:56
mupPR snapd#10115 opened: tests: force a proxy to use cache action <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/10115>22:26

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