/srv/irclogs.ubuntu.com/2020/05/07/#snappy.txt

mupPR core20#53 opened: Add secureboot-db <Created by xnox> <https://github.com/snapcore/core20/pull/53>00:54
mupPR snapd#8611 opened: tests: not fail when boot dir cannot be determined <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/8611>02:04
mborzeckimorning05:20
jameshWow.  I've got a green tick on PR 582205:53
mupPR #5822: wrappers: allow user mode systemd daemons <:birthday:> <Needs Samuele review> <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/5822>05:53
mborzeckiwow, that PR is old :P06:11
jameshzyga's session-tool work has made the tests a lot more reliable06:12
mborzeckieagerly waiting for something else to break, at times it really feels like we're only maintaining the ci system06:13
mborzeckiquick errand, back in 3006:32
mupPR snapd#8610 closed: many: use /run/mnt/data over /run/mnt/ubuntu-data for uc20 (2.45) <UC20> <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8610>06:42
zygajamesh: woot06:44
zyga:-)06:45
jameshzyga: needed a minor change to session-tool to get things working on 16.0406:45
zygaGood morning everyone06:45
zygaCool, what was it?06:46
jameshzyga: "session-tool --has-session-systemd-and-dbus" returns false on 16.04, yet it has a working user instance of systemd06:46
jameshyou don't need a systemd controlled session bus to talk to systemd06:47
zygaAh, bit that is real06:47
zygaYou indeed a package installed06:47
zygaSome of our tests do that06:47
zygaDubs-user-session or something like that06:47
zygaDubs-session-bus maybe06:47
zygaAfter you install that package, session to gives you a green light06:48
jameshzyga: try running "strace --trace=connect systemctl --user status default.target" locally, and find out where it connects to the session bus :-)06:48
zygaWhere does it connect?06:48
jamesha socket at "$XDG_RUNTIME_DIR/systemd/private", which talks directly to the systemd instance06:49
zygaIirc the package ships usr lib systemd user dbus.socket06:49
jameshyes, but "systemctl --user" doesn't rely on it06:49
zygaOh. Interesting06:49
zygaBut we kind of do, you don’t get the environment variable without it06:50
jameshand it just so happens 16.04 is a system where it makes a difference06:50
zygaI worked kind of late yesterday06:51
zygaI’ll wake up and gladly look at changes06:51
jameshzyga: Here's the change I made: https://github.com/snapcore/snapd/pull/5822/commits/043ba49f8f95d5111875f99e34425e52674c88cd06:51
mupPR #5822: wrappers: allow user mode systemd daemons <:birthday:> <Needs Samuele review> <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/5822>06:51
jameshit's sitting at the tail end of my user-daemons PR at the moment06:51
jameshI can cherry pick it out into an independent PR, but my preference would be to just land user-daemons :-)06:52
zygaDoes it pass on centos-806:52
zyga706:52
jameshIt passed everywhere06:52
zygaMmmm06:52
jameshI'm doing a "systemctl --user is-enabled default.target" call first, which should only fail if we can't talk to systemd06:53
zygaThe reason I ask is that centos 7 disabled systemd —user explicitly06:53
zygaAhh06:53
zygaPerhaps that is the trick then06:53
zygaCool06:53
zygaLooking forward to having this all merged :-)06:54
jameshif there is a simpler availability check, we can use that06:54
zygaI need a coffee though06:54
zygaFew hours of sleep today06:54
zygaI’m very happy all this work is paying off06:55
mborzeckire06:58
mborzeckizyga: i'm glad it's seems to be working now, but i'm also amazed how complicated user session setup is07:03
pstolowskimorning07:03
mborzeckimakes me wonder whether it really has to be that complicated07:03
mborzeckipstolowski: hey07:03
mvogood morning pstolowski07:07
mvoand morning to mborzecki and zyga  :)07:07
zygamborzecki: I can gladly pass the baton07:11
mborzeckizyga: nah, thanks :)07:13
zygaat my desk07:14
zygagreen ticks07:14
zyganot everyone07:15
zygabut man :)07:15
zygacall me eco-friendly ;D07:15
zygamvo: I worked to like 2AM07:15
zygamvo: I kind of feel tired today07:15
zygaI will probably just attend meetings07:15
zygaand not do much meanwhile07:15
zygamaybe push some small fixes07:16
zygaand two claudio's branches are green too07:16
jameshmborzecki: just wait until we try to set up a working user session on a real Ubuntu Core system, rather than just in the test environment...07:16
zygamborzecki: rebase / merge master07:16
zyga:D07:16
zygajamesh: btw, did you notice that core 20 seems to have everything required for user services already?07:16
jameshzyga: more so than core18?07:17
zygayes07:17
zygacheck this out07:17
zygahttps://github.com/snapcore/snapd/blob/master/tests/main/session-tool-support/task.yaml07:17
zygacore 20 ships /lib/systemd/user/dbus.socket07:18
jameshzyga: ah. I agree that makes a difference for D-Bus services, yes :-)07:19
jameshuser services are working all the way back to core1607:20
zygaindeed07:20
zygajamesh: one relevant aspect that I didn't explain properly before07:20
zygabecause I was typing from a phone07:20
zygawas that dbus.socket unit injects DBUS_SESSION_BUS_ADDRESS into session environment07:21
zygaand .e.g. snap run checks for it07:21
zygaso it's plausible that other programs also check for it07:21
zygaand not fall back to other locations07:21
zygabut in general, having dbus in the session is desired07:21
jameshdefinitely07:21
jameshand maybe in a year we can pretend that it is always true07:21
jameshonce 16.04 goes EOL07:22
zygajamesh: well, that 10 year support probably means my kids can gro up to become engineers and support it07:22
mborzeckihahah07:23
zyga(for the record, my son is almost 14 now)07:23
jameshneither the desktop or snapd were included in 14.04's ESM07:24
jameshsnapd might not be so lucky for 16.04, but you might not need to care about desktop sessions there any more07:24
zygajamesh: so about that07:25
zygathere's some discussion to extend session-tool to 14.0407:25
zygaso that we have better coverage07:25
zygaI _might_ just do it07:25
jameshthere's no user instance of systemd on 14.04, so it will probably look like CentOS 707:26
zygaI was thinking about emulating all the upstart-goodies there07:26
zygaso not based on systemd07:26
zygabut stil following PAM07:26
zygaand doing "something" that is representative07:27
pedronisthe agreement on 14.04 is mostly livepatch should install and work07:29
zygammm, I see07:29
zygamaybe it's just not worth it then07:29
pedronisafaiu no07:30
mupPR snapd#8606 closed: progress: fix progress bar with multibyte duration units <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8606>07:46
mborzeckiyay07:46
zygasee you at the code review meetign!07:52
zyga*meeting07:52
pedronismvo: I did a pass on #833407:57
mupPR #8334: many: add core.resiliance.vitality-hint config setting <Needs Samuele review> <Created by mvo5> <https://github.com/snapcore/snapd/pull/8334>07:57
mvopedronis: \o/ thank you07:57
mupPR snapd#5822 closed: wrappers: allow user mode systemd daemons <:birthday:> <Needs Samuele review> <Created by jhenstridge> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5822>08:06
mupPR core20#53 closed: Add secureboot-db <Created by xnox> <Merged by mvo5> <https://github.com/snapcore/core20/pull/53>08:14
zygaI identified and fixed the tests that were breaking the pulseaudio test before08:46
zygait was the portal and xdg-open tests08:46
zygathey created ~test/.config as root08:47
zygaand that was enoguh08:47
zygaI'll send patches shortly08:47
Mirvhi I'm once again searching for bug which may or may not be a bug.. after Tumbleweed upgrade to GNOME 3.36 on two machines, the other one is missing snap in XDG_DATA_DIRS and also missing snap_bin_path and snap_xdg_path - what should be setting those? and I wonder if there's anything that could be made bullet proof regarding setting them.08:50
zygaMirv: hello08:50
MirvI can obviously workaround by setting the missing parts manually08:50
zygathose are set by IIRC the environment generator08:51
zyga(systemd env generator)08:51
zygaMirv: do you have ...08:52
zygaMirv: /usr/lib/systemd/system-environment-generators/snapd-env-generator08:53
Mirvyes I have on both machines. I'm doing random grepping but not finding differences between the machines yet09:00
zygamborzecki: ^09:03
* zyga needs to go afk for a moment09:03
mborzeckizyga: snapd-env-generator is for services iirc09:07
zygawhat? why?09:07
pedronispstolowski: is #8533 really just the test?  does it need  master merge?09:07
mupPR #8533: image, tests: core18 early config test <Created by stolowski> <https://github.com/snapcore/snapd/pull/8533>09:07
mborzeckizyga: for user sessions there's systemd-environment-d-generator09:08
mborzeckizyga: and as for why, i have no clue ;)09:08
mborzeckiMirv: does /usr/lib/environment.d/990-snapd.conf exist in your system? does `systemctl --user show-environment | grep '^XDG_DATA_DIRS='` list /var/lib/snapd/desktop ?09:09
pstolowskipedronis: ah, no, it's also actual image.go change, i will update the desc09:09
pedronispstolowski: ah, ok09:09
Mirvmborzecki: exists on both, on the affected system however /var/lib/snapd/desktop is missing while on the working system it's there09:13
Mirv(ie 990-snapd.conf exists on both)09:13
zygaMirv: any chance you are using zsh?09:13
Mirvbash on both09:13
pedronispstolowski: maybe the configcore changes should be in their own PR?09:16
mborzeckihmm looks like the issue we had on centos and rhel, where it worked in my vm, but didn't work in degville's09:16
degvillemborzecki: I think I'll try a fresh install and see what happens.09:17
pstolowskipedronis: sure, i can extract them09:18
pedronispstolowski: if it's not too annoying09:18
pstolowskipedronis: it shouldn't09:18
pedronisthank you09:18
Mirvanyway, the problem seems a bit more like systemd problem now that it is in environment.d correctly, not snap problem09:19
Mirverh... I noticed there is also 99-environment.conf symlink to /etc/environment , so out of interest I tried to copy-paste the content of 990-snapd.conf into /etc/environment and rebooted.. upon login, it seemed like I could not launch any apps, and no extensions were loaded. so I removed the lines from /etc/environment and rebooted again and... now, for some reason XDG_DATA_DIRS has the snapd dir!09:22
Mirvmaybe it's a systemd bug09:23
Mirvbefore this I had used the system with multiple reboots since last week09:23
mborzeckiperhaps some race condition09:24
mborzeckiMirv: is there a /usr/lib/systemd/user-environment-generators/30-systemd-environment-d-generator in your system?09:25
mborzeckibtw. noticed therels /usr/lib/systemd/user-environment-generators/60-flatpak that runs after, but it seems to be handling the XDG_DATA_DIRS path correctly09:28
mborzeckiMirv: if you have that 60-flatpak file ^^ can you run `XDG_DATA_DIRS=/var/lib/snapd/desktop /usr/lib/systemd/user-environment-generators/60-flatpak` and make sure that output contains /var/lib/snapd/desktop path?09:30
Mirvmborzecki: yes there is 30-systemd-environment-d-generator on both machines, and yes the output contains snapd/desktop path. but as said, after I made something error out by modifying /etc/environment and then reverting that change, now the /var/lib/snapd/desktop is correctly there also on this system that didn't have it for the past week, so I can't reproduce the problem anymore.09:35
Mirvmborzecki: .. I rebooted again, and now the problem is again there .. still the output containts the desktop path09:37
Mirvit's something causing the systemd not generate the environment correctly, quite consistently on this machine but not the other09:38
mborzeckiMirv: are you using gdm?09:39
Mirvmborzecki: yes09:39
mborzeckiMirv: ok, can you `cat /usr/share/gdm/env.d/flatpak.env`?09:40
mborzeckiif it exists09:40
Mirv-> XDG_DATA_DIRS=$HOME/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/09:42
mborzeckiMirv: heh ok, can you mv that file to say $HOME for a bit, and then reboot/relogin?09:42
mborzeckijamesh: are you familiar with gdm internals by any chance?09:44
jameshmborzecki: not deeply, but maybe I can help?09:45
mborzeckijamesh: when the user session starts up, are env files from /usr/share/gdm/env.d/ applied, and if so would that happen to run after/before systemd user env generators?09:46
mupPR snapd#8612 opened: sysconfig: use new _writable_defaults dir to create cloud config <⛔ Blocked> <Created by mvo5> <https://github.com/snapcore/snapd/pull/8612>09:46
mborzeckijamesh: from the code i see it's in the worker https://github.com/GNOME/gdm/blob/2155ffa023d94fd269cf01d69d897ebe9a63a386/daemon/gdm-session-worker.c#L1633 but does it run when user logs in or is it only for the actual gdm process?09:47
mupPR core20#54 opened: static: switch /etc/cloud from synced to persistent <Blocked> <Created by mvo5> <https://github.com/snapcore/core20/pull/54>09:47
jameshmborzecki: I'm not sure09:48
Mirvmborzecki: I've moved that away and the problem is gone for at least two subsequent boots (more than ever before).. so maybe it's a race condition09:48
Mirvanyway, I'll need to go now for a bit09:49
mborzeckijamesh: hmm the call chain goes up to do_start_session() https://github.com/GNOME/gdm/blob/2155ffa023d94fd269cf01d69d897ebe9a63a386/daemon/gdm-session-worker.c#L276409:51
zygaI found and fixed a bug affecting all portals tests09:58
zygathat should remove some more random failures09:58
zygatwo PRs to go though09:58
mborzeckiwtf is /usr/lib/systemd/user/dbus.service.d/flatpak.conf ? why are all 3 ways of injecting environment used by flatpak?10:09
zygalol10:10
zygawhat?10:10
mborzeckiat least 2 of those just override whatever is set via user env generators10:11
zygawhat's there?10:11
jameshare you sure it is only 3?10:11
mborzecki# /usr/lib/systemd/user/dbus.service.d/flatpak.conf10:11
mborzecki[Service]10:11
mborzeckiEnvironment=XDG_DATA_DIRS=%h/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/10:11
zygaheh10:11
zygaso kind10:11
mborzeckijamesh: skipped pam_env since we know it's off limits :P10:11
jameshit's not using /etc/profile.d too?10:11
zygamaybe we should file a bug?10:11
mborzeckithat file and /usr/share/gdm/env.d/flatpak.env just set XDG_DATA_DIRS10:12
jameshunilaterally overriding (rather than appending/prepending) is bad manners10:12
zygamborzecki: just ship aaa-snapd and zzz-snapd.conf10:12
zygaand set it again10:12
mborzeckialso found this comment https://bugzilla.gnome.org/show_bug.cgi?id=766176#c11 there's like 4 possible scenarios how env is injected10:13
* zyga queues for the best tech solution award ;)10:13
zygajokes aside10:13
zygait's a bug10:13
zygaand a bit eivl10:13
zyga*evil10:13
jameshwe've definitely had problems where the environment injection methods we thought we universal turn out not to be10:14
jameshthey're probably just adding new ones as they find new corner cases10:14
mborzeckiwe are seriously doomed10:15
mupPR snapd#8613 opened: o/configcore: pass extra options to FileSystemOnlyApply <Created by stolowski> <https://github.com/snapcore/snapd/pull/8613>10:16
mborzeckiwell the linux desktop is xD10:16
pedroniszyga: I did a pass on #782510:23
mupPR #7825: many: use transient scope for tracking apps and hooks <Security-High> <Created by zyga> <https://github.com/snapcore/snapd/pull/7825>10:23
zygapedronis: thank you!10:23
pedroniszyga: I should look at 8566 next, is that right?10:24
zygayes please10:24
pedronisok, lunch first10:25
zygapedronis: the main remark about the transient unit code is that test tests will be probably 500+ lines and I just didn't want to do them all here (behind a feature flag) - the main innovation is being able to do the tests in the first place (but that has since landed to master)10:27
zygapedronis: I'm happy to do the tests in the same PR if people are ok with that10:27
pedroniszyga: tbh, I think it makes more sense to split out the helper to meaningful packages and do the tests there10:28
pedronis*helpers10:28
zygapedronis: sure, just tell me where10:28
pedroniszyga: I made some suggestions in the comments10:28
zygapedronis: cmd/dbusutil? dbusutil top level... somewhere else?10:28
pedroniszyga: I think some bits belong to systemd, some bits might belong to a dbusutil package10:29
pedronisand some bits belong to sandbox/cgroup10:29
pedronisthe latter point is the more unclear10:29
pedronisI have a comment with a question about it10:29
zygaso should I split that into bits that can be discussed10:30
zygaor do you suggest to continue in the branch, just iterating on the parts there10:30
zyga(the branch has the advantage of having spread tests to check things end to end)10:31
mupPR core20#55 opened: hooks: make systemd-modules-load depend on mounts at /usr/lib/{firmware,modules} <Created by anonymouse64> <https://github.com/snapcore/core20/pull/55>10:32
zygamborzecki: https://github.com/snapcore/snapd/pull/861410:35
mupPR #8614: tests: don't create root-owned things in ~test <Test Robustness> <Created by zyga> <https://github.com/snapcore/snapd/pull/8614>10:35
mupPR snapd#8614 opened: tests: don't create root-owned things in ~test <Test Robustness> <Created by zyga> <https://github.com/snapcore/snapd/pull/8614>10:35
* zyga needs to run an errand for his parents, I will probably miss standup as we need to drive around10:35
zygathe portal tests are still not reliable, I found one more bug that is fixed locally10:36
zygabut there is more, I just cannot understand why it fails10:36
pedroniszyga: you can do the work in the branch and then split it, atm it has the problem that is both too big and not big enough (missing coverage, too much code directly in cmd_run.go)10:42
zygaOk, sounds good10:43
zygaAnd I agree10:43
pedronismborzecki: mvo: seems #8464 can be merged11:03
mupPR #8464: cmd/snap-boostrap, boot: use /run/mnt/data instead of ubuntu-data <Squash-merge> <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/8464>11:03
mvopedronis: thank you, merged11:06
mvopedronis: I updated the vitality-score PR11:06
mupPR snapd#8464 closed: cmd/snap-boostrap, boot: use /run/mnt/data instead of ubuntu-data <Squash-merge> <UC20> <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8464>11:06
mborzeckiyay11:06
ijohnsonthanks folks11:06
ijohnsonand g'morning11:06
zygaijohnson: hey :)11:07
ijohnsonhey zyga11:07
ijohnsonI had a look at your session-tool pulseaudio PR that you merged last night, it all looked good to me11:07
zygaijohnson: I fixed that bugger and found the cause for the failure11:07
ijohnsonvery nice11:07
zygahttps://github.com/snapcore/snapd/pull/861411:07
mupPR #8614: tests: don't create root-owned things in ~test <Test Robustness> <Created by zyga> <https://github.com/snapcore/snapd/pull/8614>11:08
ijohnsonzyga: nice11:10
ijohnsonit feels good to see master very green11:10
zygait is not over11:11
zygaI found two more bugs in portal tests11:11
zygafixed one11:11
zygainvestigated the other but cannot grok it yet11:11
zygarace11:11
zygabut cannot grok why11:11
zygabut little by little :11:11
zyga:)11:11
* mvo hugs zyga 11:12
mupPR snapd#8615 opened: github: register the problem matcher in a separate step to running spread <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/8615>11:12
mvothank you ijohnson and good morning as well :)11:12
ijohnsono/ mov11:13
ijohnsonah typing is hard11:13
ijohnsono/ mvo11:13
zygaoho11:13
zygakid invasion11:13
ogradont call ian a kid !11:13
zygaI have a sleeping lucy hugging me now11:13
ijohnsonhaha11:14
ijohnsonmborzecki: just noticed this unit test failure from one of my runs where I merged master: https://pastebin.ubuntu.com/p/RbzqwMKSbP/11:27
ijohnsonI'm a bit unclear what went wrong in the regex there, but it looks related to your change11:27
ijohnsonit came from https://github.com/snapcore/snapd/pull/8559/checks11:28
mupPR #8559: boot, bootloader: adjust comments, expand tests <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/8559>11:28
mborzeckiijohnson: hmm yeah, 0B/s weird11:28
mborzeckimaybe something needs tweaking11:28
zygahttps://github.com/snapcore/snapd/pull/8602 is green11:38
mupPR #8602: configcore: only reload journald if systemd is new enough <Squash-merge> <Created by stolowski> <https://github.com/snapcore/snapd/pull/8602>11:38
zygaand +311:38
zygapstolowski: ^^11:38
pstolowskigrea, and it's green finally11:39
mupPR snapd#8602 closed: configcore: only reload journald if systemd is new enough <Squash-merge> <Created by stolowski> <Merged by stolowski> <https://github.com/snapcore/snapd/pull/8602>11:41
mupPR snapd#8616 opened:  progress: tweak multibyte label unit test data  <Simple 😃> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/8616>11:42
mborzeckiijohnson: this should fix it ^^11:42
mborzecki(or at least make it more robust)11:42
pedroniscmatsuoka: hi, I wanted to review #8577 but it has conflicts atm12:10
mupPR #8577: secboot,cmd/snap-bootstrap: move initramfs-mounts tpm access to secboot <UC20> <Created by cmatsuoka> <https://github.com/snapcore/snapd/pull/8577>12:11
cmatsuokapedronis: yes, I'm fixing the conflicts but then in a test installation broke for some reason, I'm checking with ian12:11
cmatsuokapedronis: I'm retesting installation with pure master now12:12
cmatsuokapedronis: resolved12:17
pedronisthx12:17
cmatsuokapedronis: there's a handle type there I couldn't come with a good name for, suggestions welcome12:18
cachiopstolowski, hi12:40
cachiopstolowski, I see an error in preseed test https://paste.ubuntu.com/p/j5x2pHBH9m/12:40
ograhave there been any snapd changes to make anything talk to avahi via dbus recently ?12:41
cachiopstolowski, is it familiar for you?12:41
ograseems oSoMoN and I both see avahi denials for apps that did not have them before ... but funnily we see similar denials for different apps12:41
ogramsg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" interface="org.freedesktop.DBus.Peer" member="Ping" mask="send" name="org.freedesktop.Avahi" pid=431942 label="snap.chromium.chromium"12:41
ogra(i see it for chromium, olivier for libreoffice ... neither app has used avahi before)12:42
zygachrome is pinging avahi12:42
ograzyga, well ... here it is12:42
ograseems for oSoMoN libreoffice is all of a sudden pinging avahi :)12:43
ograhmm, could that be portal integration stuff?12:43
oSoMoNto be fair I don't know whether it was doing it before, I never noticed but then again I'm not watching denials all day long12:43
ograi tend to have a terminal with journalctl -f while trying our new snaps or fixing something ... i dont run my logs regulary though, but every now and then ... and i thinnk i'D have noticed Avahi denials12:44
ogras/our/out/12:45
ografor me this is definitely new ... though i have only upgraded to focal end of last week12:45
ograperhaps it is focal related12:46
zygapedronis: updated https://github.com/snapcore/snapd/pull/856612:56
mupPR #8566: cmd/cmdutil: add run inhibition operations <Created by zyga> <https://github.com/snapcore/snapd/pull/8566>12:56
* zyga -> standupo12:56
zygastandup even12:56
pstolowskicachio: looks like deb is old and doesn't ship snap-preseed binary?13:02
mupPR snapd#8615 closed: github: register the problem matcher in a separate step to running spread <Created by jhenstridge> <Closed by jhenstridge> <https://github.com/snapcore/snapd/pull/8615>13:24
mupPR snapd#8617 opened: tests: new directory used to store the cloud images on gce <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/8617>13:29
seb128bah, don't use --gdb it screws up configs/application13:32
seb128I just spent an hour figuring out my snap-store was b0rked because I tried to get a bt a few weeks ago13:32
seb128(thanks Ken for helping debugging ;-)13:32
pstolowskicachio: the preseed nested test fails because of these changes made recently to nested suite, where current snapd deb is not installed on the host. if you install it it will have snap-preseed command13:44
cachiopstolowski, ah13:44
pstolowskicachio: so solution is to install snapd.deb from /home/hopath13:45
pstolowski*gopath13:45
cachiois that part of a PR right?13:45
cachiowhich is not merged yet?13:45
pstolowskicachio: no13:45
cachioah, ok13:45
cachioin that caase I'll add that to my current pr13:46
pstolowskicachio: you probably confused it with another test that I've in a PR where I hit similiar problem13:46
cachiopstolowski, right13:46
cachioI'll fix that13:46
cachioCould you please take a look #855813:48
mupPR #8558: tests: make the nested library usable independently of spread <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/8558>13:49
cachiopstolowski, I already included that13:49
pstolowskicachio: ok13:49
cachiopstolowski, I am running tests here13:49
cachiopstolowski, I see error now https://paste.ubuntu.com/p/489MC2WnNw/14:08
cachioseccomp-compiler-version is different14:09
pstolowskicachio: yes14:11
mupPR snapd#8618 opened: gadget: fix fallback device lookup for 'mbr' type structures <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/8618>14:14
mborzeckicmatsuoka: mvo: ^^ this will fix gadget updates to rev 100 of pc gadget14:14
mvomborzecki: do we need this in snapd beta for uc20 beta?14:15
mvomborzecki: also if that is a problem, why did we not see this earlier? also thanks for the fix :)14:16
mvomborzecki: if we need it for 2.45 then let's add a tag14:16
mborzeckimvo: it'd be nice, otherwise if `update.edition:` is bumped again, the update will fail until one updates snapd first14:16
mborzeckimvo: and we did not see this earlier because pc gadget started using assets update in rev 100, the spread test we have did not update mbr because if we screed that up the spread node would be inaccessible, and there was no unit test :)14:17
mborzecki(or there was a unit test but not for this particular 'mbr' type)14:17
mvomborzecki: aha of course - that's fine then14:18
mvomborzecki: so not criticial for beta, that's good14:18
mvomborzecki: but nice to have14:18
mborzeckimvo: verified this locally in qemu updating pc gadget from 96 -> 10014:18
mborzecki(still wodnering whether updating the boostrap bit in mbr is a good idea)14:19
mborzeckiif this goes bad the chances of bricking the device is high14:20
pstolowskicachio: i need to think about this test14:20
cachiopstolowski, sure, thanks for checking it14:21
pedronisjdstrand: hi, irrespective of detailed review, I think in https://github.com/snapcore/snapd/pull/8592 a more specific interface would be better, do you have (different) input on that?14:29
mupPR #8592: Add initial support for the hardware-control interface <Created by devec0> <https://github.com/snapcore/snapd/pull/8592>14:29
mborzeckihmm session agent unit test panicked https://pipelines.actions.githubusercontent.com/xS8oSnypZkPEQZqiZgDaRp2kdvQJKbOY08TesHp7E8vn7g4hYR/_apis/pipelines/1/runs/3849/signedlogcontent/3?urlExpires=2020-05-07T14%3A34%3A52.7708746Z&urlSigningMethod=HMACV1&urlSignature=Cu8PuD6tbXaeK9XSQWsuVXqbd8jH%2B62vrOPPofc0KA0%3D14:34
mborzeckia better link https://paste.ubuntu.com/p/Cc4YQ4tCPQ/14:34
pedronismborzecki: it's actually wrappers that paniced, no?14:39
mborzeckimore like it hit a timeout and go-check aumatically panicked14:41
mborzeckibut it's weird why it'd timeout14:41
pedronissomething deadlocked14:41
pedronisor didn't Stop14:41
pedronisseems the tests are running usersession for real14:41
pedronisand stop didn't work14:41
pedronisgithub.com/snapcore/snapd/usersession/agent.(*SessionAgent).Stop(0xc4204222d0, 0x0, 0x0)14:42
pedronisis sitting there for 4 minutes14:42
pedronisthe http server bits are in Accept14:44
mborzeckimhm14:44
pedronisactualy there's a workaround added recently about this14:48
pedronisthat doesn't seem to help14:48
pedronismborzecki: what go version is that on?14:48
mborzeckipedronis: 1.914:49
* zyga is still helping his parents14:51
pedronismborzecki: this is annoying(tm)14:55
mborzeckifailed again14:56
mborzeckihttps://github.com/snapcore/snapd/runs/65330216114:56
mborzeckiat laest it's consistent14:56
mborzeckineed to run an errand with the kids, bbl14:57
pedronistrying to run it locally with 1.915:02
pedronisa bunch of times15:02
pstolowskicachio: that tests passes on master for me (but i had to add installation of the .deb on the host)15:03
cachiopstolowski, works well on 20.04?15:05
pstolowskicachio: ah, i only checked 19.10 that was failing for you. let me run on 20.0415:05
cachiopstolowski, sorry, 19.10 is working well now15:06
cachio20.04 is failing with that error15:06
pstolowskiaah15:06
ijohnsonmborzecki: mvo: can't we avoid putting that into the beta by having the gadget snap just use assumes on a new snapd version?15:18
mvoijohnson: oh, nice, yeah, that should work. I'm not sure we have assumes for pre versions yet :)15:19
ijohnsonTrue that would only work 2.45 -> 2.46 right now15:19
pedronismborzecki: it's not blocking here with 1.9.3, we are missing something15:27
mupPR snapd#8619 opened: o/devicestate,cmd/snap-bootstrap: seal to recover mode cmdline <UC20> <Created by cmatsuoka> <https://github.com/snapcore/snapd/pull/8619>15:34
cmatsuokaijohnson, mvo: a quick fix for the recover mode cmdline: https://github.com/snapcore/snapd/pull/8619/files15:35
mupPR #8619: o/devicestate,cmd/snap-bootstrap: seal to recover mode cmdline <UC20> <Created by cmatsuoka> <https://github.com/snapcore/snapd/pull/8619>15:35
ijohnsoncmatsuoka: ack looking now15:35
cmatsuokaijohnson: feel free to push any fixes, I'll be back after lunch15:35
cmatsuokaijohnson: I didn't actually test it in a real image15:40
ijohnsoncmatsuoka: I'll test it out here for ya15:40
ijohnsonhmm didn't work ootb15:59
pstolowskicachio: ok, i investigated (20.04 test fails for me too)16:01
pstolowskicachio: and i understand the issue16:01
cachiopstolowski, good, thanks for digging16:03
pstolowskicachio: is the .deb on the nested vm the official one from the distro? i assume so since it is version 2.44.3?16:04
cachioyes16:04
pstolowskiright16:05
pstolowskicachio: so the issue is: the deb in the 20.04 image has a newer version of snapd than the one that is in seeds/16:06
pstolowskicachio: snap-preseed mounts the vm image and runs snapd from seeds (the old one)16:06
cachioahhh16:06
pstolowskicachio: then the vm is started, but since snapd from deb is newer it doesn't re-exec16:07
cachiopstolowski, is it easy to fix it?16:07
pstolowskicachio: so everything runs as expected, but the test expects that the snapd from seeds was used16:07
pstolowskicachio: the fix will be in test. we should probably inject latest snapd into seeds/ of the image (which i was doing intially in these tests some time ago)16:11
cachiopstolowski, right16:11
pstolowskii wonder if this is a valid scenario that we should handle better in preseeding, need to talk to pedronis16:11
cachiopstolowski, download snapd from beta/edge and copy it right?16:12
pstolowskicachio: that could work, or repack16:13
pstolowskiyeah, edge would do16:13
cachiopstolowski, nice16:16
cachioare you testing this?16:16
cachioto see if it works?16:16
pstolowskicachio: no, not now, i can look at it tomorrow16:16
cachiopstolowski, ok, if I finish a fix I am doing I'll try to make it16:17
pstolowskicachio: it's a bit annoying as you need to mount the image, modify seed.yaml etc16:17
cachiopstolowski, ah, ok, well, in case you know the details you can do it :)16:18
pstolowskicachio: it was implemented initially in preseed.sh helpers, you can find it in git history16:18
cachiono hurry16:18
pstolowskicachio: ok, sure, i can do it16:19
cachiopstolowski, thanks16:19
pstolowskiyw16:20
* cachio lunch16:22
mupPR core20#56 opened: Revert "Add secureboot-db" <Created by xnox> <https://github.com/snapcore/core20/pull/56>16:36
mupPR core20#56 closed: Revert "Add secureboot-db" <Created by xnox> <Merged by xnox> <https://github.com/snapcore/core20/pull/56>16:39
mupPR pc-amd64-gadget#47 opened: gadget: bump edition to 2, using production signing keys for everything <Created by xnox> <https://github.com/snapcore/pc-amd64-gadget/pull/47>17:25
mupPR snapcraft#3109 opened: pcache: introduce persistent cache decorator <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/3109>17:58
cachiozyga, hey, I see this error in un18 https://paste.ubuntu.com/p/7yxW5zcspd/18:06
cachiouc1818:06
cachiozyga, is this something that you have change right? Initially the test fails like this https://paste.ubuntu.com/p/tM9HDxWsMp/18:08
mupPR snapcraft#3110 opened: repo: use persistent cache for fetching stage packages <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/3110>18:13
mupPR pc-amd64-gadget#47 closed: gadget: bump edition to 2, using production signing keys for everything <Created by xnox> <Merged by xnox> <https://github.com/snapcore/pc-amd64-gadget/pull/47>18:30
jdstrandpedronis: re 8592. yes, 'hardware-control' is way too general. also, it says it is for 'lspci -A linux-sysfs', but that command is read-only (and the r access is in hardware-observe)18:40
jdstrandpedronis: beyond the name, 'w' access over a huge swath of /sys is too general18:41
pedronisjdstrand: yes, that's what I thought as well18:41
pedronisI asked to propose something more specific to the use case, it will be also clearer what the access really is18:41
jdstrandpedronis: we have a cpu-control interface that this might fit in, or perhaps fan-control. I think we need to understand all the desired accesses. running lm-sensors to configure the host from a snap... ehh18:42
jdstrandpedronis: but we can look at it18:42
pedronisjdstrand: yes, I also mentioned that maybe there is one were it can fit already18:43
pedronis*where18:43
jdstrandtbc, we have cpu-control, fan-control would be new, but the submitter likely wants a lot of different accesses. we should look at them all specifically to decide how to organize18:44
jdstrandemitorino: fyi ^18:45
mupPR snapd#8620 opened: Adds GPL-3.0-or-later license <Created by prabhu> <https://github.com/snapcore/snapd/pull/8620>19:15
=== KindTwo is now known as KindOne
mupPR snapd#8618 closed: gadget: fix fallback device lookup for 'mbr' type structures <UC20> <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8618>19:52
mupPR snapd#8619 closed: o/devicestate,cmd/snap-bootstrap: seal to recover mode cmdline <Squash-merge> <UC20> <Created by cmatsuoka> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8619>19:53
mupPR snapd#8616 closed:  progress: tweak multibyte label unit test data  <Simple 😃> <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8616>19:55
mupPR snapd#8621 opened: o/devicestate,cmd/snap-bootstrap: seal to recover mode cmdline, unlock in recover mode initramfs <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/8621>20:00
mupPR snapd#8622 opened: cmd/snap-bootstrap/initramfs-mounts: add sudoers to dirs to copy as well <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/8622>20:32
mupPR snapd#8621 closed: o/devicestate,cmd/snap-bootstrap: seal to recover mode cmdline, unlock in recover mode initramfs <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8621>20:40
om26erHi! How does the Snap Store calculate "territory" matrix ? Is there a place where I could read about the technical information about that ? Is that anonymous ?21:22
om26erhttps://snapcraft.io/docs/snap-store-metrics -- The page I found, does not answer my question21:23

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