[00:00] <pinusc> Is there an easy way to nuke all my lxd configuration and just start from scratch?
[00:00] <pinusc> Now lxc delete is giving me errors
[00:00] <stgraber> a btrfs subvolume is the other option, if you have a large disk (like your /data) already mounted, LXD can also use an empty directory from that as its source
[00:00] <stgraber> rm -rf /var/snap/lxd/common/lxd followed by a reboot would be quite efficient at resetting everything
[00:01] <stgraber> should get you to the same state as just having installed LXD for the first time
[00:01] <pinusc> Okay, great
[00:02] <pinusc> Well, that's all I need
[00:03] <pinusc> Thank you so much, you've been so helpful! Can't believe that the lxd project lead had time to help me sort through my fuck-up.
[00:06] <stgraber> sorry about your containers, hopefully your next setup will be more solid :)
[04:28] <mup> PR snapd#9779 opened: testutil: make DBusTest use a custom bus configuration file <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/9779>
[06:45] <mborzecki> morning
[07:00] <jamesh> hi mborzecki
[07:00] <mborzecki> jamesh: hey
[07:18] <jamesh> mborzecki: could you have a look at https://github.com/snapcore/snapd/pull/9779 ? -- it's short and should make the dbus unit tests a little more robust
[07:18] <mup> PR #9779: testutil: make DBusTest use a custom bus configuration file <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/9779>
[07:18] <mborzecki> jamesh: sure, will do
[07:19] <jamesh> mborzecki: it basically just disables service activation for the DBusTest private session bus
[07:20] <mvo> hey mborzecki and jamesh
[07:20] <jamesh> hi mvo
[07:23] <mborzecki> jamesh: yeah, that sounds like a good idea, it'd be a bummer if some known service got activated on a test bus
[07:24] <mborzecki> mvo: sorry for confusing comments in #9776, i clearly shouldn't be doing reviews that late ;)
[07:24] <mup> PR #9776: gadget: add validation for "$kernel:ref" style content <Skip spread> <UC20> <Created by mvo5> <https://github.com/snapcore/snapd/pull/9776>
[07:39] <mborzecki> jamesh: +1
[07:52] <jamesh> mborzecki: thanks
[08:00] <pstolowski> morning
[08:42] <mborzecki> mvo: https://github.com/snapcore/snapd/pull/9776#discussion_r539976882 i'll play with it locally to see if i can propose a diff that would not use the regex
[08:42] <mup> PR #9776: gadget: add validation for "$kernel:ref" style content <Skip spread> <UC20> <Created by mvo5> <https://github.com/snapcore/snapd/pull/9776>
[08:48] <mvo> mborzecki: thanks, looks like it needs to be stricter. feel free to push something else, if so please make it a helper because the regexp is used in the followup
[08:48] <mvo> mborzecki: something like parserKernelRef(ref) (tag, path, error) or something
[08:50] <pedronis> I'm very confused by https://github.com/snapcore/snapd/pull/9775 it has unit tests failures that don't make sense to me
[08:50] <mup> PR #9775: gadget,o/devicestate,tests: drop EffectiveFilesystemLabel and instead set the implicit labels when loading the yaml <Cleanup :broom:> <Run nested> <UC20> <Created by pedronis> <https://github.com/snapcore/snapd/pull/9775>
[08:51] <pedronis> anyway I need to push to it again
[09:14] <mup> Bug #1906621 changed: System doesn't do FDE when installing with secure boot enabled <uc20> <Snappy:Invalid> <https://launchpad.net/bugs/1906621>
[09:23] <mborzecki> mvo: there's a mismatch between what kernel/kernel.go treats as valid asset name and #9776, i'll tweak it to allow [a-zA-Z0-9][a-zA-Z0-9-]* like your PR does
[09:23] <mup> PR #9776: gadget: add validation for "$kernel:ref" style content <Skip spread> <UC20> <Created by mvo5> <https://github.com/snapcore/snapd/pull/9776>
[09:24] <mvo> mborzecki: \o/ thank you
[09:49] <mborzecki> mvo: pushed a couple of patches to 9776, please take a look, if the asset name validation is too lax we can revert the relevant patch
[09:52] <mvo> ta, in a meeting I have a look in a wee bit
[10:17] <cachio> pstolowski, mborzecki hi, could you take a look to #9737 please
[10:17] <mup> PR #9737: tests: use os.query tool instead of comparing the system var <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9737>
[10:17] <pstolowski> cachio: hey, will do
[10:17] <cachio> thanks
[10:18] <mborzecki> pedronis: sure
[10:19] <cachio> mvo, hey, still this test failing for sbuild test on debian https://paste.ubuntu.com/p/76pSQXqS52/
[10:19] <cachio> mvo, the only one
[10:22] <pedronis> mborzecki: ?
[10:22] <mborzecki> pedronis: uhh, sorry
[10:22] <mborzecki> cachio: sure :)
[10:23] <cachio> mborzecki, tx
[10:24] <pedronis> ah, I was confused because the obvious other p* recipient would have been Pawel
[10:29] <mvo> cachio: uh, right. thanks for the reminder
[10:29] <cachio> mvo, yaw
[10:34] <cachio> pstolowski, hey, I see the hotplug test failing for 20.04 and 2.10 https://travis-ci.org/github/snapcore/spread-cron/builds/748673129#L5564
[10:35] <cachio> pstolowski, I'll try to reproduce it
[10:41] <pstolowski> cachio: ok
[10:43] <pstolowski> cachio: did start failing today?
[10:44] <cachio> not sure, because previous days it was failing because a problem with travis
[10:44] <cachio> the dependencies problem started during the weeken on travis
[10:44] <cachio> and then I fixed that yesterday and next run I see this error on hotplug
[10:45] <pstolowski> cachio: ok. but before that it was passing right?
[10:45] <cachio> yes
[10:45] <pstolowski> or we didn't notice?
[10:45] <pstolowski> ok
[10:46] <cachio> https://travis-ci.org/github/snapcore/spread-cron/builds/748546888
[10:46] <cachio> yesterday after the fix it passed
[10:58] <pedronis> cachio: I'm getting this:  2020-12-10 10:30:03 Cannot allocate google-nested:ubuntu-18.04-64: cannot find any Google image matching "ubuntu-1804-64-virt-enabled" on project "computeengine" or "ubuntu-os-cloud"
[10:59] <pedronis> do we need to clean the image list?
[10:59] <cachio> pedronis, I just did it 20 minutes ago
[10:59] <cachio> pedronis, is it still happening?
[10:59] <pedronis> maybe I started just before
[10:59] <pedronis> I'll wait a bit and re-run
[11:00] <cachio> pedronis, nice, thanks
[11:00] <pstolowski> cachio: i don't see classic/hotplug in yesterday's log
[11:00] <pstolowski> only core/hotplug
[11:01] <cachio> pstolowski, right
[11:01] <cachio> it is a different run
[11:02] <cachio> pstolowski, I don't have previous runs
[11:03] <cachio> all of them have failed with the dependencies error
[11:03] <pstolowski> cachio: ok
[11:10] <mup> PR snapd#9780 opened: many: use ResolvedSource() from gadget content when writing boot assets <UC20> <Created by mvo5> <https://github.com/snapcore/snapd/pull/9780>
[11:11] <pedronis> mvo: I reviewed #9758
[11:11] <mup> PR #9758: secboot: add new LockSealedKeys() that uses either TPM/fde-reveal-key <Squash-merge> <UC20> <Created by mvo5> <https://github.com/snapcore/snapd/pull/9758>
[11:11] <mvo> pedronis: \o/ thank you
[11:12] <cachio> mvo, I see this on uc20 nested tests https://paste.ubuntu.com/p/vTqb9dTZfS/
[11:12] <cachio> on uc20
[11:12] <cachio> it is trying to find core snap
[11:20] <pstolowski> cachio: reviewed
[11:21] <cachio> pstolowski, thanks
[11:28] <mvo> cachio: oh, this is strange indeed, why is it trying to start snapd from core on a uc20 system :/ what is the full log?
[11:29] <cachio> mvo, https://paste.ubuntu.com/p/WngswJTXFs/
[11:29] <cachio> I am researching why some tests are failing on uc20
[11:29] <cachio> I saw that
[11:29] <cachio> I ran from my machine
[11:30] <cachio> this test google-nested:ubuntu-20.04-64:tests/nested/core20/gadget-reseal
[11:30] <mvo> cachio: thank you!
[11:46] <mvo> hm, I see a tests/core/netplan test failure with undefined symbol netplan_parse_yaml() - is this a fluke or did others see this too?
[11:49] <cachio> mvo, I saw many tests fail with similar errors
[11:49] <cachio> all of them on uc20 test suite
[11:50] <mborzecki> mvo: i think we can land https://github.com/snapcore/snapd/pull/9779 failures are unrelated
[11:50] <mup> PR #9779: testutil: make DBusTest use a custom bus configuration file <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/9779>
[11:52] <mvo> mborzecki: yes
[11:52] <mvo> cachio: thanks
[11:53] <mvo> ijohnson: looks like test-snapd-netplan-apply is auto-uploaded by you currently, what recipe is providing this currently?
[11:55] <mup> PR snapd#9779 closed: testutil: make DBusTest use a custom bus configuration file <Created by jhenstridge> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9779>
[11:56] <pstolowski> stgraber: hey, quick question, would it be possible for lxd snap to drop install hook completely and move it's logic (which is just mkdir/chmod) to daemon.activate script?
[12:00] <mvo> ijohnson: nevermind, found it
[12:05] <mup> PR snapd#9781 opened: gadget/quantity: introduce Offset, start using it for offset related fields in the gadget <Simple 😃> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9781>
[12:18] <cachio> pstolowski, hey, I don't get this comment https://github.com/snapcore/snapd/pull/9737#discussion_r540083054
[12:18] <mup> PR #9737: tests: use os.query tool instead of comparing the system var <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9737>
[12:20] <pstolowski> cachio: yeah sorry, i think i was confused
[12:20] <cachio> pstolowski, nice,
[12:20] <cachio> np
[12:22] <pstolowski> +1
[12:25] <mborzecki> interesting failure in unit tests https://paste.ubuntu.com/p/9MBwSdktSv/
[12:27] <pedronis> so my gadget changes might be breaking something for real, many core20 nested tests failed to prepare
[12:27] <mvo> fwiw, I filed https://github.com/anonymouse64/test-snapd-netplan-apply/issues/1 for the netplan test fialures
[12:27] <pedronis> though the error is not obvious
[12:45] <mup> PR snapd#9768 closed: daemon: start splitting snaps op tests out of api_test.go <Cleanup :broom:> <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/9768>
[12:46] <pstolowski> i need 2nd reviews for #9732 and #9429 (order doesn't matter, they are independent)
[12:46] <mup> PR #9732: asserts: snapasserts method to validate installed snaps against validation sets <validation-sets :white_check_mark:> <Created by stolowski> <https://github.com/snapcore/snapd/pull/9732>
[12:46] <mup> PR #9429: o/daemon: validation sets api and basic spread test <Needs Samuele review> <validation-sets :white_check_mark:> <Created by stolowski> <https://github.com/snapcore/snapd/pull/9429>
[12:51] <pedronis> pstolowski: related, I forgot that my change going forward has now landed: https://github.com/snapcore/snapd/pull/9429/files#r540141892
[12:51] <mup> PR #9429: o/daemon: validation sets api and basic spread test <Needs Samuele review> <validation-sets :white_check_mark:> <Created by stolowski> <https://github.com/snapcore/snapd/pull/9429>
[12:51] <pstolowski> pedronis: ah right, that crossed my mind yesterday, will update
[14:33] <mborzecki> do we still need /usr/lib/snapd/system-shutdown helper?
[14:36] <pedronis> mvo: we should probably talk anyway about the reseal issue, I have some ideas
[14:42] <mvo> pedronis: sounds good, please give me 2min
[14:42] <mvo> pedronis: I pushed something trivial as a starting point, I can be in the HO in 2min
[14:44] <pedronis> I'm in the standup
[14:45] <mup> PR snapd#9782 opened: devicestate: make DeviceManager.hasFDESetupHook() more robust <Run nested> <Squash-merge> <UC20> <Created by mvo5> <https://github.com/snapcore/snapd/pull/9782>
[15:00] <mvo> pedronis: sorry! I have 30min more, meeting either got moved or I misremembred the time. but we were done, right?
[15:02] <pedronis> mvo: we are done
[15:02] <pedronis> I'm taking a break
[15:02] <mvo> pedronis: I work on the discussed fix now, enjoy your break
[15:25] <mup> PR snapd#9782 closed: devicestate: make DeviceManager.hasFDESetupHook() more robust <Run nested> <Squash-merge> <UC20> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/9782>
[15:25] <ijohnson> pedronis: addressed your feedback on #9778
[15:25] <mup> PR #9778: asserts/repair.go: add "bases" and "modes" support to the repair assertion <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9778>
[15:25]  * ijohnson goes to work on netplan now
[15:30] <mvo> pedronis: pushed the first bit of what we discussed and should unbreak master but need to run for meeting now :(
[15:30] <mup> PR snapd#9783 opened: gadget: use "sealed-keys" to determine what method to use for reseal <Run nested> <Squash-merge> <UC20> <Created by mvo5> <https://github.com/snapcore/snapd/pull/9783>
[15:32] <ijohnson> hey mvo do you have logs from the netplan failure, I can't reproduce it
[15:32] <ijohnson> I tried on a uc20 system, perhaps I should try on uc18 ?
[15:34] <mvo> ijohnson: I think it's only python3.5
[15:34] <ijohnson> mvo: so where did you see it fail?
[15:35] <mvo> ijohnson: I did see it on 16.04
[15:35] <ijohnson> so ubuntu core 16 or ubuntu 16.04 ?
[15:35] <mvo> ijohnson: ubuntu 16.04
[15:35] <ijohnson> afaik that snap should only be used on core systems, not classic
[15:35] <ijohnson> hmm
[15:36] <ijohnson> ah I see it is used on classic with the fake netplan service we run in tests/main/fake-netplan-apply
[16:19] <ijohnson> hmm I don't think that layout is enough, it still complains about not being able to load the fil
[16:20] <ijohnson> *not being able to load/find that symbol from the file
[16:25] <mup> PR snapd#9784 opened: interfaces/builtin/network-setup-control: allow using netplan apply directly <Needs security review> <Simple 😃> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9784>
[16:43] <stgraber> pstolowski: hmm, if you look at the comment in the install hook, it states that it creates the path needed by the unit, so the snap.lxd.daemon.unix.socket unit would fail to initialize if that wasn't present.
[16:43] <stgraber> pstolowski: (or would initialize and allow everyone to list the path content which may arguably be worse)
[16:45] <mvo> can someone please do a second review for #9758 ?
[16:45] <mup> PR #9758: secboot: add new LockSealedKeys() that uses either TPM/fde-reveal-key <Squash-merge> <UC20> <Created by mvo5> <https://github.com/snapcore/snapd/pull/9758>
[16:49] <pstolowski> stgraber: ah of course, i see it now, thanks
[16:49] <ijohnson> mvo I will review it today, I started yesterday
[16:49] <mvo> ijohnson: \o/
[16:49] <mvo> ijohnson: thank you!
[16:49] <ijohnson> pedronis: I responded to a suggestion in #9784, thoughts ?
[16:50] <mup> PR #9784: interfaces/builtin/network-setup-control: allow using netplan apply directly <Needs security review> <Simple 😃> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9784>
[16:51] <pedronis> ijohnson: sorry, I meant not to include err
[16:51] <ijohnson> pedronis: ah ok
[16:51] <ijohnson> sure that's fine
[16:52] <pedronis> ijohnson: there's code like that also in model.go
[16:52] <ijohnson> got it, makes sense
[16:53] <ijohnson> pedronis: pr is updated
[16:56] <pedronis> ijohnson: thx
[19:09]  * cachio afk
[22:47] <mup> PR snapd#9785 opened: tests/main/fake-netplan-apply: disable test on xenial for now <Simple 😃> <⚠ Critical> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9785>