[Bug 1976281] Re: snapd autopkgtest tests impossible combination of things
I uploaded snapd 2.55.5 as a SRU to all the relevant releases. They are in the "unapproved" queue right now, see e.g. https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=snapd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976281 Title: snapd autopkgtest tests impossible combination of things To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1976281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974147] Re: [SRU] 2.56
** Description changed: - placeholder + This is a new version of snapd. + + The changelog is available here + https://github.com/snapcore/snapd/blob/2.56/packaging/ubuntu-16.04/changelog, + the raw git changelog is available here: + https://github.com/snapcore/snapd/commits/2.56 (note that the debian + changelog is auto-generated from the merges of the git commits so there + is usually no need to look at the raw git commits). + + The snappy team released a new release that we want SRU into bionc+. The + new process described in https://wiki.ubuntu.com/SnapdUpdates was used + and we have done integration-tests on the snappy images, autopkgtests on + classic and unit tests. + + GitHub Actions test runs can be found at + https://github.com/snapcore/snapd/actions?query=branch%3Arelease%2F2.56 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974147 Title: [SRU] 2.56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1974147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set with networkd
The snapd test change is up in https://github.com/snapcore/snapd/pull/11810 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set with networkd To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974147] [NEW] [SRU] 2.56
Public bug reported: placeholder ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [SRU] 2.55 + [SRU] 2.56 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974147 Title: [SRU] 2.56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1974147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded
Fwiw, I tested this also for focal->jammy on my laptop (real machien) and it worked fine there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969162 Title: bad interaction between snapd and update-notifier when snapd package is being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded
I ran the spread test in the snapd PR https://github.com/snapcore/snapd/pull/11702 against this change in 21.10 and 22.04 and the restart behavior is correct: if snapd is upgraded from a version that does not yet use "dh_systemd --restart- after-upgrade" still keep running. ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969162 Title: bad interaction between snapd and update-notifier when snapd package is being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded
It seems the above is not an issue on 21.10 at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969162 Title: bad interaction between snapd and update-notifier when snapd package is being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded
There is one thing I noticed - when transitioning from "dh_systemd_start" to "dh_systemd_start --restart-after-upgrade" at least on 16.04 snapd.service is stopped in the old prerm but when the new postinst runs it calls "systemctl restart snapd" but that only restarts a service if it was not stopped before by systemctl so one ends up without a running snapd. I need to check if that is just 16.04 (it was a failure in our CI) or if it also affects 21.10 and later (hope this makes sense) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969162 Title: bad interaction between snapd and update-notifier when snapd package is being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded
I uploaded a version of snapd with the changes from https://github.com/snapcore/snapd/pull/11680 and https://github.com/snapcore/snapd/pull/11287 to the my ppa:mvo/tmp for impish too. On a minimal impish system (created with autopkgtest-buildvm) I ran: $ sudo apt-add-repository ppa:mvo/tmp $ sudo apt install --no-install--recommends snapd update-notifier $ sudo snap install canonical-livepatch $ apt list -a snapd [shows the impish PPA version is used] $ sudo sed -i 's/impish/jammy/' /etc/apt/sources.list $ sudo sed -i 's/impish/jammy/' /etc/apt/sources.list.d/mvo-ubuntu-tmp-impish.list $ sudo apt update $ apt list -a snapd [shows the PPA version as the one that will be upgraded to] $ sudo apt full-upgrade -y with that the upgrade does not hang anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969162 Title: bad interaction between snapd and update-notifier when snapd package is being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded
On a minimal impish system (created with autopkgtest-buildvm) I ran: $ sudo apt install --no-install--recommends snapd update-notifier $ sudo snap install canonical-livepatch $ sudo apt-add-repository ppa:mvo/tmp $ sudo sed -i 's/impish/jammy/' /etc/apt/sources.list $ sudo sed -i 's/impish/jammy/' /etc/apt/sources.list.d/mvo-ubuntu-tmp-impish.list $ sudo apt update $ apt list -a snapd [shows the PPA version as the one that will be upgraded to] $ sudo apt full-upgrade -y With that it still hangs, most likely because the *old* prerm is run which will stop snapd during the upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969162 Title: bad interaction between snapd and update-notifier when snapd package is being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded
On a minimal impish system (created with autopkgtest-buildvm) I ran: $ sudo apt install --no-install--recommends snapd update-notifier $ sudo snap install canonical-livepatch $ sudo sed -i 's/impish/jammy/' /etc/apt/sources.list $ sudo apt update $ sudo apt full-upgrade -y and with that I can reproduce the hang. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969162 Title: bad interaction between snapd and update-notifier when snapd package is being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded
I uploaded a cherry pick of Albertos branch with the current jammy snapd plus the fix to https://launchpad.net/~mvo/+archive/ubuntu/tmp/+packages and will test once it's build in there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969162 Title: bad interaction between snapd and update-notifier when snapd package is being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969097] Re: connecting interfaces with a udev rule triggers return to gdm login screen
This could be the solution https://gitlab.gnome.org/GNOME/gdm/-/commit/307c683f00e1711973139837992ca0f6f55314a5 ** Also affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969097 Title: connecting interfaces with a udev rule triggers return to gdm login screen To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1969097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969097] Re: connecting interfaces with a udev rule triggers return to gdm login screen
I just tested it and and with the attached debdiff I can no longer reproduce the problem. ** Patch added: "debdiff with the fix" https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1969097/+attachment/5580697/+files/gdm3_42.0-1ubuntu3.debdiff ** Changed in: gdm (Ubuntu) Status: New => In Progress ** Changed in: gdm (Ubuntu) Importance: Undecided => Critical ** Changed in: snapd Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969097 Title: connecting interfaces with a udev rule triggers return to gdm login screen To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1969097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792656] Re: snapd should depend on fuse for snapfuse
** Changed in: snapd (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792656 Title: snapd should depend on fuse for snapfuse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1792656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set with networkd
** Summary changed: - netplan dbus returns "false" in io.netplan.Netplan.Config.Set + netplan dbus returns "false" in io.netplan.Netplan.Config.Set with networkd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set with networkd To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
The deeper reason appears to be: https://git.launchpad.net/ubuntu/+source/netplan.io/tree/debian/patches/0006-cli- apply-give-some-extra-time-for-networkctl- reload.patch?h=applied/ubuntu/focal-updates#n25 It was a bit hard to find because for the "networkctl" calls in strace there was no corresponding code in the github repo. But after inspecting the package the issue seems to be clear. So there is a 5s timeout that is hit here because the networkctl output is: """ qemu:ubuntu-core-20-64 .../tests/core/netplan-cfg# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 etherroutableconfigured 3 br54 bridge degradedconfiguring 3 links listed. """ I don't know if our test-case is pathological in the sense that nooone would create a br54 interface and then not use it or if this is a real bug. But in any case, that seems to be the root issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set with networkd To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
I can also reproduce this on a minimal 20.04 VM image (created with autopkgtest-buildvm). Running the reproducer script above triggers the same "false" return so it seems to be related to the renderer. I was not able to reproduce it on my desktop with network-manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
The (super naive) diff I used to increase the timeout:
"""
diff --git a/src/dbus.c b/src/dbus.c
index 4d9b17a..78cdafe 100644
--- a/src/dbus.c
+++ b/src/dbus.c
@@ -512,8 +512,8 @@ method_try(sd_bus_message *m, void *userdata, sd_bus_error
*ret_error)
// LCOV_EXCL_STOP
/* wait for the /run/netplan/netplan-try.ready stamp file to appear */
-guint poll_timeout = 500;
-if (seconds > 0 && seconds < 5)
+guint poll_timeout = 1500;
+if (seconds > 0 && seconds < 15)
poll_timeout = seconds * 100;
/* Timeout after up to 5 sec of waiting for the stamp file */
for (int i = 0; i < poll_timeout; i++) {
"""
(just for completness)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967084
Title:
netplan dbus returns "false" in io.netplan.Netplan.Config.Set
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
Fwiw, it might be interessting to see where this time is actually spend - 6s is long for a relatively small config, maybe there is a bug hidding here somewhere that is just masked when we increase the timeout? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
So it looks like the timeout in dbus.c that is hardcoded to 5s is the problem. I patched dbus.c to use a 15s timeout (values was arbitrary) and run the reproducer I get: # time ./repo.sh + cut -d" -f2 + grep object path + dbus-send --type=method_call --system --print-reply --dest=io.netplan.Netplan /io/netplan/Netplan io.netplan.Netplan.Config + objpath=/io/netplan/Netplan/config/ENTPK1 + dbus-send --type=method_call --system --print-reply --dest=io.netplan.Netplan /io/netplan/Netplan/config/ENTPK1 io.netplan.Netplan.Config.Set string:bridges.br54.dhcp4=true string:90-foo method return time=1649663748.713135 sender=:1.93 -> destination=:1.95 serial=6 reply_serial=2 boolean true + dbus-send --type=method_call --system --print-reply --dest=io.netplan.Netplan /io/netplan/Netplan/config/ENTPK1 io.netplan.Netplan.Config.Try uint32:300 method return time=1649663754.663485 sender=:1.93 -> destination=:1.96 serial=8 reply_serial=2 boolean true real0m6.054s user0m0.008s sys 0m0.001s """ So it seems like the timeout just needs to be bigger, probably a lot bigger given that it takes 6s on a reasonable fast amd64 VM. This code will run on pi2 like ARM or RISCV systems :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
Here is a reproducer script """ #!/bin/sh set -ex objpath=$(dbus-send --type=method_call --system --print-reply --dest=io.netplan.Netplan /io/netplan/Netplan io.netplan.Netplan.Config | grep "object path" | cut -d'"' -f2) dbus-send --type=method_call --system --print-reply --dest=io.netplan.Netplan "$objpath" io.netplan.Netplan.Config.Set string:"bridges.br54.dhcp4=true" string:"90-foo" dbus-send --type=method_call --system --print-reply --dest=io.netplan.Netplan "$objpath" io.netplan.Netplan.Config.Try uint32:300 """ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
I managed to capture a debug log from netplan when run via the ddbus comments
in #8. It was a bit tricky (bind mounted utils.py and set debug = True there)
because netplan is coming from a RO location and no way to use the environment
to enable debugging. Unfortunately the log gives me not many hints:
"""
qemu:ubuntu-core-20-64 .../tests/core/netplan-cfg# dbus-send --type=method_call
--system --print-reply --dest=io.netplan.Netplan
/io/netplan/Netplan/config/PCJPK1 io.netplan.Netplan.Config.Try uint32:300
DEBUG:all-en not found in {}
DEBUG:all-eth not found in {'all-en': {'match': {'name': 'en*'}, 'dhcp4': True}}
DEBUG:br54 not found in {}
DEBUG:Merged config:
network:
bridges:
br54:
dhcp4: true
ethernets:
all-en:
dhcp4: true
match:
name: en*
all-eth:
dhcp4: true
match:
name: eth*
version: 2
DEBUG:New interfaces: set()
DEBUG:netplan generated networkd configuration changed, reloading networkd
DEBUG:all-en not found in {}
DEBUG:all-eth not found in {'all-en': {'match': {'name': 'en*'}, 'dhcp4': True}}
DEBUG:br54 not found in {}
DEBUG:Merged config:
network:
bridges:
br54:
dhcp4: true
ethernets:
all-en:
dhcp4: true
match:
name: en*
all-eth:
dhcp4: true
match:
name: eth*
version: 2
DEBUG:no netplan generated NM configuration exists
DEBUG:all-en not found in {}
DEBUG:all-eth not found in {'all-en': {'match': {'name': 'en*'}, 'dhcp4': True}}
DEBUG:br54 not found in {}
DEBUG:Merged config:
network:
bridges:
br54:
dhcp4: true
ethernets:
all-en:
dhcp4: true
match:
name: en*
all-eth:
dhcp4: true
match:
name: eth*
version: 2
DEBUG:Link changes: {}
DEBUG:all-en not found in {}
DEBUG:all-eth not found in {'all-en': {'match': {'name': 'en*'}, 'dhcp4': True}}
DEBUG:Merged config:
network:
ethernets:
all-en:
dhcp4: true
match:
name: en*
all-eth:
dhcp4: true
match:
name: eth*
version: 2
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for ens3
DEBUG:netplan triggering .link rules for br54
DEBUG:all-en not found in {}
DEBUG:all-eth not found in {'all-en': {'match': {'name': 'en*'}, 'dhcp4': True}}
DEBUG:br54 not found in {}
DEBUG:Merged config:
network:
bridges:
br54:
dhcp4: true
ethernets:
all-en:
dhcp4: true
match:
name: en*
all-eth:
dhcp4: true
match:
name: eth*
version: 2
method return time=1649661702.221874 sender=:1.40 -> destination=:1.45
serial=12 reply_serial=2
boolean false
"""
but maybe it's more useful for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967084
Title:
netplan dbus returns "false" in io.netplan.Netplan.Config.Set
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
Fwiw I was able to reproduce this on core20 via: """ $ dbus-send --type=method_call --system --print-reply --dest=io.netplan.Netplan /io/netplan/Netplan io.netplan.Netplan.Config [got the /io/netplan/Netplan/config/4ZMNK1 path here] $ dbus-send --type=method_call --system --print-reply --dest=io.netplan.Netplan /io/netplan/Netplan/config/4ZMNK1 io.netplan.Netplan.Config.Set string:"bridges.br54.dhcp4=true" string:"90-foo" [got true here] $ dbus-send --type=method_call --system --print-reply --dest=io.netplan.Netplan /io/netplan/Netplan/config/4ZMNK1 io.netplan.Netplan.Config.Try uint32:300 [got false here] """ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
I was wrong and looked at old code. There is now a case where the dbus Try()
returns "false". It was added in e19441c3 and has:
"""
+/* wait for the /run/netplan/netplan-try.ready stamp file to appear */
+guint poll_timeout = 500;
+if (seconds > 0 && seconds < 5)
+poll_timeout = seconds * 100;
+/* Timeout after up to 5 sec of waiting for the stamp file */
+for (int i = 0; i < poll_timeout; i++) {
+if (stat(netplan_try_stamp, ) == 0)
+break;
+usleep(1000 * 10);
+}
+if (stat(netplan_try_stamp, ) != 0) {
+ g_debug("cannot find %s stamp file", netplan_try_stamp);
+ return sd_bus_reply_method_return(m, "b", false);
+}
"""
Maybe 5s is a bit low on slow systems, maybe something else is doing on.
I also wonder if netplan should report some sort of error in this case
to provide more context?
** Description changed:
As part of our snapd core integration testing we run the spread test for
netplan on a UC20 PI device.
On this device our test fails with:
"""
2022-03-25 14:33:00 Error executing
external:ubuntu-core-20-arm-32:tests/core/netplan-cfg
(external:ubuntu-core-20-arm-32) :
-
+ echo 'Getting version works'
Getting version works
+ snap get system system.network.netplan.network.version
+ MATCH '^2$'
+ echo 'Getting the full document works and it is valid json'
Getting the full document works and it is valid json
+ jq .
+ snap get -d system system.network.netplan
{
"system.network.netplan": {
"network": {
"ethernets": {
"eth0": {
"dhcp4": true,
"match": {
"macaddress": "b8:27:eb:41:42:43"
},
"set-name": "eth0"
}
},
"version": 2
}
}
}
+ echo 'Check that setting adding a br54 interface via netplan works'
Check that setting adding a br54 interface via netplan works
+ snap set system system.network.netplan.network.bridges.br54.dhcp4=true
error: cannot perform the following tasks:
- Run configure hook of "core" snap (run hook "configure": cannot try netplan
config: no specific reason returned from netplan)
-
"""
This error means that snapd called io.netplan.Netplan.Config.Set and got
a "false" without an error from that call (c.f.
https://github.com/snapcore/snapd/blob/master/overlord/configstate/configcore/netplan.go#L218)
+
+
+ [edit: now this also fails in GCE testing on amd64 and this looks like a
regression as this used to work].
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967084
Title:
netplan dbus returns "false" in io.netplan.Netplan.Config.Set
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
I'm sorry, my initial comment was wrong - we do have a "false" path in "Try()" now, I was looking at old code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
Sergio reported that he sees "systemd-networkd[804]: Could not set hostname: Permission denied" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
It's pretty consistent now, here is a strace log from uc20 in google that shows the calls from dbus: https://paste.ubuntu.com/p/hmjDQYYc9S/ ** Also affects: netplan Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
We also observe this behavior now on UC20 systems that run with amd64, e.g. in this run: https://github.com/snapcore/snapd/runs/5876437750?check_suite_focus=true The log looks like this: """ 2022-04-07T22:28:41.1746417Z Apr 07 22:28:33 apr072148-447340 snapd[3454]: netplan.go:122: DEBUG: using netplan config snapshot /io/netplan/Netplan/config/UY2RJ1 2022-04-07T22:28:41.1747073Z Apr 07 22:28:34 apr072148-447340 snapd[3454]: netplan.go:122: DEBUG: using netplan config snapshot /io/netplan/Netplan/config/FKW9J1 2022-04-07T22:28:41.1747878Z Apr 07 22:28:34 apr072148-447340 snapd[3454]: retry.go:49: DEBUG: Retrying https://api.snapcraft.io/v2/snaps/info/core?architecture=amd64=download, attempt 1, elapsed time=20.694µs ... 2022-04-07T22:28:41.1830683Z Apr 07 22:28:34 apr072148-447340 snapd[3454]: retry.go:61: DEBUG: The retry loop for https://api.snapcraft.io/api/v1/snaps/download/99T7MUlRhtI3U0QFgl5mXXESAiSwt776_12834.snap finished after 1 retries, elapsed time=229.430054ms, status: 200 2022-04-07T22:28:41.1831580Z Apr 07 22:28:34 apr072148-447340 snapd[3454]: netplan.go:228: DEBUG: store reachable before netplan changes: true (tried 0 times) 2022-04-07T22:28:41.1832435Z Apr 07 22:28:40 apr072148-447340 snapd[3454]: task.go:343: DEBUG: 2022-04-07T22:28:40Z ERROR run hook "configure": cannot try netplan config: no specific reason returned from netplan """ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] Re: netplan dbus returns "false" in io.netplan.Netplan.Config.Set
Hm, what is super mysterious is that AFAICT from reading https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/netplan.io/0.104-0ubuntu2~20.04.1/netplan.io_0.104-0ubuntu2~20.04.1.dsc there is nothing in `method_apply()` code path that could trigger this. I only see that `sd_bus_error_setf()` is called or `return sd_bus_reply_method_return(m, "b", true);`. However there is a line in "_try_accept" that says: /* ATTENTION: There might be a race here: * When this accept/reject method is called at the same time as the 'netplan try' * python process is reverting and closing itself. Not sure what to do about it... * Maybe this needs to be fixed in python code, so that the * 'netplan.terminal.InputRejected' exception (i.e. self-revert) cannot be * interrupted by another exception/signal */ But could be a red-herring as it would not explain getting "false", I would expect some sort of dbus error if this happens. Fwiw on the Pi4 and on real amd64 devices this is not happening which would indicate some sort of race. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967084 Title: netplan dbus returns "false" in io.netplan.Netplan.Config.Set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1967084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967084] [NEW] netplan dbus returns "false" in io.netplan.Netplan.Config.Set
Public bug reported:
As part of our snapd core integration testing we run the spread test for
netplan on a UC20 PI device.
On this device our test fails with:
"""
2022-03-25 14:33:00 Error executing
external:ubuntu-core-20-arm-32:tests/core/netplan-cfg
(external:ubuntu-core-20-arm-32) :
-
+ echo 'Getting version works'
Getting version works
+ snap get system system.network.netplan.network.version
+ MATCH '^2$'
+ echo 'Getting the full document works and it is valid json'
Getting the full document works and it is valid json
+ jq .
+ snap get -d system system.network.netplan
{
"system.network.netplan": {
"network": {
"ethernets": {
"eth0": {
"dhcp4": true,
"match": {
"macaddress": "b8:27:eb:41:42:43"
},
"set-name": "eth0"
}
},
"version": 2
}
}
}
+ echo 'Check that setting adding a br54 interface via netplan works'
Check that setting adding a br54 interface via netplan works
+ snap set system system.network.netplan.network.bridges.br54.dhcp4=true
error: cannot perform the following tasks:
- Run configure hook of "core" snap (run hook "configure": cannot try netplan
config: no specific reason returned from netplan)
-
"""
This error means that snapd called io.netplan.Netplan.Config.Set and got
a "false" without an error from that call (c.f.
https://github.com/snapcore/snapd/blob/master/overlord/configstate/configcore/netplan.go#L218)
** Affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- As part of our ubuntu core integration testing we run the spread test
- for netplan on a PI device.
+ As part of our snapd core integration testing we run the spread test for
+ netplan on a UC20 PI device.
On this device our test fails with:
"""
- 2022-03-25 14:33:00 Error executing
external:ubuntu-core-20-arm-32:tests/core/netplan-cfg
(external:ubuntu-core-20-arm-32) :
+ 2022-03-25 14:33:00 Error executing
external:ubuntu-core-20-arm-32:tests/core/netplan-cfg
(external:ubuntu-core-20-arm-32) :
-
+ echo 'Getting version works'
Getting version works
+ snap get system system.network.netplan.network.version
+ MATCH '^2$'
+ echo 'Getting the full document works and it is valid json'
Getting the full document works and it is valid json
+ jq .
+ snap get -d system system.network.netplan
{
- "system.network.netplan": {
- "network": {
- "ethernets": {
- "eth0": {
- "dhcp4": true,
- "match": {
- "macaddress": "b8:27:eb:41:42:43"
- },
- "set-name": "eth0"
- }
- },
- "version": 2
- }
- }
+ "system.network.netplan": {
+ "network": {
+ "ethernets": {
+ "eth0": {
+ "dhcp4": true,
+ "match": {
+ "macaddress": "b8:27:eb:41:42:43"
+ },
+ "set-name": "eth0"
+ }
+ },
+ "version": 2
+ }
+ }
}
+ echo 'Check that setting adding a br54 interface via netplan works'
Check that setting adding a br54 interface via netplan works
+ snap set system system.network.netplan.network.bridges.br54.dhcp4=true
error: cannot perform the following tasks:
- Run configure hook of "core" snap (run hook "configure": cannot try netplan
config: no specific reason returned from netplan)
-
"""
This error means that snapd called io.netplan.Netplan.Config.Set and got
a "false" without an error from that call (c.f.
https://github.com/snapcore/snapd/blob/master/overlord/configstate/configcore/netplan.go#L218)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967084
Title:
netplan dbus returns "false" in io.netplan.Netplan.Config.Set
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1967084/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Changed in: shadow (Ubuntu Bionic) Status: New => In Progress ** Changed in: shadow (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959912] Re: libmount: multiple user options are not supported
** Description changed: Only a single user option (the first one) is taken into consideration when mounting a new disk regardless of the filesystem. # mount /dev/sdd1 /mnt/cruizer -onodev,ro,x-gdu.hide,x-gvfs-hide # findmnt --mtab /mnt/cruizer TARGET SOURCEFSTYPE OPTIONS /mnt/cruizer /dev/sdd1 fusebl ro,nodev,relatime,user_id=0,group_id=0,allow_oth # grep /mnt/cruizer /run/mount/utab SRC=/dev/sdd1 TARGET=/mnt/cruizer ROOT=/ OPTS=x-gdu.hide - Reported issue: https://github.com/util-linux/util-linux/issues/1583 + Reported issues: https://github.com/util-linux/util-linux/issues/1429 and https://github.com/util-linux/util-linux/issues/1583 Confirmed fix with upstream commit: https://github.com/util-linux/util-linux/commit/d85f45d5ddb020b9858356b4c2c91d962ac7e6d7 ** Also affects: util-linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959912 Title: libmount: multiple user options are not supported To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1959912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959570] [NEW] netplan crashes on UbuntuCore with the network-manager snap installed
Public bug reported: When using the netplan-dbus API on Ubuntu Core and the network-manager renderer the "netplan-dbus" appication will crash. To reproduce take a UC20 or UC22 system and run: ``` $ sudo snap set system system.network.netplan.network.bridges.br54.dhcp4=true ``` (which in effect just drives the dbus API of netplan). After that the network is lost. When manually restarting it the error is: ``` error: cannot perform the following tasks: - Run configure hook of "core" snap (run hook "configure": cannot try netplan config: no specific reason returned from netplan and cannot cancel netplan config: Unknown object '/io/netplan/Netplan/config/VDDSG1'.) ``` and the journal reports: ``` Jan 31 10:46:04 ubuntu sudo[1746]: mvo : TTY=pts/0 ; PWD=/home/mvo ; USER=root ; COMMAND=/usr/bin/snap set system system.network.netplan.network.bridges.br54.dhcp4=true Jan 31 10:46:04 ubuntu sudo[1746]: pam_unix(sudo:session): session opened for user root(uid=0) by mvo(uid=1000) Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: Traceback (most recent call last): Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/share/netplan/netplan/cli/commands/try_command.py", line 99, in command_try Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: NetplanApply().command_apply(run_generate=True, sync=True, exit_on_error=False, state_dir=self.state) Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/share/netplan/netplan/cli/commands/apply.py", line 272, in command_apply Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: if b'\nconnected' in subprocess.check_output(cmd, env=env): Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/lib/python3.9/subprocess.py", line 424, in check_output Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/lib/python3.9/subprocess.py", line 505, in run Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: with Popen(*popenargs, **kwargs) as process: Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/lib/python3.9/subprocess.py", line 951, in __init__ Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: self._execute_child(args, executable, preexec_fn, close_fds, Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/lib/python3.9/subprocess.py", line 1821, in _execute_child Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: raise child_exception_type(errno_num, err_msg, err_filename) Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: FileNotFoundError: [Errno 2] No such file or directory: 'nmcli' Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: During handling of the above exception, another exception occurred: Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: Traceback (most recent call last): Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/sbin/netplan", line 23, in Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: netplan.main() Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/share/netplan/netplan/cli/core.py", line 50, in main Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: self.run_command() Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/share/netplan/netplan/cli/utils.py", line 315, in run_command Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: self.func() Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/share/netplan/netplan/cli/commands/try_command.py", line 81, in run Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: self.run_command() Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/share/netplan/netplan/cli/utils.py", line 315, in run_command Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: self.func() Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/share/netplan/netplan/cli/commands/try_command.py", line 113, in command_try Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: self.revert() Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/share/netplan/netplan/cli/commands/try_command.py", line 143, in revert Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: NetplanApply().command_apply(run_generate=False, sync=True, exit_on_error=False, state_dir=tempdir) Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/share/netplan/netplan/cli/commands/apply.py", line 272, in command_apply Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: if b'\nconnected' in subprocess.check_output(cmd, env=env): Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/lib/python3.9/subprocess.py", line 424, in check_output Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: File "/usr/lib/python3.9/subprocess.py", line 505, in run Jan 31 10:46:05 ubuntu io.netplan.Netplan[1763]: with Popen(*popenargs, **kwargs) as process: Jan 31
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Patch added: "debdiff for the PPA jammy test upload" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5557912/+files/shadow_4.8.1-2ubuntu2~ppa1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Patch added: "Proposed (untested) patch" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5557911/+files/shadow-lp1959375.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] [NEW] [SRU] Please support group manipulation with "extrausers"
Public bug reported: Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Affects: shadow (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: shadow (Ubuntu Focal) Importance: Undecided Status: New ** Affects: shadow (Ubuntu Impish) Importance: Undecided Status: New ** Affects: shadow (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: shadow (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: shadow (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: shadow (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: shadow (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955137] Re: [SRU] 2.54
** Description changed: - Placeholder + This is a new version of snapd. + + The changelog is available here + https://github.com/snapcore/snapd/blob/2.54.2/packaging/ubuntu-16.04/changelog, + the raw git changelog is available here: + https://github.com/snapcore/snapd/commits/2.54.2 (note that the debian + changelog is auto-generated from the merges of the git commits so there + is usually no need to look at the raw git commits). + + The snappy team released a new release that we want SRU into bionc+. The + new process described in https://wiki.ubuntu.com/SnapdUpdates was used + and we have done integration-tests on the snappy images, autopkgtests on + classic and unit tests. + + GitHub Actions test runs can be found at + https://github.com/snapcore/snapd/actions?query=branch%3Arelease%2F2.54.2 ** Also affects: snapd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955137 Title: [SRU] 2.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1955137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955137] [NEW] [SRU] 2.54
Public bug reported: Placeholder ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955137 Title: [SRU] 2.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1955137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946127] Re: [SRU] 2.53
** Also affects: snapd (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: snapd (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946127 Title: [SRU] 2.53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1946127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Fwiw, it looks like the latest core18 edge build that includes https://launchpad.net/ubuntu/+source/cloud-init/21.4-0ubuntu1~18.04.1 make the problem go away. It seems https://bugs.launchpad.net/cloud- init/+bug/1946003 is what caused it. The old code had a udev rule that would call into the cloud-init python code for each "net|block" device that got added that spiked the CPU when a block device was added which then made the race that seems to exist much more likely to appear. Given what Dan said above something deeper seems to be still lurking here that probably needs fixing (but will be harder to trigger now). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
I attached the /run/cloud-init and /var/log/cloud-init logs of the good/bad run - I looked over the diff via "diff -u <(cut -f 4- -d: /tmp/cloud-init-good-core18-r2206/cloud-init.log) <(cut -f 4- -d: /tmp/cloud-init-bad-core18-r2208/cloud-init.log)" but couldn't see anything standing out there (but I'm really not a cloud-init guy). Alberto mentioned that latest cloud-init adds "hotplug" (https://github.com/canonical/cloud-init/pull/936) which might be related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
** Attachment added: "cloud-init logs for the "good" run" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+attachment/5542024/+files/cloud-init-good-core18-r2206.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
** Attachment added: "cloud-init logs for the "bad" run" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+attachment/5542025/+files/cloud-init-bad-core18-r2208.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
I spend a bit more time bisecting the various core18 snaps to see at
what revision the failure started to become reproducible. Interestingly
I found that it started with r2208 AFAICT. It's all a bit annoying
because it's a race so I don't trust it 100% but the previous r2206 got
2 good runs in a row but the r2208 failed also two times in a row. The
only change there is cloud-init
https://people.canonical.com/~mvo/core18-changes/html/edge/'20210928'r2206_'20210930'r2208.html
which might explain why we see the failure in our integration tests in
GCE but not inside QEMU. Unfortuantely the cloud-init diff is pretty
big.
For reference, here is what I ran:
"""
$ git status
On branch tests-use-core18-from-gce
Your branch is up to date with 'sergiocazzolato/tests-use-core18-from-gce'.
$ git describe
2.53.1-460-gd171d434ed
diff --git a/overlord/devicestate/devicestate.go
b/overlord/devicestate/devicestate.go
index d40b32bcbd..77ec3fc0a8 100644
--- a/overlord/devicestate/devicestate.go
+++ b/overlord/devicestate/devicestate.go
@@ -117,6 +117,8 @@ func canAutoRefresh(st *state.State) (bool, error) {
if !seeded {
return false, nil
}
+ // HACK
+ return false, nil
// Try to ensure we have an accurate time before doing any
// refreshy stuff. Note that this call will not block.
diff --git a/spread.yaml b/spread.yaml
index 0aef5dea7c..68cbdc09b7 100644
--- a/spread.yaml
+++ b/spread.yaml
@@ -37,7 +37,7 @@ environment:
MANAGED_DEVICE: "false"
# a global setting for LXD channel to use in the tests
LXD_SNAP_CHANNEL: "latest/edge"
-UBUNTU_IMAGE_SNAP_CHANNEL: "latest/candidate"
+UBUNTU_IMAGE_SNAP_CHANNEL: "beta/1.11"
CORE_CHANNEL: '$(HOST: echo "${SPREAD_CORE_CHANNEL:-edge}")'
BASE_CHANNEL: '$(HOST: echo "${SPREAD_BASE_CHANNEL:-edge}")'
KERNEL_CHANNEL: '$(HOST: echo "${SPREAD_KERNEL_CHANNEL:-edge}")'
diff --git a/tests/lib/prepare.sh b/tests/lib/prepare.sh
index e6b984c4d0..14b9608fb9 100755
--- a/tests/lib/prepare.sh
+++ b/tests/lib/prepare.sh
@@ -973,7 +973,26 @@ EOF
fi
if os.query is-core18; then
-curl -s -o core18.snap
https://storage.googleapis.com/snapd-spread-tests/snaps/core18_20211102_amd64.snap
+# GOOD
+#curl --insecure -o core18.snap
https://people.canonical.com/~mvo/tmp/CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6_2081.snap
+# GOOD
+#curl --insecure -o core18.snap
https://people.canonical.com/~mvo/tmp/CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6_2128.snap
+# BAD
+#curl --insecure -o core18.snap
https://people.canonical.com/~mvo/tmp/CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6_2239.snap
+# GOOD
+#curl --insecure -o core18.snap
https://people.canonical.com/~mvo/tmp/CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6_2141.snap
+# GOOD (3 good runs in a row)
+#curl --insecure -o core18.snap
https://people.canonical.com/~mvo/tmp/CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6_2191.snap
+# BAD
+#curl --insecure -o core18.snap
https://people.canonical.com/~mvo/tmp/CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6_2213.snap
+# BAD
+#curl --insecure -o core18.snap
https://people.canonical.com/~mvo/tmp/CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6_2228.snap
+# BAD
+#curl --insecure -o core18.snap
https://people.canonical.com/~mvo/tmp/CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6_2219.snap
+# BAD
+curl --insecure -o core18.snap
https://people.canonical.com/~mvo/tmp/CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6_2208.snap
+# GOOD (2 good run in a row)
+#curl --insecure -o core18.snap
https://people.canonical.com/~mvo/tmp/CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6_2206.snap
EXTRA_FUNDAMENTAL="$EXTRA_FUNDAMENTAL --snap $PWD/core18.snap"
fi
$ $GOPATH/bin/spread -repeat 2
google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy
...
"""
Each run takes ~12min so it's a bit cumbersome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails to activate mount units in Ubuntu Core 18
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
@Dan Thanks, this find about BindsTo is super interesting! It's not something that snapd writes out, it's curious where this comes from. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
I spend a bit of quality time with this bug today and it seems there is (also?)
a kernel dimension to it. I ran the following:
"""
$ git status
On branch tests-use-core18-from-gce
Your branch is up to date with 'sergiocazzolato/tests-use-core18-from-gce'.
$ git diff
diff --git a/overlord/devicestate/devicestate.go
b/overlord/devicestate/devicestate.go
index d40b32bcbd..77ec3fc0a8 100644
--- a/overlord/devicestate/devicestate.go
+++ b/overlord/devicestate/devicestate.go
@@ -117,6 +117,8 @@ func canAutoRefresh(st *state.State) (bool, error) {
if !seeded {
return false, nil
}
+ // HACK
+ return false, nil
// Try to ensure we have an accurate time before doing any
// refreshy stuff. Note that this call will not block.
diff --git a/spread.yaml b/spread.yaml
index 0aef5dea7c..68cbdc09b7 100644
--- a/spread.yaml
+++ b/spread.yaml
@@ -37,7 +37,7 @@ environment:
MANAGED_DEVICE: "false"
# a global setting for LXD channel to use in the tests
LXD_SNAP_CHANNEL: "latest/edge"
-UBUNTU_IMAGE_SNAP_CHANNEL: "latest/candidate"
+UBUNTU_IMAGE_SNAP_CHANNEL: "beta/1.11"
CORE_CHANNEL: '$(HOST: echo "${SPREAD_CORE_CHANNEL:-edge}")'
BASE_CHANNEL: '$(HOST: echo "${SPREAD_BASE_CHANNEL:-edge}")'
KERNEL_CHANNEL: '$(HOST: echo "${SPREAD_KERNEL_CHANNEL:-edge}")'
diff --git a/tests/lib/prepare.sh b/tests/lib/prepare.sh
index e6b984c4d0..215d0611be 100755
--- a/tests/lib/prepare.sh
+++ b/tests/lib/prepare.sh
@@ -973,8 +973,8 @@ EOF
fi
if os.query is-core18; then
-curl -s -o core18.snap
https://storage.googleapis.com/snapd-spread-tests/snaps/core18_20211102_amd64.snap
-EXTRA_FUNDAMENTAL="$EXTRA_FUNDAMENTAL --snap $PWD/core18.snap"
+curl --insecure -o pc-kernel.snap
https://people.canonical.com/~mvo/tmp/pYVQrBcKmBa0mZ4CCN7ExT6jH8rY1hza_831.snap
+EXTRA_FUNDAMENTAL="$EXTRA_FUNDAMENTAL --snap $PWD/pc-kernel.snap"
fi
/snap/bin/ubuntu-image snap \
"""
which essentially moves the image to a 2 month older 4.14 kernel. With that I
could not reproduce the error for three subsequent runs of 2 repeats.
However when I disabled this code and use the current "18/edge" pc-
kernel (or stable, it's the same revision) then I can trigger the bug
right away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails to activate mount units in Ubuntu Core 18
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
About the question about Focal/hirsute/uc20 - we have not observed the issue there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Fwiw, the patch debian/lp1934147/0001-core-add-a-new-unit-method- catchup.patch is part of a fairly large patchset (https://github.com/systemd/systemd/pull/9200/commits) so maybe something is missing there? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Just for the record, I also did another run with: https://storage.googleapis.com/snapd-spread- tests/snaps/core18_20211102_amd64.snap and that also fails right away: """ $ git status On branch tests-use-core18-from-gce Your branch is up to date with 'sergiocazzolato/tests-use-core18-from-gce'. $ git diff [empty] $ $GOPATH/bin/spread -repeat 100 google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy ... 2021-11-08 12:13:57 Error executing google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081101-381415) : - + . /home/gopath/src/github.com/snapcore/snapd/tests/lib/disabled-svcs.sh ++ SVC_MISSING_ERR_MSG='state.json is missing last-active-disabled-services in it:' + echo 'CASE 1' CASE 1 + echo 'Install the snap' Install the snap + snap install --dangerous disabled-svcs-kept_1.0_all.snap disabled-svcs-kept 1.0 installed + echo 'Check that state.json doesn'\''t contain last-active-disabled-services' Check that state.json doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'CASE 2' CASE 2 + echo 'Disable a service in the snap' Disable a service in the snap + snap stop --disable disabled-svcs-kept.svc Stopped. + echo 'Check that it was actually disabled' Check that it was actually disabled + retry -n 10 --wait 1 sh -c 'snap services disabled-svcs-kept | MATCH "disabled-svcs-kept\\.svc\\s+disabled\\s+inactive"' + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'Disable the whole snap' Disable the whole snap + snap disable disabled-svcs-kept disabled-svcs-kept disabled + echo 'Check that state.json DOES contain last-active-disabled-services' Check that state.json DOES contain last-active-disabled-services + check_state_json_yes_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' '!=' null 'state.json has invalid last-active-disabled-services in it:' + echo 'Enable the whole snap' Enable the whole snap + snap enable disabled-svcs-kept disabled-svcs-kept enabled + echo 'Check that the service is still disabled' Check that the service is still disabled + MATCH 'disabled-svcs-kept\.svc\s+disabled\s+inactive' + snap services disabled-svcs-kept + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'CASE 3' CASE 3 + echo 'Refresh the snap' Refresh the snap + snap install --dangerous disabled-svcs-kept_1.0_all.snap disabled-svcs-kept 1.0 installed + echo 'Check that the service is still disabled' Check that the service is still disabled + MATCH 'disabled-svcs-kept\.svc\s+disabled\s+inactive' + snap services disabled-svcs-kept + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'CASE 4' CASE 4 + echo 'Revert the snap' Revert the snap + snap revert disabled-svcs-kept --revision=x1 disabled-svcs-kept reverted to 1.0 + echo 'Check that the service is still disabled' Check that the service is still disabled + MATCH 'disabled-svcs-kept\.svc\s+disabled\s+inactive' + snap services disabled-svcs-kept + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'Refresh back to the new revision to unmark it as blacklisted' Refresh back to the new revision to unmark it as blacklisted + snap refresh disabled-svcs-kept --revision=x2
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Thanks Lukas for providing this revert of f0831ed2a03fcef582660be1c3b1a9f3e267e656. Using https://people.ubuntu.com/~slyon/uc18/core18_20211105_amd64.snap I can no longer reproduce the isue. To make it easier to reproduce what I did: """ $ git status On branch tests-use-core18-from-gce Your branch is up to date with 'sergiocazzolato/tests-use-core18-from-gce'. ... $ git diff diff --git a/tests/lib/prepare.sh b/tests/lib/prepare.sh index e6b984c4d0..5c58a55b2f 100755 --- a/tests/lib/prepare.sh +++ b/tests/lib/prepare.sh @@ -973,7 +973,7 @@ EOF fi if os.query is-core18; then -curl -s -o core18.snap https://storage.googleapis.com/snapd-spread-tests/snaps/core18_20211102_amd64.snap +curl -s -o core18.snap https://people.ubuntu.com/~slyon/uc18/core18_20211105_amd64.snap EXTRA_FUNDAMENTAL="$EXTRA_FUNDAMENTAL --snap $PWD/core18.snap" fi $ $GOPATH/bin/spread -repeat 100 google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy ... 2021-11-08 11:39:41 Preparing google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081028-580805)... 2021-11-08 11:39:53 Executing google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081028-580805) (1/1)... 2021-11-08 11:40:49 Restoring google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081028-580805)... 2021-11-08 11:41:00 Preparing google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081028-580805)... ... """ To validate my findings I'm also running the same test against core18 in stable and it fails very quickly: """ $ git status HEAD detached at upstream/master $ git describe 2.53.1-480-g2c39794030 $ $GOPATH/bin/spread -repeat 100 google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy 2021-11-08 11:58:46 Error executing google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081048-716592) : - + . /home/gopath/src/github.com/snapcore/snapd/tests/lib/disabled-svcs.sh ++ SVC_MISSING_ERR_MSG='state.json is missing last-active-disabled-services in it:' + echo 'CASE 1' CASE 1 + echo 'Install the snap' Install the snap + snap install --dangerous disabled-svcs-kept_1.0_all.snap disabled-svcs-kept 1.0 installed + echo 'Check that state.json doesn'\''t contain last-active-disabled-services' Check that state.json doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'CASE 2' CASE 2 + echo 'Disable a service in the snap' Disable a service in the snap + snap stop --disable disabled-svcs-kept.svc Stopped. + echo 'Check that it was actually disabled' Check that it was actually disabled + retry -n 10 --wait 1 sh -c 'snap services disabled-svcs-kept | MATCH "disabled-svcs-kept\\.svc\\s+disabled\\s+inactive"' + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'Disable the whole snap' Disable the whole snap + snap disable disabled-svcs-kept disabled-svcs-kept disabled + echo 'Check that state.json DOES contain last-active-disabled-services' Check that state.json DOES contain last-active-disabled-services + check_state_json_yes_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' '!=' null 'state.json has invalid last-active-disabled-services in it:' + echo 'Enable the whole snap' Enable the whole snap + snap enable disabled-svcs-kept disabled-svcs-kept enabled + echo 'Check that the service is still disabled' Check that the service is still disabled + MATCH 'disabled-svcs-kept\.svc\s+disabled\s+inactive' + snap services disabled-svcs-kept + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'CASE 3' CASE 3 + echo 'Refresh the snap' Refresh the snap + snap install --dangerous disabled-svcs-kept_1.0_all.snap disabled-svcs-kept 1.0 installed + echo 'Check that the service is still disabled' Check that the service is still disabled + MATCH 'disabled-svcs-kept\.svc\s+disabled\s+inactive' + snap services
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
We created a test PR that uses this core18 snap build in https://github.com/snapcore/snapd/pull/11015 - we are still running tests but it seems the error is still there :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942930] Re: Unset a subtree crashes
Hm, maybe I'm holding it wrong (again) but I'm not sure this is fully fixed: $ apt list netplan.io netplan.io/now 0.103-0ubuntu5~21.04.2 amd64 [installed,local] $ $ zcat /usr/share/doc/netplan.io/changelog.Debian.gz |head -n 6 netplan.io (0.103-0ubuntu5~21.04.2) hirsute; urgency=medium * Backport patches from impish: + Add d/p/0006-netplan-set-make-it-possible-to-unset-a-whole-devtyp.patch: Fix unset of a devtype subtree, e.g. "netplan set network.ethernets=null" (LP: #1942930) $ netplan get network: renderer: NetworkManager version: 2 netplan set network=null Traceback (most recent call last): File "/usr/sbin/netplan", line 23, in netplan.main() File "/usr/share/netplan/netplan/cli/core.py", line 50, in main self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 310, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/set.py", line 53, in run self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 310, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/set.py", line 103, in command_set hints = self.split_tree_by_hint(set_tree) File "/usr/share/netplan/netplan/cli/commands/set.py", line 59, in split_tree_by_hint for devtype in network: TypeError: 'NoneType' object is not iterable But maybe that is a different bug that needs to be reported differently. Anyway, I can probably work around this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942930 Title: Unset a subtree crashes To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1942930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
I distro patched the impish version of snapd with the fix from Ian and uploaded a new version: https://launchpad.net/ubuntu/impish/+queue?queue_state=1_text=snapd with the fix as 2.53+21.10ubuntu1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946127] [NEW] [SRU] 2.53
Public bug reported: This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.53/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.53 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The snappy team released a new release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. GitHub Actions test runs can be found at https://github.com/snapcore/snapd/actions?query=branch%3Arelease%2F2.53 ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946127 Title: [SRU] 2.53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1946127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1505670] Re: "uncaptured python exception"
My apologizes that this totally was not on my radar. I applied the patch (thank you!) and moved the code from bzr to git, added a gbp.conf and pushed to GH for now (but maybe this really should go to salsa instead). I hope I will be able to release a new .16 release with these changes (and the most recent Debian NMU changes). Sorry again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1505670 Title: "uncaptured python exception" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1505670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944988] Re: [FeatureFreezeException] snapd 2.53~pre1
** Changed in: snapd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944988 Title: [FeatureFreezeException] snapd 2.53~pre1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1944988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944988] Re: [FeatureFreezeException] snapd 2.53~pre1
This got accepted into impish now. ** Changed in: snapd (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944988 Title: [FeatureFreezeException] snapd 2.53~pre1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1944988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944988] Re: [FeatureFreezeException] snapd 2.53~pre1
The build log on impish: https://launchpad.net/~mvo/+archive/ubuntu/tmp/+build/22111395 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944988 Title: [FeatureFreezeException] snapd 2.53~pre1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1944988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944988] [NEW] [FeatureFreezeException] snapd 2.53~pre1
Public bug reported: Snapd needs to be updated to support cgroups v2 and also need to cater for some changes in libc. This is why we would like to ask for a feature freeze exception for snapd to upload 2.53~pre1 and eventually 2.53 into impish. Unfortunately it's very hard to backport this in isolation as the cgroup work required a lot of internal changes that make it unsuitable for this to be cherry picked. We keep building/testing snapd in our spread based automatic VM testing, I will provide a log. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944988 Title: [FeatureFreezeException] snapd 2.53~pre1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1944988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
This is now uploaded to impish as snapd_2.53~pre1.git19b68f708_source.changes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
** Changed in: snapd (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935667] Re: snapd FTBFS when built with libfuse3-dev
This is merged now in: https://github.com/snapcore/snapd/pull/10524 and will be part of the next release. ** Changed in: snapd (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935667 Title: snapd FTBFS when built with libfuse3-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1935667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933827] Re: Symlink incorrectly installs to a sub-directory related to source name (github: 80)
** Also affects: zmk (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: zmk (Ubuntu) Status: New => Fix Released ** Changed in: zmk (Ubuntu Hirsute) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933827 Title: Symlink incorrectly installs to a sub-directory related to source name (github: 80) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zmk/+bug/1933827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935667] Re: snapd FTBFS when built with libfuse3-dev
Thanks for the patch! For us it's slightly more complicated because we want to make sure that snapd keeps building (ideally unchanged) back to 16.04. We will look a bit more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935667 Title: snapd FTBFS when built with libfuse3-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1935667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935667] Re: Please switch to fuse3
** Changed in: snapd (Ubuntu) Status: New => Triaged ** Changed in: snapd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935667 Title: Please switch to fuse3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1935667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
** Description changed: Snapd will soon support to have DTBs in the kernel snap that are automatically installed on kernel refreshes. To support this, please add the following file to the pi-kernel: This should also add "assumes: [kernel-assets]" to the meta/snap.yaml so that the updated kernel/gadget are only used by a snap version that understand this, see https://github.com/snapcore/snapd/pull/ $ cat meta/kernel.yaml assets: pidtbs: update: true content: - - dtbs/broadcom/ - - dtbs/overlays/ + - dtbs/ - This will allow the gadget to select DTBs from the kernel. The gadget - needs to be updated to have all dtb files removed. And the gadget.yaml - needs to change to something like + This will allow the gadget to select DTBs from the kernel. The arm64 + gadget needs to be updated to have all dtb files removed. And the + gadget.yaml needs to change to something like $ head -20 meta/gadget.yaml device-tree: bcm2709-rpi-3-b-plus volumes: pi: schema: mbr bootloader: u-boot structure: - name: ubuntu-seed role: system-seed filesystem: vfat type: 0C size: 1200M content: - source: $kernel:pidtbs/dtbs/broadcom/ target: / - source: $kernel:pidtbs/dtbs/overlays/ target: /overlays - source: boot-assets/ target: / - name: ubuntu-boot role: system-boot ... + + AFAICT the armhf needs to be updated differently because the layout + of the dtbs folder is different in the armhf kernel: + + $ head -20 meta/gadget.yaml + volumes: + pi: + schema: mbr + bootloader: u-boot + structure: + - name: ubuntu-seed + role: system-seed + filesystem: vfat + type: 0C + size: 1200M + content: + - source: $kernel:pidtbs/dtbs/ + target: / + - source: boot-assets/ + target: / + - name: ubuntu-boot + role: system-boot + + + If those could be provided in a snap branch that would be *amazing* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926005] [NEW] [SRU] 2.50
Public bug reported: This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.50/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.50 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The snappy team released a new release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926005 Title: [SRU] 2.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1926005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920107] Re: Failed messages of sd-umoun show with reboot/shutdown
** Package changed: snapd (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920107 Title: Failed messages of sd-umoun show with reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1920107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920107] Re: Failed messages of sd-umoun show with reboot/shutdown
** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920107 Title: Failed messages of sd-umoun show with reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1920107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922293] Re: Snaps appear broken on 21.04 Beta with ZFS
[from-irc] mvo: hey! There are 2 things here: - the zfs generator is currently broken in the default setup due to OpenZFS 2.0 default layout. ubiquity in unapproved since this morning is fixing this (people using our default setup will not be impacted by the bug then) - then, for people using ZFS themselves (no ZSys/not our default setup with a generator), indeed, all the .mount units needs to specify After=zfs-mount.service as Pawel suggested (as the mount points are only available once zfs-mount.service has run) mvo: I guess cking (who is our ZFS maintainer) can have a second eye on this, but the truth shouldn’t be far from that :) didrocks: cool, thanks. so your recommendation is that we implement the workaround? didrocks: for those who use non-defaults? mvo: correct, for everyone using non default having a dataset as a parent directory where you mount the snaps (for the .mount files) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922293 Title: Snaps appear broken on 21.04 Beta with ZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922293] Re: Snaps appear broken on 21.04 Beta with ZFS
This looks a lot like an issue with zfs-linux to me (and *maybe* systemd, not sure about this). The issue is that the snaps are on /var/lib/snapd/snaps and snapd writes mount units into /etc/systemd/system/ so that the snaps are mounted under /snap//. Looking at a zfs-linux system and the "mount" output /var/lib is mounted: $ mount |grep var/lib rpool/ROOT/ubuntu_azzm5v/var/lib on /var/lib type zfs (rw,relatime,xattr,posixacl) and the systemd unit for this mount point is auto-generated: $ systemctl status var-lib.mount var-lib.mount - /var/lib Loaded: loaded (/proc/self/mountinfo) Active: active (mounted) since Tue 2021-04-06 16:38:58 CEST; 19min ago Where: /var/lib What: rpool/ROOT/ubuntu_azzm5v/var/lib Systemd should order mounts so that var-lib.mount is mounted before What=/var/lib/snapd/... is used. I see a zfs-generator in the zfs-linux source tree that looks like it should generator the mount entries from the pool. However nothing generated in /run/systemd/generator: $ find /run/systemd/generator /run/systemd/generator /run/systemd/generator/netplan.stamp /run/systemd/generator/openvpn.service.wants /run/systemd/generator/local-fs.target.wants /run/systemd/generator/local-fs.target.wants/systemd-remount-fs.service /run/systemd/generator/swap.target.requires /run/systemd/generator/swap.target.requires/dev-disk-by\x2duuid-9c43c866\x2dbe89\x2d499c\x2d9300\x2d098d5dcb0509.swap /run/systemd/generator/dev-disk-by\x2duuid-9c43c866\x2dbe89\x2d499c\x2d9300\x2d098d5dcb0509.swap /run/systemd/generator/boot-grub.mount /run/systemd/generator/local-fs.target.requires /run/systemd/generator/local-fs.target.requires/boot-grub.mount /run/systemd/generator/local-fs.target.requires/boot-efi.mount /run/systemd/generator/boot-efi.mount We could easily workaround this via Pawels approach above but I feel this will affect more than snapd. Everyone who wants to mount anyting under /var/lib will be affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922293 Title: Snaps appear broken on 21.04 Beta with ZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922293] Re: Snaps appear broken on 21.04 Beta with ZFS
** Also affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922293 Title: Snaps appear broken on 21.04 Beta with ZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
Fwiw, the dtbs/ dir: $ ls pi-kernel-armhf-rev266/dtbs/ bcm2708-rpi-b.dtb bcm2710-rpi-cm3.dtb bcm2835-rpi-zero.dtb bcm2708-rpi-b-plus.dtbbcm2711-rpi-400.dtb bcm2835-rpi-zero-w.dtb bcm2708-rpi-b-rev1.dtbbcm2711-rpi-4-b.dtb bcm2836-rpi-2-b.dtb bcm2708-rpi-cm.dtbbcm2711-rpi-cm4.dtb bcm2837-rpi-3-a-plus.dtb bcm2708-rpi-zero.dtb bcm2835-rpi-a.dtbbcm2837-rpi-3-b.dtb bcm2708-rpi-zero-w.dtbbcm2835-rpi-a-plus.dtb bcm2837-rpi-3-b-plus.dtb bcm2709-rpi-2-b.dtb bcm2835-rpi-b.dtbbcm2837-rpi-cm3-io3.dtb bcm2710-rpi-2-b.dtb bcm2835-rpi-b-plus.dtb overlays.tgz bcm2710-rpi-3-b.dtb bcm2835-rpi-b-rev2.dtb bcm2710-rpi-3-b-plus.dtb bcm2835-rpi-cm1-io1.dtb $ ls pi-kernel-arm64-rev264/dtbs/ broadcom/ overlays/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
The kernel wants to use: ``` assets: pidtbs: update: true content: - dtbs/ ``` instead of the one suggested above because the pi-kernel on arm64 and armhf have different dtbs/ dir layout: arm64: dtbs/broadcom/*.dtb, dtbs/overlays armhf: dtbs/*.dtb, dtbs/overlays So the armhf has all the dtb files under dtbs/ directly and the arm64 has it under broadcom/. The suggestion is then that the gadget maps it from here to the right places. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920754] Re: FTBFS and autopkgtest failure in hirsute
** Changed in: snapd (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920754 Title: FTBFS and autopkgtest failure in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1920754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636927] Re: upgrading kernel/gadget snap on Pi3 did not update dtb files
This is in progress now in the snapd and ubuntu-image. This will also need changes in the gadget/kernel that are tracked here: https://bugs.launchpad.net/snapd/+bug/1907056 ** Changed in: snapd (Ubuntu) Status: Triaged => In Progress ** Also affects: ubuntu-image (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-image (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-image (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636927 Title: upgrading kernel/gadget snap on Pi3 did not update dtb files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1636927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
** Description changed: Snapd will soon support to have DTBs in the kernel snap that are automatically installed on kernel refreshes. To support this, please add the following file to the pi-kernel: - WE ALSO NEED TO UPDATE THE ASSUMES in the meta/snap.yaml, diff will - follow shortly. + This should also add "assumes: [kernel-assets]" to the meta/snap.yaml so + that the updated kernel/gadget are only used by a snap version that + understand this, see https://github.com/snapcore/snapd/pull/ $ cat meta/kernel.yaml assets: pidtbs: update: true content: - dtbs/broadcom/ - dtbs/overlays/ This will allow the gadget to select DTBs from the kernel. The gadget needs to be updated to have all dtb files removed. And the gadget.yaml needs to change to something like $ head -20 meta/gadget.yaml device-tree: bcm2709-rpi-3-b-plus volumes: pi: schema: mbr bootloader: u-boot structure: - name: ubuntu-seed role: system-seed filesystem: vfat type: 0C size: 1200M content: - source: $kernel:pidtbs/dtbs/broadcom/ target: / - source: $kernel:pidtbs/dtbs/overlays/ target: /overlays - source: boot-assets/ target: / - name: ubuntu-boot role: system-boot ... If those could be provided in a snap branch that would be *amazing* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
** Description changed: Snapd will soon support to have DTBs in the kernel snap that are automatically installed on kernel refreshes. To support this, please add the following file to the pi-kernel: + + WE ALSO NEED TO UPDATE THE ASSUMES in the meta/snap.yaml, diff will + follow shortly. $ cat meta/kernel.yaml assets: pidtbs: update: true content: - dtbs/broadcom/ - dtbs/overlays/ This will allow the gadget to select DTBs from the kernel. The gadget needs to be updated to have all dtb files removed. And the gadget.yaml needs to change to something like - $ head -20 meta/gadget.yaml + $ head -20 meta/gadget.yaml device-tree: bcm2709-rpi-3-b-plus volumes: - pi: - schema: mbr - bootloader: u-boot - structure: - - name: ubuntu-seed - role: system-seed - filesystem: vfat - type: 0C - size: 1200M - content: - - source: $kernel:pidtbs/dtbs/broadcom/ - target: / - - source: $kernel:pidtbs/dtbs/overlays/ - target: /overlays - - source: boot-assets/ - target: / - - name: ubuntu-boot - role: system-boot + pi: + schema: mbr + bootloader: u-boot + structure: + - name: ubuntu-seed + role: system-seed + filesystem: vfat + type: 0C + size: 1200M + content: + - source: $kernel:pidtbs/dtbs/broadcom/ + target: / + - source: $kernel:pidtbs/dtbs/overlays/ + target: /overlays + - source: boot-assets/ + target: / + - name: ubuntu-boot + role: system-boot ... If those could be provided in a snap branch that would be *amazing* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915156] Re: sudoers file keeps being tracked as part of snapd
** Changed in: snapd (Ubuntu) Status: Confirmed => In Progress ** Changed in: snapd (Ubuntu) Importance: Undecided => High ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Michael Vogt (mvo) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915156 Title: sudoers file keeps being tracked as part of snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1915156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915250] Re: buildd file owner/group for shared libraries
Fwiw, mysql-8.0 is also affected: $ dpkg -c libmysqlclient21_8.0.23-3_amd64.deb|grep buildd drwxr-xr-x buildd/buildd 0 2021-02-11 10:32 ./ [many more] And some more: $ dpkg -c libqt5xdg3_3.6.0-1ubuntu2_amd64.deb |grep buildd -rw-r--r-- buildd/buildd 268440 2021-02-11 21:58 ./usr/lib/x86_64-linux-gnu/libQt5Xdg.so.3.6.0 But it seems to have stopped around Saturday, not sure if something was done on the buildds maybe? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915250 Title: buildd file owner/group for shared libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878541] Re: Grub fails to load kernel from squashfs if mem < 1500mb
This is fixed now. ** Changed in: snapd Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878541 Title: Grub fails to load kernel from squashfs if mem < 1500mb To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1878541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915248] [NEW] [SRU] 2.49
Public bug reported: This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.49/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.49 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The snappy team released a new release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915248 Title: [SRU] 2.49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1915248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
** Description changed: Snapd will soon support to have DTBs in the kernel snap that are automatically installed on kernel refreshes. To support this, please add the following file to the pi-kernel: $ cat meta/kernel.yaml assets: pidtbs: update: true content: - dtbs/broadcom/ - - dtbs/overlays/ + - dtbs/overlays/ - This will allow the gadget to select DTBs from the kernel via: - $ diff -u meta/gadget.yaml.orig meta/gadget.yaml - --- meta/gadget.yaml.orig 2020-12-07 10:10:16.775139010 +0100 - +++ meta/gadget.yaml 2020-12-07 10:11:33.482871026 +0100 - @@ -10,8 +10,10 @@ - type: 0C - size: 1200M - content: - - - source: boot-assets/ - + - source: $kernel:pidtbs/dtbs/broadcom/ - target: / - + - source: $kernel:pidtbs/dtbs/overlays/ - +target: /overlays - - name: ubuntu-boot - role: system-boot - filesystem: vfat + This will allow the gadget to select DTBs from the kernel. The gadget + needs to be updated to have all dtb files removed. And the gadget.yaml + needs to change to something like + + $ head -20 meta/gadget.yaml + device-tree: bcm2709-rpi-3-b-plus + volumes: + pi: + schema: mbr + bootloader: u-boot + structure: + - name: ubuntu-seed + role: system-seed + filesystem: vfat + type: 0C + size: 1200M + content: + - source: $kernel:pidtbs/dtbs/broadcom/ + target: / + - source: $kernel:pidtbs/dtbs/overlays/ + target: /overlays + - source: boot-assets/ + target: / + - name: ubuntu-boot + role: system-boot + ... If those could be provided in a snap branch that would be *amazing* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
After discussing this we decided that we will leave cgroups v1 support for 21.04 because the snapd team will not be able to port all features to v2 in time. But early in the 21.10 cycle v1 is turned off and snapd needs to be ported to full v2 support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
@rbalint Do you have a timeline when you plan this? The changes required make this most likely something we can only tackle during the 21.10 cycle :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
@rbalint Thanks for this heads up. Unfortunately we are not ready for cgroups v2. Snapd is working on v2 systems but a lot of the functionality is not ported. AIUI it requires quite a bit of work on our side and the two are quite different :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906690] Re: [SRU] 2.48.2
** Summary changed: - [SRU] 2.48.1 + [SRU] 2.48.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906690 Title: [SRU] 2.48.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1906690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
** Description changed: Snapd will soon support to have DTBs in the kernel snap that are automatically installed on kernel refreshes. To support this, please add the following file to the pi-kernel: $ cat meta/kernel.yaml assets: pidtbs: update: true content: - - dtbs/ + - dtbs/broadcom/ + - dtbs/overlays/ This will allow the gadget to select DTBs from the kernel via: $ diff -u meta/gadget.yaml.orig meta/gadget.yaml --- meta/gadget.yaml.orig 2020-12-07 10:10:16.775139010 +0100 +++ meta/gadget.yaml 2020-12-07 10:11:33.482871026 +0100 @@ -10,8 +10,10 @@ type: 0C size: 1200M content: - - source: boot-assets/ - + - source: $kernel:pidtbs/broadcom/ + + - source: $kernel:pidtbs/dtbs/broadcom/ target: / - + - source: $kernel:pidtbs/overlays/ + + - source: $kernel:pidtbs/dtbs/overlays/ +target: /overlays - name: ubuntu-boot role: system-boot filesystem: vfat If those could be provided in a snap branch that would be *amazing* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
** Description changed: Snapd will soon support to have DTBs in the kernel snap that are automatically installed on kernel refreshes. To support this, please add the following file to the pi-kernel: $ cat meta/kernel.yaml assets: - pi-dtbs: + pidtbs: update: true content: - dtbs/ This will allow the gadget to select DTBs from the kernel via: $ diff -u meta/gadget.yaml.orig meta/gadget.yaml --- meta/gadget.yaml.orig 2020-12-07 10:10:16.775139010 +0100 +++ meta/gadget.yaml 2020-12-07 10:11:33.482871026 +0100 @@ -10,8 +10,10 @@ type: 0C size: 1200M content: - - source: boot-assets/ - + - source: $kernel:pi-dtbs/broadcom/ + + - source: $kernel:pidtbs/broadcom/ target: / - + - source: $kernel:pi-dtbs/overlays/ + + - source: $kernel:pidtbs/overlays/ +target: /overlays - name: ubuntu-boot role: system-boot filesystem: vfat If those could be provided in a snap branch that would be *amazing* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
** Description changed: Snapd will soon support to have DTBs in the kernel snap that are automatically installed on kernel refreshes. To support this, please add the following file to the pi-kernel: $ cat meta/kernel.yaml assets: pi-dtbs: update: true content: - - dtbs + - dtbs/ This will allow the gadget to select DTBs from the kernel via: $ diff -u meta/gadget.yaml.orig meta/gadget.yaml --- meta/gadget.yaml.orig 2020-12-07 10:10:16.775139010 +0100 +++ meta/gadget.yaml 2020-12-07 10:11:33.482871026 +0100 @@ -10,8 +10,10 @@ type: 0C size: 1200M content: - - source: boot-assets/ - + - source: $kernel:pi-dtbs/broadcom + + - source: $kernel:pi-dtbs/broadcom/ target: / - + - source: $kernel:pi-dtbs/overlays + + - source: $kernel:pi-dtbs/overlays/ +target: /overlays - name: ubuntu-boot role: system-boot filesystem: vfat If those could be provided in a snap branch that would be *amazing* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
** Description changed: Snapd will soon support to have DTBs in the kernel snap that are automatically installed on kernel refreshes. To support this, please add the following file to the pi-kernel: $ cat meta/kernel.yaml assets: - pi-dtbs: - update: true - content: - - dtbs + pi-dtbs: + update: true + content: + - dtbs This will allow the gadget to select DTBs from the kernel via: $ diff -u meta/gadget.yaml.orig meta/gadget.yaml --- meta/gadget.yaml.orig 2020-12-07 10:10:16.775139010 +0100 +++ meta/gadget.yaml 2020-12-07 10:11:33.482871026 +0100 @@ -10,8 +10,10 @@ - type: 0C - size: 1200M - content: + type: 0C + size: 1200M + content: - - source: boot-assets/ + - source: $kernel:pi-dtbs/broadcom - target: / + target: / + - source: $kernel:pi-dtbs/overlays +target: /overlays -- name: ubuntu-boot - role: system-boot - filesystem: vfat + - name: ubuntu-boot + role: system-boot + filesystem: vfat + + If those could be provided in a snap branch that would be *amazing* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] [NEW] Please add meta/kernel.yaml
Public bug reported: Snapd will soon support to have DTBs in the kernel snap that are automatically installed on kernel refreshes. To support this, please add the following file to the pi-kernel: $ cat meta/kernel.yaml assets: pi-dtbs: update: true content: - dtbs This will allow the gadget to select DTBs from the kernel via: $ diff -u meta/gadget.yaml.orig meta/gadget.yaml --- meta/gadget.yaml.orig 2020-12-07 10:10:16.775139010 +0100 +++ meta/gadget.yaml2020-12-07 10:11:33.482871026 +0100 @@ -10,8 +10,10 @@ type: 0C size: 1200M content: - - source: boot-assets/ + - source: $kernel:pi-dtbs/broadcom target: / + - source: $kernel:pi-dtbs/overlays +target: /overlays - name: ubuntu-boot role: system-boot filesystem: vfat ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906690] [NEW] [SRU] 2.48.1
Public bug reported: placeholder ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906690 Title: [SRU] 2.48.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1906690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904098] Re: [SRU] 2.48
The travis runs are currently not active, we move to GH actions. The 2.48 release test run is visible at https://github.com/snapcore/snapd/pull/9685/checks?check_run_id=1443415116 Some isolated test failures on centos/suse but Ubuntu is all green. One small issue on ubuntu-core-20 with the fsck test which happens because of a change in the gadget and the fix for that will be part of 2.48.1 (it's harmless, really just affects the test, no real functionality). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904098 Title: [SRU] 2.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1904098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905272] Re: Can't get h/w video acceleration on rpi4
** Changed in: snapd Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905272 Title: Can't get h/w video acceleration on rpi4 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1905272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903054] Re: [SRU] Please merge u-boot 2020.10+dfsg-1 from Debian unstable
** Also affects: u-boot (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: u-boot (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: u-boot (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: u-boot (Ubuntu Bionic) Status: New => In Progress ** Changed in: u-boot (Ubuntu Focal) Status: New => In Progress ** Changed in: u-boot (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903054 Title: [SRU] Please merge u-boot 2020.10+dfsg-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1903054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904098] [NEW] [SRU] 2.48
Public bug reported: This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.48/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.48 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The travis logs for 2.48 can be found here: https://travis- ci.org/snapcore/snapd/branches The snappy team released a new release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904098 Title: [SRU] 2.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1904098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903054] Re: Please merge u-boot 2020.10+dfsg-1 from Debian unstable
Thanks for this! I sponsored the upload, happy to sponsor more! ** Changed in: u-boot (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903054 Title: Please merge u-boot 2020.10+dfsg-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1903054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
